[Madwifi-users] Strage state of ath0 after playing a while with kismet

[<be...@ga...>]

Hi there.

I'm totally new to the atheros-wifi-land (got my 3Com 3CRPAG175 yesterday)
and experienced some strange problems with the madwifi-drivers in
kombination with kismet.
The first problem seems to be a known problem (NETDEV WATCHDOG: ath0:
transmit timed out), the second is totally new to me and I haven't found =
any
references on this yet.

If I quit kismet the device stays in "Monitor"-mode. I may do something
completely stupid here, but I tried to "fix" that with
iwconfig ath0 mode managed

After that I happened to look at this:

$ifconfig ath0
ath0      Link encap:UNSPEC  HWaddr
00-0D-54-98-EF-90-00-54-00-00-00-00-00-00-00-00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:178 errors:22167 dropped:0 overruns:0 frame:22167
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199
          RX bytes:65066 (63.5 Kb)  TX bytes:92 (92.0 b)
          Interrupt:11 Memory:de9a9000-de9b9000

Looks quite strange.. Especially the link encapsulation and the hardware
address.. Am I doing something terribly wrong?

Thanks for any hints,
Ben