Timur
Do:
$ ifconfig
which will report like below. All channels except "lo" should be
closed with commands like:
$ sudo ifconfig wlan0 down
before doing a dialout, or the DNS for ppp0 will be misdirected to
that for wlan0.
You can compare:
$ ping -c 1 209.85.171.83
PING 209.85.171.83 (209.85.171.83) 56(84) bytes of data.
64 bytes from 209.85.171.83: icmp_seq=1 ttl=249 time=104 ms
with
$ ping -c 1 gmail.com
PING gmail.com (209.85.171.83) 56(84) bytes of data.
64 bytes from cg-in-f83.google.com (209.85.171.83): icmp_seq=1 ttl=249
time=106 ms
If the first succeeds, while the 2nd fails, the problem is only DNS service.
If the first fails, you do not have a CONNECT to the Internet.
Marv S
MarvS
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6810 errors:0 dropped:0 overruns:0 frame:0
TX packets:6810 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:340500 (332.5 KB) TX bytes:340500 (332.5 KB)
wlan0 Link encap:Ethernet HWaddr 00:13:d3:00:6e:91
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:d3ff:fe00:6e91/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1990 errors:0 dropped:0 overruns:0 frame:0
TX packets:1407 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1813529 (1.7 MB) TX bytes:255837 (249.8 KB)
wmaster0 Link encap:UNSPEC HWaddr
00-13-D3-00-6E-91-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
On Sat, Jan 10, 2009 at 1:03 PM, Timur Irmatov <irmatov@xxxxxxxxx> wrote:
> Hi, Bjorn.
>
> On Sat, Jan 10, 2009 at 9:19 PM, Bjorn Wielens <Uniacke1@xxxxxxxx> wrote:
>> Hi,
>> I read the message...
>> Can you browse the internet normally?
>> What exactly is it that you are pinging?
>> BJorn.
>
> I just tried again, and got the same results. Answers to your
> questions: no, I cannot browse internet normally. I ping the other
> side of ppp connection (Access server at ISP). It's IP address is
> first in traceroute output from modem connection, and also could be
> learned from output of 'ip address ls ppp0' or 'ifconfig ppp0' - it is
> peer ip address.
>
> Following are ping results I got this time. As you see, pings start
> ok, then for 30 secs there seems to be no answer to pings but then
> suddenly packets arrive, with big (and decreasing delays), then
> everything repeats from the beginning. No packets are lost. It seems
> as if some buffering is occuring inside of the drivers..
>
> PING A.B.C.D (A.B.C.D) 56(84) bytes of data.
> 64 bytes from A.B.C.D: icmp_seq=1 ttl=255 time=278 ms
> 64 bytes from A.B.C.D: icmp_seq=2 ttl=255 time=136 ms
> ... some lines removed...
> 64 bytes from A.B.C.D: icmp_seq=32 ttl=255 time=140 ms
> 64 bytes from A.B.C.D: icmp_seq=33 ttl=255 time=126 ms
>
> 64 bytes from A.B.C.D: icmp_seq=34 ttl=255 time=31511 ms
> 64 bytes from A.B.C.D: icmp_seq=35 ttl=255 time=30512 ms
> 64 bytes from A.B.C.D: icmp_seq=36 ttl=255 time=29540 ms
> 64 bytes from A.B.C.D: icmp_seq=37 ttl=255 time=28540 ms
> ... some lines removed...
> 64 bytes from A.B.C.D: icmp_seq=70 ttl=255 time=2875 ms
> 64 bytes from A.B.C.D: icmp_seq=71 ttl=255 time=1875 ms
> 64 bytes from A.B.C.D: icmp_seq=72 ttl=255 time=875 ms
> 64 bytes from A.B.C.D: icmp_seq=73 ttl=255 time=128 ms
>
> 64 bytes from A.B.C.D: icmp_seq=74 ttl=255 time=38520 ms
> 64 bytes from A.B.C.D: icmp_seq=75 ttl=255 time=37531 ms
> 64 bytes from A.B.C.D: icmp_seq=76 ttl=255 time=36531 ms
> ...some lines removed...
> 64 bytes from A.B.C.D: icmp_seq=112 ttl=255 time=1283 ms
> 64 bytes from A.B.C.D: icmp_seq=113 ttl=255 time=279 ms
> 64 bytes from A.B.C.D: icmp_seq=114 ttl=255 time=180 ms
> 64 bytes from A.B.C.D: icmp_seq=115 ttl=255 time=132 ms
>
>
> --
> Timur Irmatov, xmpp:irmatov@xxxxxxxxx
>
