Re: Connect, ping, traceroute work, but not surf on the net

Marcelo Laia wrote:
I connect to net from my notebook like this:

ISP -----------> computer -----------> notebook (friend) ------------>
my notebook
ADSL cable wireless ad-hoc

My notebook connect, i am able to ping any IP, traceroute resolve, but
firefox, aMSN, skype, emphaty didn't connect/surf on the web.

This layout was working very well. Since may, 7, at night, dind't work any more.

Here is some information:

Debian testing kernel 2.6.29-1-686

At work, from eth0, I surf on the net very well.

:~$ cat /etc/resolv.conf
nameserver 200.221.11.100
nameserver 208.67.222.222
nameserver 192.168.0.1
:~$
:~$ traceroute www.google.com
traceroute to www.google.com (74.125.113.147), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.474 ms 0.965 ms 1.393 ms
2 10.1.1.1 (10.1.1.1) 12.775 ms 13.050 ms 13.282 ms
3 192.168.2.2 (192.168.2.2) 13.694 ms 14.743 ms 15.106 ms
4 BrT-L10-bnut3703.dsl.brasiltelecom.net.br (201.24.99.254) 50.339
ms 54.201 ms 57.317 ms
5 BrT-10G4-0-0-bsacoborder.brasiltelecom.net.br (201.10.206.206)
107.511 ms 110.020 ms 115.461 ms
6 200.163.207.202 (200.163.207.202) 248.044 ms 211.421 ms 236.112 ms
7 72.14.236.173 (72.14.236.173) 236.264 ms 239.429 ms 242.608 ms
8 209.85.254.252 (209.85.254.252) 271.682 ms * 271.750 ms
9 72.14.239.136 (72.14.239.136) 279.964 ms 280.079 ms 264.343 ms
10 209.85.249.238 (209.85.249.238) 272.560 ms 275.016 ms 280.158 ms
11 64.233.174.117 (64.233.174.117) 280.371 ms 282.002 ms 282.864 ms
12 72.14.236.193 (72.14.236.193) 225.116 ms 216.239.47.250
(216.239.47.250) 228.493 ms *
13 vw-in-f147.google.com (74.125.113.147) 240.297 ms 246.500 ms 252.203 ms
:~$
:~$ ping 200.221.11.100
PING 200.221.11.100 (200.221.11.100) 56(84) bytes of data.
64 bytes from 200.221.11.100: icmp_seq=1 ttl=56 time=59.9 ms
64 bytes from 200.221.11.100: icmp_seq=2 ttl=56 time=58.9 ms
64 bytes from 200.221.11.100: icmp_seq=3 ttl=56 time=57.8 ms
64 bytes from 200.221.11.100: icmp_seq=4 ttl=56 time=52.3 ms
64 bytes from 200.221.11.100: icmp_seq=5 ttl=56 time=58.1 ms
64 bytes from 200.221.11.100: icmp_seq=6 ttl=56 time=56.2 ms
64 bytes from 200.221.11.100: icmp_seq=7 ttl=56 time=59.0 ms
64 bytes from 200.221.11.100: icmp_seq=8 ttl=56 time=56.7 ms
^C
--- 200.221.11.100 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7010ms
rtt min/avg/max/mdev = 52.398/57.416/59.914/2.221 ms
:~$

:~$ sudo route
Tabela de Roteamento IP do Kernel
Destino Roteador MáscaraGen. Opções Métrica Ref Uso Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
default xxx-5e7b4676c1d 0.0.0.0 UG 0 0 0 wlan0
:~$

The IP 192.168.0.1 is from host xxx-5e7b4676c1d (my friend's notebook).

:~$ cat /etc/host.conf
multi on
:~$

Any clue here?

Thank you very much!

I have had very similar problems and every time it has been a problem with mdns being used to resolve sites external to my LAN. The easiest fix for me is to just get rid of the avahi-daemon package as it takes mdns with it and I don't use any packages that rely on mdns.

The symptoms are the same for me as they are for you. I can ping, traceroute, and use host to resolve urls from the bash prompt, but when I try to surf the net nothing gets resolved.

To check to see if this is the problem install wireshark, if you don't already have it installed, and do a packet capture when trying to surf to an external website. If you have dns queries going to 224.xxx.xxx.xxx avahi-daemon/mdns is the culprit. There's another fix that doesn't require getting rid of avahi-daemon if you make use of it, but I can't remember what it is off the top of my head. IIRC it has to do with /etc/hosts and localdomain, but I wouldn't swear to that. It's been too long since I wanted to keep avahi-daemon and repaired the problem without getting rid of avahi-daemon and I've forgotten the exact details.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: internet apps dont connect in FC14
    ... traceroute to the same address. ... It won't resolve the name. ... download software. ... I can also ping sites out on the Internet from the ...
    (Fedora)
  • Re: Name resolution vs. multiple NICs
    ... Not, they cannot ping that name, not even on the same machine. ... For example I may have a private DNS server that will ... > discover the correct FQDN. ... can resolve the name on the computer you run it on. ...
    (microsoft.public.win32.programmer.networks)
  • More info (Was: Web access stopped working - intrusion?)
    ... Walter Hofmann wrote: ... try to ping or traceroute to it. ... anything it greps forever in file /dev/DEVICES. ...
    (comp.os.linux.security)
  • Re: A problem with "hosts" file: hostnames with dots are not being resolved
    ... whenever their DNS server can't resolve ... Windows 2000 IP Configuration ... zzyzx. ... Ping statistics for 192.168.1.22: ...
    (microsoft.public.win2000.dns)
  • [SLE] Apache 2.0.46 & ipv6
    ... I have setup the dns to resolve ipv6.wiplinger.org. ... I can ping this host from my local lan from an xp machine with ping and ... In order to make sure that I really use IPv6, I set up apache to use ...
    (SuSE)