On Feb 20, 2008 2:10 PM, Rich Healey <[EMAIL PROTECTED]> wrote:

>  Forrest Y. Yu wrote:
>
> 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
>                 $
>               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.845ms
>                 64 bytes from 192.168.1.11: icmp_seq=3 ttl=64 time=0.854ms
>                 64 bytes from 192.168.1.11: icmp_seq=4 ttl=64 time=0.852ms
>
>                 --- 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
>                 $
>               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
>                 $
>
>             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.
>
>             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.
>
> And also, when this happened, I plugged the wire and tried the wired
> network, it failed too.
>
> Thank you very much.
>
> Best Regards,
> Forrest
>
> On Jan 25, 2008 10:12 PM, Celejar <[EMAIL PROTECTED]> wrote:
> > On Fri, 25 Jan 2008 16:13:12 +0800
> >
> > "Forrest Y. Yu" <[EMAIL PROTECTED]> wrote:
> >
> > > On Jan 25, 2008 3:07 PM, Celejar <[EMAIL PROTECTED]> wrote:
> > > >
> > > > On Fri, 25 Jan 2008 14:50:23 +0800
> > > > "Forrest Y. Yu" <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Hi Everyone,
> > > > >
> > > > > I have a laptop Acer Aspire 5610Z, which uses Atheros AR5005G as
> the
> > > > > network controller. Everything is ok, however, sometime when I
> resume
> > > the
> > > > > machine, I cannot access the network anymore.
> > > >
> > > > Details. What happens when you try to access the network? Can you
> > > > ping the router? Other hosts on the lan? Other hosts on the
> > > > internet? By name? By IP?
> > >
> > > Actually, when I use firefox to access a website, it sometimes
> succeeds, but
> > > the speed is very very slow. It'll take about 5~10 minutes to open a
> Google
> > > main page. Sometimes it fails to open any pages.
> > >
> > > I can ping the router. I can even access the route via the web admin
> > > interface of the router. The speed looks good too. That's the most
> weird
> > > thing.
> > >
> > > I have only one host in the lan -- my laptop. Maybe I should connect
> one
> > > more computer for testing.
> > >
> > > I tried to ping a website by name, it seems reachable. As I mentioned,
> > > sometimes web pages is reachable. The speed is intolerable.
> >
> > By speed, do you mean latency or data transfer time? What are the ping
> > times like (before and after suspend? How long does name resolution
> > take? Do protocols other than HTTP also suffer? What about other
> > browsers?
>
> >
> >
> >
> >
> > > > > What confuses me most is, I can still access my Router, whose
> model is a
> > > > > TP-LINK TL-WR541G/542G.
> > > > >
> > > > > Neither restarting NetworkManager nor reloading the ath_pci solved
> the
> > > > > problem. Everything becomes good again after rebooting, but
> obviously
> > > reboot
> > > > > is not a good solution.
> > > >
> > > > > Cheers,
> > > > > Forrest
> > > >
> > > > Celejar
> >
> > Celejar
> > --
> > mailmin.sourceforge.net - remote access via secure (OpenPGP) email
> > ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
> >
> >
>
>
>
> --
> Stupid is as stupid does.
>
> Why not ifdown [primary interface] && ifup [primary interface] ?
> it's most likely dropping the routing table, one of my old lappy's used to
> do that,.
>
> Regards
>
>
> Rich Healey
>

Thank you Rich. Actually I tried to restart the interface, but it didn't
work. I even reloaded the ath_pci module, it was useless either.

Forrest


-- 
Stupid is as stupid does.

Reply via email to