> > > Based on the testing Rich and I did, I don't think the problem is > specific > > to NM. With WICD, the > > wifi interface would come up and radio connection would be made. But then > > there was IP routing troubles as Rich couldn't get to the wifi captive > > portal page. When I ran a traceroute, I saw the packets attempting to go > > out the eth0 interface that has a static ip but no cable plugged in. > > > > > this makes me feel that the current issue is specific to NM. I wish I could > have had a turn at the wheel with wicd; what you describe sounds much more > within my field to handle. > > Rich, at this point I would highly recommend you go back to the default vanilla Slackware install with WICD. The remove the static ip conifg on eth0 and see if WICD manages the interface and routes packets correctly to the WAP. I suspect it will. I can't recall if we did this test.
Based on my experience with this issue, my definition of the problem is this: When there is a static ip config for eth0 and no cable is plugged into eth0, the default gateway entry for eth0 is not removed and causes problems routing packets over the WLAN. However, this should work. On the Dell, there are two default routes in the routing table. 1 for eth0 and 1 for wlan0. I believe on the Dell there were different metrics when the "route -n" command was run. Which I would expect there to be if on default gwy interface has an active connection and the other doesn't. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
