mandriva 2006 - wireless interface ra0 becomes unresponsive

via_strass · 02-25-2006, 02:46 PM

hi there,

i'm using the rtx500 driver over mandriva 2006 to connect by laptop (ralink 2500 cardbus card) to a router/broadband modem.

i think the driver came with the distro, but i'm not sure because i also installed the module by hand when running fc4 previously.

my problem is that wireless usually works, but then will suddenly become unresponsive.

i notice because web pages fail to load.

then i've tried pinging the router - it fails if i use the hostname 'homeportal' - 'unknown host'. if i ping 192.168.254.1 it succeeds - sort of:

Code:

[jack@sonja ~]$ ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=255 time=9956 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=255 time=8957 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=255 time=7958 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=255 time=6958 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=255 time=5959 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=255 time=4967 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=255 time=3968 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=255 time=2968 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=255 time=1969 ms
64 bytes from 192.168.1.254: icmp_seq=10 ttl=255 time=969 ms
64 bytes from 192.168.1.254: icmp_seq=29 ttl=255 time=10.8 ms
64 bytes from 192.168.1.254: icmp_seq=12 ttl=255 time=17012 ms
64 bytes from 192.168.1.254: icmp_seq=13 ttl=255 time=16014 ms
64 bytes from 192.168.1.254: icmp_seq=14 ttl=255 time=15014 ms
64 bytes from 192.168.1.254: icmp_seq=15 ttl=255 time=14015 ms
64 bytes from 192.168.1.254: icmp_seq=16 ttl=255 time=13015 ms
64 bytes from 192.168.1.254: icmp_seq=17 ttl=255 time=12016 ms
64 bytes from 192.168.1.254: icmp_seq=18 ttl=255 time=11016 ms
64 bytes from 192.168.1.254: icmp_seq=19 ttl=255 time=10017 ms
64 bytes from 192.168.1.254: icmp_seq=20 ttl=255 time=9017 ms
64 bytes from 192.168.1.254: icmp_seq=21 ttl=255 time=8018 ms
64 bytes from 192.168.1.254: icmp_seq=22 ttl=255 time=7018 ms
64 bytes from 192.168.1.254: icmp_seq=23 ttl=255 time=6019 ms
64 bytes from 192.168.1.254: icmp_seq=24 ttl=255 time=5019 ms
64 bytes from 192.168.1.254: icmp_seq=25 ttl=255 time=4020 ms
64 bytes from 192.168.1.254: icmp_seq=26 ttl=255 time=3021 ms
64 bytes from 192.168.1.254: icmp_seq=27 ttl=255 time=2021 ms
64 bytes from 192.168.1.254: icmp_seq=28 ttl=255 time=1022 ms

--- 192.168.1.254 ping statistics ---
30 packets transmitted, 28 received, 6% packet loss, time 29004ms
rtt min/avg/max/mdev = 10.838/7426.603/17012.960/4729.615 ms, pipe 18

ie, it takes about 10 seconds or more for packets to get returned, then 10 or however many packets come back at once.

so i think web or other connections break because they time out.

router provides dhcp and dns, so i think dns times out similarly when pinging 'homeportal'?

i'm not really sure what other logs provide more info on this.

wireless connection in windows on the same machine and from other computers work fine.

i crossposted this to the forums for the driver at rt2x00.serialmonkey.com, hope this is okay, but i have no idea if it's a problem with the drivers. if they come up with anything i'll post it back here, but maybe someone can at least suggest ways to further investigate?

thanks a lot.