Hi Folks,

I've a strange behaviour with an embedded ARM-based platform using the ath5k 
(linux 2.6.27) with
a AR5414 chip.

Everything seems to be OK (ifconfig wlan0 up works), I can transmit some stuff 
apparently, but I get absolutely
NO packet.

Hereafter, the results from iwconfig and ifconfig (after having done ifconfig 
wlan0 up)

/sbin # iwconfig
lo        no wireless extensions.

dummy0    no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11abg  ESSID:"public-heig-vd"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:16:9C:BA:D8:71
          Bit Rate=36 Mb/s   Tx-Power=23 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Encryption key:off
          Power Management:off
          Link Quality=62/100  Signal level:-54 dBm  Noise level=-94 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

gre0      no wireless extensions.

(after having made a ping)

/sbin # ifconfig
wlan0     Link encap:Ethernet  HWaddr 00:0B:6B:2B:96:E2
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1824 (1.7 KiB)

wmaster0  Link encap:UNSPEC  HWaddr 
00-0B-6B-2B-96-E2-40-0A-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING 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)


As you can see, there is 3 TX packets (which are issued from the ping command), 
but no rx packets is received.


Any idea??

Kind regards
Daniel



_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Reply via email to