Re: Laptop Connects to WAP, But Cannot Access 'Net [FIXED]
Bengt Richter <[email protected]>
| Newsgroups | gmane.linux.slackware |
|---|---|
| Message-ID | <[email protected]> |
On 04/03/2012 11:37 AM Rich Shepard wrote: > On Tue, 3 Apr 2012, Robby Workman wrote: > >> If you'd posted the config information and such as you were asked on >> numerous occasions, I'd be willing to bet that someone would have noticed >> that your static ip address on eth0 is in the same subnet as that assigned >> by the wireless access point. Remember when someone asked for your >> routing tables? That's why. > > Robby, > > I wrote this before, but I'll do so again. The static IP address for eth0 > is 192.168.55.5. At this one coffee shop the IP address on wlan0 is > 10.5.70.104. > > The routing table showed the eth0 gateway as 192.168.55.4 and the wlan0 > gateway as 10.5.70.1. > > There's a nice utility called ifplugd that brings up eth0 if there's a > cable attached and brings down eth0 if the cable is removed. There's no > slackbuild script for that (but there is for the required libdaemon), so > I'll build these on the Sony, configure them, and test it at the coffee > shop later today. > > Regards, > > Rich Hm, I wonder if the "right" solution would be a multi-gateway one, with possible simultaneous use of both even, but at least a simple failover sequence. I'm surprised if what it's currently doing is just banging on a dead eth0 gateway as default and not having the logic to see another opening. (OOTB, I mean -- I'm (almost) sure there are ways to make it do it ;-) BTW, can udev be made to handle this kind of thing dynamically/hotplug style to keep up with changing multiple paths to the internet? Regards, Bengt Richter