> > > D) It's not connectivity to the WAP that's the problem, it's accessing > the > 'Net (directly or via a T&C Web page first) that fails because the packets > apparently insist on forcing themselves on the non-running eth0 and there's > no cable to move them along. So they die. > > > I use the phrase "wap connectivity" as short notation to describe the problem. The laptop has wireless radio connectivity but not ip connectivity over the wifi link.
> > > Have you tried removing the static ip config for eth0 on the Sony and > test > > WAP connectivity? > > Yep. If I manually (as root) issue 'ifconfig eth0 down' everything works. > What I need to do is automate this for the Sony's user. > > > That's not what I meant. I should have written "have you deleted the static ip config stanza from /etc/rc.d/rc.inet1.conf file and then tested net connectivity over wifi.?" Also, as Slackware will start up the interfaces in the order they are found in that file, have you tried listing wla0 first? Maybe if wlan0 starts up first, it's def gwy would get preference. The other thing you could do is not define the def gwy for eth0 or have a rc.inet1.bak with the eth0 static ip config. When you connect to an eth lan, just copy that file over inet1.conf. Of course these are just band-aids to get you working over wifi assuming the Dell is similarly configured. All things being the same in this equation, same distro rev, WICD and static ip config, the only other variable between the two computers is the NIC driver. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
