ath5k usage


Does anyone use the ath5k driver (http://madwifi.org/wiki/About/ath5k)
regularly? I can't seem to get it to work. For the last kernel I built
(2.6.25.5), I thought I'd give it a try for my AR5212 Atheros card. While
the Madwifi drivers work great, I can't get any real results out of ath5k.
The first test was just monitor mode, to see if it saw traffic. It
mangaged to grab 3 packets, all invalid (unreadable via
tcpdump/tshark/etc). Another strange thing is that it sets the light on
the back of the card to a constant "on" state. This light usually blinks
during normal use while using the Madwifi drivers. The module loads OK,
the card is recognized. It will take parameters via iwconfig and take an
IP address. In other words, it appears to work fine - only doesn't ;)


su -l -s /bin/ksh
Password:

hello, world
Today is Boomtime, the 16th day of Confusion in the YOLD 3174
root@ root $ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:11:11:2b:6f:83 brd ff:ff:ff:ff:ff:ff

root@ root $ modinfo ath5k
filename: /lib/modules/2.6.25.5/kernel/drivers/net/wireless/ath5k/ath5k.ko.gz
version: 0.1.1 (EXPERIMENTAL)
license: Dual BSD/GPL
description: Support for 5xxx series of Atheros 802.11 wireless LAN cards.
author: Nick Kossifidis
author: Jiri Slaby
srcversion: 77DC604AB448D99160D5FD9
alias: pci:v0000168Cd00000024sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000023sv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Csv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Bsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Asv*sd*bc*sc*i*
alias: pci:v0000168Cd00000019sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000018sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000017sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000016sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000015sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000014sv*sd*bc*sc*i*
alias: pci:v0000168Cd00001014sv*sd*bc*sc*i*
alias: pci:v000010B7d00000013sv*sd*bc*sc*i*
alias: pci:v0000A727d00000013sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000013sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000012sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000011sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000007sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000207sv*sd*bc*sc*i*
depends: mac80211
vermagic: 2.6.25.5 mod_unload PENTIUM4
parm: debug:uint
root@ root $ modprobe ath5k

root@ root $ ip addr add 192.168.30.1/24 broadcast + dev wlan0

root@ root $ iwconfig wlan0 mode monitor

root@ root $ iwconfig wlan0
wlan0 IEEE 802.11g Mode:Monitor Channel:0 Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@ root $ cd /tmp
root@ tmp $ ip link set wlan0 up

Try with channel hopping -

CH 1 ][ Elapsed: 2 mins ][ 2008-06-11 12:40

BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID



root@ tmp $ iwconfig wlan0 channel 6
root@ tmp $ tcpdump -s0 -i wlan0 -vv -A
tcpdump: listening on wlan0, link-type IEEE802_11_RADIO (
BSSID STATION PWR Rate Lost Packets Probes

^C

Now try a specific channel. I know ch6 has traffic because the other
station is seeing it.


802.11 plus BSD radio information header), capture size 65535 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
root@ tmp $

Nothing. Not even an invalid/broken packet this time.


--
[** America, the police state **]
Whoooose! What's that noise? Why, it's US citizen's
rights, going down the toilet with Bush flushing.
http://www.theregister.co.uk/2008/01/27/bush_nsa_internal/
http://www.wired.com/politics/security/news/2007/08/wiretap
http://www.hermes-press.com/police_state.htm
http://www.privacyinternational.org/article.shtml?cmd%5B347%5D=x-347-559597

.

Relevant Pages

  • Re: IPMP enabled serious Network Problems
    ... inet 10.xx.xx.49 netmask ffffff00 broadcast xxxxxxx.255 ... Turn off this option to track all network interfaces ... input packets with dribble condition detected ...
    (comp.unix.solaris)
  • Re: Strange raid behaviour
    ... Hi Gilboa, ... [root@nucoda root]# ... BLKRASET: Invalid argument ...
    (Fedora)
  • Re: pinging without root privileges
    ... > feasible, since I want to be able to do this w/out root privileges, so ... > The closest thing I found was a promise about sending UDP packets to ... > an unbound port, and looking for a port unreachable message. ... > weakness of UDP is that the sender has no way of knowing what happened ...
    (comp.unix.programmer)
  • Re: Strange raid behaviour
    ... Hi Gilboa, ... [root@nucoda root]# ... BLKRASET: Invalid argument ...
    (Fedora)
  • Re: if_bge driver problem. - Upgrade to RELEASE :)
    ... I also added the tcpdump; before starting out tcpdump I initiated a ping xxx.yyy.2.1 for the outgoing messages. ... pfctl: pf not enabled ... 95 packets received by filter ...
    (freebsd-stable)