atheros adhoc mode

Mon Sep 8 17:02:12 PDT 2003

Ok,

The kernel was built from CURRENT source checked out at about 17:00 HST on 
Aug 29 (03:00 Aug 30 GMT).  The mirror I use can be as much as three hours 
delayed from what I see on the commit messages.

I attempted to set the debug link2 as suggested and the link became too 
lossy for our code which then removes all routing through the ath card.  I 
also get lots of "ath0: hardware error; resetting" errors with the 
debugging set.

ifconfig from our ath0:

ath0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
         inet 10.0.0.5 netmask 0xffffffff broadcast 10.0.0.5
         inet6 fe80::202:6fff:fe20:2881%ath0 prefixlen 64 scopeid 0x4
         ether 00:02:6f:20:28:81
         media: IEEE 802.11 Wireless Ethernet autoselect <adhoc>
         status: associated
         ssid phop 1:phop
         channel 2 authmode OPEN powersavemode OFF powersavesleep 100
         wepmode OFF weptxkey 1

All other cards in this case are wi.

A snippet of the output from debug link2:
(the hardware errors happen about 3-4 more frequently with this set)

ath0: hardware error; resetting
NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M
  0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 8021 aaaa 0300 
0000 0800 4500 0034
  9206 0000 0111 3dac 0a00 0005 e000 0002 15b3 15b3 0020 0eb3 0101 fa00 
0a4d 0047 0303 fa00
  0a00 0059 c0a8 035a 0a4d 004b
NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M
  0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 9021 aaaa 0300 
0000 0800 4500 0034
  9506 0000 0111 3aac 0a00 0005 e000 0002 15b3 15b3 0020 0cb3 0101 fb00 
0a4d 0047 0303 fb00
  0a00 0059 c0a8 035a 0a4d 004b
ath0: hardware error; resetting
NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M
  0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 a021 aaaa 0300 
0000 0800 4500 0030
  9806 0000 0111 37b0 0a00 0005 e000 0002 15b3 15b3 001c cebe 0100 fc00 
0303 fc00 0a4d 0047
  0a00 0059 0a4d 004b
NODS 00:02:6f:04:2e:1c->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +40
  0800 0000 0100 5e00 0002 0002 6f04 2e1c 0202 9f4e 8fd7 30dd aaaa 0300 
0000 0800 4500 0024
  d6ac 0000 0111 f8c1 0a00 0059 e000 0002 15b3 15b3 0010 3306 0101 ac00 
0a00 0005 6ea7 954f
NODS 00:02:6f:04:2e:1e->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +11
  0800 0000 0100 5e00 0002 0002 6f04 2e1e 0202 9f4e 8fd7 d06a aaaa 0300 
0000 0800 4500 0020
  6920 0000 0111 6613 0a4d 004b e000 0002 15b3 15b3 000c 57d5 0100 9100 
9847 3193
NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M
  0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 b021 aaaa 0300 
0000 0800 4500 0028
  9b06 0000 0111 34b8 0a00 0005 e000 0002 15b3 15b3 0014 e1c1 0100 fd00 
0301 fd00 0a4d 0047
ath0: hardware error; resetting
NODS 00:02:6f:04:2e:37->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +34
  0800 0000 0100 5e00 0002 0002 6f04 2e37 0202 9f4e 8fd7 109e aaaa 0300 
0000 0800 4500 0024
  9d97 0000 0111 319c 0a4d 0047 e000 0002 15b3 15b3 0010 bdcb 0101 2100 
0a00 0005 731d bd04
NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M
  0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 c021 aaaa 0300 
0000 0800 4500 0028
  9e06 0000 0111 31b8 0a00 0005 e000 0002 15b3 15b3 0014 dfc1 0100 fe00 
0301 fe00 0a4d 0047
ath0: hardware error; resetting
NODS 00:02:6f:04:2e:1c->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +23
  0800 0000 0100 5e00 0002 0002 6f04 2e1c 0202 9f4e 8fd7 40df aaaa 0300 
0000 0800 4500 0020
  d6b5 0000 0111 f8bc 0a00 0059 e000 0002 15b3 15b3 000c 3a14 0100 af00 
78fe b21a
NODS 00:02:6f:04:2e:1e->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +11
  0800 0000 0100 5e00 0002 0002 6f04 2e1e 0202 9f4e 8fd7 e06c aaaa 0300 
0000 0800 4500 0030
  6929 0000 0111 65fa 0a4d 004b e000 0002 15b3 15b3 001c 0e2e 0100 9400 
2702 0000 0a4d 004b
  0a4d 0047 0a00 0059 91a1 078d
NODS 00:02:6f:04:2e:34->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +33
  0800 0000 0100 5e00 0002 0002 6f04 2e34 0202 9f4e 8fd7 e048 aaaa 0300 
0000 0800 4500 0020
  ebeb 0000 0111 29dd c0a8 035a e000 0002 15b3 15b3 000c ee6a 0100 4100 
daab b093
NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M
  0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 d021 aaaa 0300 
0000 0800 4500 0028
  a106 0000 0111 2eb8 0a00 0005 e000 0002 15b3 15b3 0014 d564 0102 ff00 
0a00 0059 0a4d 004b
ath0: hardware error; resetting

I don't have a kernel config available, but it's basically GENERIC with the 
following additions:

options      HZ=250
options      CLK_USE_I8254_CALIBRATION
options      CONSPEED=19200
options      IPFIREWALL
options      IPFIREWALL_DEFAULT_TO_ACCEPT
options      IPDIVERT
options      MROUTING
options      NO_SWAPPING

At 09:42 PM 9/7/2003 -0700, Sam Leffler wrote:
> > We're evaluating the Soekris 4801 and a 5212 based mini-PCI radio - It
> > works well enough in infrastructure mode, but I'm having problems with
> > adhoc.
> >
> > When the radio is operating in adhoc mode, I see multicast traffic, but
> > no unicast traffic.  However, if I run tcpdump on the ath interface I get
> > sporadic traffic.
> >
> > It's possible I'm still misconfigured, but the fact that putting the
> > interface into promiscuous mode changes the behavior of the interface
> > kinda points elsewhere.  We have this application running fine on 4521s
> > with both an & wi radios.
> >
> > Is this a known problem?
>
>No, but adhoc mode has not been well tested.  11a or 11b?  What version of
>the software?  Have you tried enabling debugging and packet dumping on the
>interface (ifconfig ath0 debug link2) to see what's happening?
>
>If you're getting multicast traffic but not unicast then it sounds like the
>BSSID isn't setup correctly--which was a very old bug.
>
>         Sam
>
>_______________________________________________
>freebsd-mobile at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
>To unsubscribe, send any mail to "freebsd-mobile-unsubscribe at freebsd.org"