On Sat, 31 Mar 2012, Mike Connors wrote: > 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.
Mike, Allow me to explain again: here we use static IP addresses and hosts, such as the Sony Vaio, use ethernet. This works fine. At external, wifi hot spots, dhcpcd (called by wicd-client, too) not only gets a dynamic IP address for the portable but the server behind the WAP (if not the WAP itself, but I don't know the specifics of how it works) _overwrites_ /etc/resolv.conf and puts in its preferred DNS name servers. That is, it replaces the contents of resolv.conf that are used here with whatever the remote site server uses. I don't recall what that was at FG, but the local coffee shop, part of the NETbean coffee shop wifi-profiding network, assigned two Google DNS server IP addresses: 8.8.8.8 and 8.8.4.4. This content of resolv.conf was set by NETbeans, not by me. Does this satisfactorily explain the situation? > 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. See above and all previous posts where I keep writing that this is exactly what happens every time a portable computer is conntected to a wireless network elsewhere. It's been the case for the 15 or so years I've traveled with a notebook or laptop and it's just what I keep describing in my messages. Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
