You should get this from the DHCP server of your ISP, which would set it for
the router. Then the router would either pass that along (if you're not
using NAT), or pass itself as the gateway (if you are, which is more common).

If you're not getting default gateway set, you may want to try another DHCP
client (like, dhcpclient, or a newer version of dhcpcd). There are
apparently 2 or 3 ways to send this information, and a number of RFCs that
define different ways that are allowed. In some cases the client has to ask
explicitly for a gateway in its request. Check the configuration file for
your current DHCP client and make sure its asking for that as well.

Networking can be a pain at times, but once you've set it up right once, you
generally don't have to play with it again. Good luck, and keep up the good
attitude of seeing this as a learning experience.

Steven wrote:

> I've managed to get wireles to work.
> But I've stumbled onto an issue that I've always taken for granted.
>
> In rc.inet1.conf, there's this GATEWAY para which defines the default
> gateway.
> I realised that if i do not set the default gateway, ie: Leave it
> empty. my wireless will not be able to get any data outside my internal
> lan.
>
> I dont get it. Since Im able to connect to my ESSID; which means i can
> get my IP from dhcp automatically; then why should I need to set the
> default gateway? If I were to set the default GATEWAY, doesnt that
> defeats the purpose of wireless? Since wireless means mobility. I can
> go to cafes and surf net from there, etc. Go to cafes, sets the ESSID,
> viola. Correct me if im wrong.
>
> Setting DHCP_KEEPGW doesnt help either. I left DHCP_KEEPGW blank.
>
> In order for my wireles to get outside of my internal LAN, I have to
> set the GATEWAY para. Which is weird.
>
> Can anyone shed some light, please?
>
> Thanks & Regards,
> Steven
>