> > > > It shouldn't be in a "running" state unless there is physical > > connectivity > > > and packets are flowing across the interface. > > > > The eth0 interface is not RUNNING, but the routes are there and so is > > the > > constipation. > > > Actually you are wrong on this point. As you stated earlier today, once > you 'ifconfig eth0 down' things worked. If that was truely the case then > the interface was up but > without a carrier. The routes would remain intact as the kernel doesn't > know when or if the network carrier will return. > > Larry - I also found that statement confusing, however from my own testing I think it's behaving that way do the static ip config of eth0.
With a static ip addr config for eth0 in /etc/network/interfaces, ifup / ifdown will insert and remove the default route. However, the state as shown by ifconfig never shows as "running" because there is no carrier. However, if there wasn't a static ip addr config for eth0 and it was up I would expect no routes for that interface to be injected in the routing table because there's nothing configured and with no carrier, the eth0 interface isn't learning any routes to propagate. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
