Re: Laptop Connects to WAP, But Cannot Access 'Net

On Mon, Apr 02, 2012 at 07:33:31PM -0700, Bradley D. Thornton wrote:
> Do yourself and everyone else here a favor. Instead of haphazardly 
> attempting to request assistance with partial snippets, go back to 
> wherever it is that you are experiencing this problem, do the 
> following, and post it to a pastebin so other's can point out where 
> you went astray. There's a pastebin at 
> http://pastebin.northtech.us/ but you can use any pastebin (redact 
> any sensitive data with bogus data if you post the info in a 
> pastebin instead of here).
> 
> <code>
> # cat /etc/rc.d/inet1.conf > wtf.txt

I would suggest removing comments:
	egrep -v '^[[:blank:]]*(;|#|$)' /etc/rc.d/rc.inet1.conf

> # ifconfig -a >> wtf.txt
> # route -n >> wtf.txt

These old and bugridden netutils are not necessary with their 
iproute2 counterparts below. [rant withheld]

> # ip address show >> wtf.txt
> # ip route show >> wtf.txt
> </code>
> 
> Open wtf.txt and paste all of the contents of that file into a 
> pastebin.
> 
> This minor configuration issue is taking entirely too long to
> troubleshoot, due to incomplete information, and is causing you
> way too much stress.
> 
> Please don't continue to provide a description of the problem.
> Just post the output of that file and it will be obvious what
> the problem is so we can get you talking :)

You're right in principle, but I am not sure we will get to the 
bottom of it with that information.

Most captive portals do run their own nameserver. Since they're not 
routing his query packets out to Google Public DNS, they have to run 
a nameserver. (Well, either that, or face a lot of complaints from 
paying customers.)

So I think a piece of the puzzle is missing. Maybe the dhcpcd has 
inhibited updates of resolv.conf ... but yes, that should show in 
uncommented /etc/rc.d/rc.inet1.conf contents.

Another captive portal possibility is redirection of HTTP traffic. 
Therefore (I think someone suggested this already) test with 
http://ip.add.re.ss/ where ip.add.re.ss is the IP of the router.

Also try:
	$ dig slackware.com. any @ip.add.re.ss
The correct answer includes:

slackware.com.          86400   IN      MX      1 mail.cwo.com.
slackware.com.          86400   IN      HINFO   "INTEL" "LINUX"
slackware.com.          86400   IN      A       64.57.102.34
slackware.com.          86400   IN      SOA     ns1.cwo.com. hostmaster.cwo.com. 201102233 43200 3600 604800 86400
slackware.com.          86400   IN      NS      ns2.cwo.com.
slackware.com.          86400   IN      NS      ns1.cwo.com.

There might be other "correct" answers for that particular captive 
portal. ANY answer means that no, the router probably did not give 
you Google Public DNS in your resolv.conf.

If necessary, manually enter "nameserver ip.add.re.ss" into the 
/etc/resolv.conf file.
-- 
  http://rob0.nodns4.us/ -- system administration and consulting
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject: