Re: cannot connect to the internet after resume
On Wed, 20 Feb 2008 14:07:20 +0800
"Forrest Y. Yu" <forrest.yu@gmail.com> wrote:
[please don't top post, and don't send me a separate copy of your mails,
as per the code of conduct]
> The network problem happened to me again today. > Here's your questions and my answers: > > What happens when you try to access the network? > - When I try to open a web page, I just get no reply. Sometimes > I get a reply after long time. > > Can you ping the router? Other hosts on the lan? Other hosts on > the internet? By name? By IP? > - I can ping the router: > $ ping 192.168.1.1 > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. > 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=64.1 ms > 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.05 ms > 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.06 ms > 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.13 ms > > --- 192.168.1.1 ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time > 2999ms > rtt min/avg/max/mdev = 1.057/17.102/64.149/27.166 ms > $
Looks good.
> I can ping other hosts on the lan: > $ ping 192.168.1.11 > PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data. > 64 bytes from 192.168.1.11: icmp_seq=1 ttl=64 time=3.97 ms > 64 bytes from 192.168.1.11: icmp_seq=2 ttl=64 time=0.845 ms > 64 bytes from 192.168.1.11: icmp_seq=3 ttl=64 time=0.854 ms > 64 bytes from 192.168.1.11: icmp_seq=4 ttl=64 time=0.852 ms > > --- 192.168.1.11 ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time > 2997ms > rtt min/avg/max/mdev = 0.845/1.631/3.973/1.352 ms > $
Good.
> I can ping other hosts on the internet: > $ ping www.debian.org > PING www.debian.org (194.109.137.218) 56(84) bytes of data. > 64 bytes from klecker.debian.org (194.109.137.218): > icmp_seq=1 ttl=47 time=401 ms > 64 bytes from klecker.debian.org (194.109.137.218): > icmp_seq=2 ttl=47 time=415 ms > 64 bytes from klecker.debian.org (194.109.137.218): > icmp_seq=3 ttl=47 time=404 ms > 64 bytes from klecker.debian.org (194.109.137.218): > icmp_seq=4 ttl=47 time=404 ms > > --- www.debian.org ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time > 3321ms > rtt min/avg/max/mdev = 401.797/406.603/415.951/5.495 ms > $ > $ ping www.google.com > PING www-china.l.google.com (64.233.189.104) 56(84) bytes of > data. > 64 bytes from hk-in-f104.google.com (64.233.189.104): > icmp_seq=1 ttl=240 time=58.9 ms > 64 bytes from hk-in-f104.google.com (64.233.189.104): > icmp_seq=2 ttl=240 time=55.1 ms > 64 bytes from hk-in-f104.google.com (64.233.189.104): > icmp_seq=3 ttl=240 time=54.2 ms > 64 bytes from hk-in-f104.google.com (64.233.189.104): > icmp_seq=4 ttl=240 time=60.5 ms > > --- www-china.l.google.com ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time > 3003ms > rtt min/avg/max/mdev = 54.227/57.232/60.585/2.627 ms > $
Good.
> > By speed, do you mean latency or data transfer time? > - I don't know. When I access a web page, it is finished after > long time. Sometimes it just fails. > > What are the ping times like (before and after suspend?) > - Pinging seems ok even when internet is inaccessable.
I think that would be impossible.
> How long does name resolution take? > - Name resolution seems ok. > > Do protocols other than HTTP also suffer? What about other > browsers? > - Other browsers such as Epiphany and w3m don't work either.
What about ftp, ssh, smtp, pop?
> And also, when this happened, I plugged the wire and tried the wired > network, it failed too.
Do you have any other machines on the network that you can test? What
about another OS on the machine? We need to figure out if there is a
misconfiguration on your machine or upstream.
> Thank you very much.
Good luck!
> Best Regards, > Forrest
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Received on Wed Feb 20 20:45:46 2008
This archive was generated by hypermail 2.1.8
: Wed Mar 19 2008 - 06:50:43 EDT
|