| View previous topic :: View next topic |
| Author |
Message |
dspahn
Guru
Joined: 22 Jun 2006
Posts: 392
|
 Posted: Fri Jul 06, 2007 10:50 pm Post subject: help with slow network on laptop with atheros/madwifi |
 |
|
I have a Sony V505DC2P with a Atheros AR5212 wireless card using madwifi. This computer has a tremendous amount of latency resolving web addresses. Here's my ifconfig:
ath0 Link encap:Ethernet HWaddr 00:02:8A:BD:48:01
inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::202:8aff:febd:4801/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58390 errors:0 dropped:0 overruns:0 frame:0
TX packets:19595 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22959990 (21.8 Mb) TX bytes:2079879 (1.9 Mb)
eth0 Link encap:Ethernet HWaddr 08:00:46:BA:49:EF
UP BROADCAST 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)
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:1609 errors:0 dropped:0 overruns:0 frame:0
TX packets:1609 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:156671 (152.9 Kb) TX bytes:156671 (152.9 Kb)
wifi0 Link encap:UNSPEC HWaddr 00-02-8A-BD-48-01-38-70-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1394772 errors:0 dropped:0 overruns:0 frame:11406
TX packets:25598 errors:18 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:167090688 (159.3 Mb) TX bytes:2797277 (2.6 Mb)
Interrupt:9
Any ideas?
Thanks![/quote] |
|
| Back to top |
|
 |
RayDude
Advocate
Joined: 29 May 2004
Posts: 2094
Location: San Jose, CA
|
| Posted: Sat Jul 07, 2007 12:36 am Post subject: Re: help with slow network on laptop with atheros/madwifi |
|
|
Need more information:
| Code: | iwconfig
emerge --info
lspci
lsmod
cat /etc/resolv.conf
netstat -rn |
Please note the gateway IP address from netstat -rn:
How long do these pings take? (CTRL-c to exit ping by the way)
Should be something like this:
| Code: | | 64 bytes from 192.168.0.10: icmp_seq=1 ttl=64 time=0.064 ms |
If it is, then try pinging the gateway:
Should look like this:
| Code: | | 64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=5.57 ms |
If its not then you have problems getting through the air. If its fast, then you must have problems with your router.
If you have problems getting through the air, check out signal strength:
Should look like this:
| Code: | srim ~ # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"XXXXXXXX"
Mode:Managed Frequency:2.447 GHz Access Point: 00:XX:XX:XX:XX:XX
Bit Rate=243 Mb/s Tx-Power:24 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX Security mode:restricted
Power Management:off
Link Quality:67/100 Signal level:-53 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:30551 Invalid misc:21188524 Missed beacon:0 |
If signal level is low and noise is high, then figure out how to get your computer closer to router or move the antennas around or something.
Let me know how it goes,
Raydude
_________________
Some day there will only be free software. |
|
| Back to top |
|
|
yuwy
n00b
Joined: 22 May 2006
Posts: 38
|
| Posted: Sat Jul 07, 2007 11:41 am Post subject: |
|
|
if there is another wireless client with an high gain antenna or laptop
closer to the AP than you are, you will experience mad lag.
Ok i just realised that maybe you need more reason as to why,
the reason is that when you want to send packets you need to send a
request to send packet which forces everyone attached to the AP
to stop sending any packets, where you will then have to receive a clear
to send packet from the AP which still makes everyone wait. Where
this sucks is for wireless clients further way from the AP may not
always get the rts packet in before the closer clients. |
|
| Back to top |
|
|
|
Kernel & Hardware
