> > > At the PLUG clinic last week the Sony Vaio laptop on the wireless > interface, wlan0, received an IP address, had the Free Geek server provide > content in /etc/resolv.conf, but would not load the Free Geek web page to > accept their terms and conditions and gain access to the 'Net. > > This morning I spent about an hour at a local coffee shop with the same > results: wlan0 was UP and RUNNING with the IP address of 10.5.70.104 and > nameservers of 8.8.8.8 and 8.8.4.4. But, firefox would not load the > netbeans.com gateway Web page, 'netstat -r' showed the gateways for wlan0, > but ping and traceroute failed with both domain names and IP addresses (the > first showed 56 bytes sent then froze, the latter told me the newwork was > unreachable). > > I don't understand enough about networking to figure out the source of > the > problem. My experiences are that a non-working ping and/or traceroute > telling me that the network is unreachable means the interface cannot find > a > DNS server to resolve the IP address. But, in this case, /etc/resolv.conf > has name servers identified and both ping and traceroute fail when fed IP > addresses, too. > > What might be the problem here, where there's an IP address issued by the > DHCP server in response to a dhcpcd request by wicd, nameservers are > assigned, but there's no ability to connect to a Web server or anywhere > else? > > Rich - From your description of the behavior you're experiencing, I offer the following explanation.
It seems you're having problems with wifi AP captive portals. The reason you're having a problem with that is that you need the *internal* DNS servers that the DHCP server hands out to get name resolution for the internal web server that provides the captive portal web page to your browser for you to accept the terms & conditions and be authorized on the wireless network before you can get connectivity to the internet and your static DNS servers. You *public* DNS servers cannot resolve the netbeans.com domain/url because it has an *internal / private* ip address. It is unknown on the public internet. What I've done in the past to get around this, is to let the DHCP servers overwrite my /etc/resolv.conf file. Once I get connected on the wlan and have internet connectivity, I copy /etc/resolv.bak which has my preferred public DNS servers over /etc/resolv.conf. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
