Jeff Vian & others wrote:
> IIRC, the /etc/sysconfig/network file is used at boot, but not used when doing a network restart, so that may be why the
> change in 'boot' vs 'network restart' routing.
Well, my network file has nothing regarding the gateway, except for GATEWAYDEV=eth0, as recommended here. I removed that line, rebooted, and still could get to the internet. The only constant factor in getting to the internet is the default route I see when I boot or route add -net default gw 192.168.50.1 dev eth0 (not network restart).
> NOZEROCONF=yes in /etc/syconfig/network will remove the route for > 169.254.0.0.
Tried it, didn't work. Now that its been explained what the 169.254.0.0 route is, I'm not really concerned.
All in all, its not a show stopper, but a). I'd like to be able to restart the network and have things working correctly, b). its just not right, and I can't leave it alone! <grin>. Plus I'm learning from all this... thanks again to everyone for help and suggestions. Here are my various scripts, etc...
/etc/sysconfig/network NETWORKING=yes HOSTNAME=choke GATEWAYDEV=eth0 NOZEROCONFIG=yes
# 3Com Corporation|3c905B 100BaseTX [Cyclone] DEVICE=eth0 BOOTPROTO=none BROADCAST=192.168.50.255 HWADDR=:XX:XX:XX:XX IPADDR=192.168.50.48 NETMASK=255.255.255.0 NETWORK=192.168.50.0 ONBOOT=yes TYPE=Ethernet USERCTL=no PEERDNS=no GATEWAY=192.168.50.1
/etc/sysconfig/network-scripts/ifcfg-eth1 # DEC|DECchip 21041 [Tulip Pass 3] DEVICE=eth1 BOOTPROTO=none BROADCAST=192.168.5.255 HWADDR=XX:XX:XX:XX IPADDR=192.168.5.200 NETMASK=255.255.255.0 NETWORK=192.168.5.0 ONBOOT=yes TYPE=Ethernet USERCTL=no PEERDNS=no GATEWAY=
/etc/sysconfig/network-scripts/routes-eth1 (i didn't create this) GATEWAY0=192.168.50.48 NETMASK0=255.255.255.0 ADDRESS0=192.168.50.0
