Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless

AK-san,

PseudoCylon wrote:
> ----- Original Message ----
>   
>> From: Ganbold <ganbold_at_gmail.com>
>> To: PseudoCylon <moonlightakkiy_at_yahoo.ca>
>> Cc: freebsd-current_at_freebsd.org; Ganbold Tsagaankhuu <ganbold_at_mobicom.mn>
>> Sent: Thu, June 10, 2010 10:53:30 AM
>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>
>> It seems like it is running without any problem so far, no more adsl
>> modem problem.
>> I can see arp packets in wlan0 interface as  well as in  macbook.
>> I will continue testing and let you know if there comes any problem.
>>
>> thanks again,
>>
>> Ganbold
>>     
>
> Hello,
>
> Glad to hear. It was an encryption problem. A client was dropping packets..
>
> Please let me know if you find another bug. (Hope there won't be)
>   

Well, looks like I was too fast :(

It seems like client is not receiving any arp packets when rspro doesn't
first initiate ping (maybe arp request) to client.
If I first ping to client from rspro, later on arp packets can be seen
on client.
When I ping from rspro to client, response is very different:

# arp -a
? (192.168.1.43) at 8e:fd:59:d6:3a:50 on bridge0 permanent [bridge]
? (192.168.1.42) at 00:22:cf:03:e0:30 on wlan0 permanent [ethernet]
? (192.168.1.41) at 00:15:6d:c1:c7:77 on arge0 permanent [ethernet]
? (192.168.1.1) at 00:30:54:62:3d:24 on arge0 expires in 1200 seconds
[ethernet]
? (192.168.1.7) at 00:1c:25:9d:36:1d on arge0 expires in 824 seconds
[ethernet]
# ping 192.168.1.50
PING 192.168.1.50 (192.168.1.50): 56 data bytes
64 bytes from 192.168.1.50: icmp_seq=0 ttl=64 time=2.694 ms
64 bytes from 192.168.1.50: icmp_seq=1 ttl=64 time=302.177 ms
64 bytes from 192.168.1.50: icmp_seq=2 ttl=64 time=1.041 ms
64 bytes from 192.168.1.50: icmp_seq=4 ttl=64 time=5234.417 ms
64 bytes from 192.168.1.50: icmp_seq=5 ttl=64 time=4225.060 ms
64 bytes from 192.168.1.50: icmp_seq=6 ttl=64 time=3214.908 ms
64 bytes from 192.168.1.50: icmp_seq=7 ttl=64 time=2207.241 ms
64 bytes from 192.168.1.50: icmp_seq=8 ttl=64 time=1197.061 ms
64 bytes from 192.168.1.50: icmp_seq=9 ttl=64 time=186.833 ms
^C
--- 192.168.1.50 ping statistics ---
11 packets transmitted, 9 packets received, 18.2% packet loss
round-trip min/avg/max/stddev = 1.041/1841.270/5234.417/1870.962 ms
# arp -a          
? (192.168.1.43) at 8e:fd:59:d6:3a:50 on bridge0 permanent [bridge]
? (192.168.1.42) at 00:22:cf:03:e0:30 on wlan0 permanent [ethernet]
? (192.168.1.41) at 00:15:6d:c1:c7:77 on arge0 permanent [ethernet]
? (192.168.1.1) at 00:30:54:62:3d:24 on arge0 expires in 1183 seconds
[ethernet]
? (192.168.1.7) at 00:1c:25:9d:36:1d on arge0 expires in 805 seconds
[ethernet]
? (192.168.1.50) at 00:26:bb:17:f6:61 on arge0 expires in 1186 seconds
[ethernet]
# ping 192.168.1.50
PING 192.168.1.50 (192.168.1.50): 56 data bytes
64 bytes from 192.168.1.50: icmp_seq=2 ttl=64 time=1590.035 ms
64 bytes from 192.168.1.50: icmp_seq=3 ttl=64 time=580.201 ms
64 bytes from 192.168.1.50: icmp_seq=4 ttl=64 time=528.019 ms
^C
--- 192.168.1.50 ping statistics ---
5 packets transmitted, 3 packets received, 40.0% packet loss
round-trip min/avg/max/stddev = 528.019/899.418/1590.035/488.804 ms

Any idea?

thanks,

Ganbold

> Thank you for testing
>
> AK
>
>
>
>
>   


-- 
Computer programmers never die, they just get lost in the processing.