Re: LOR wlan0 wi0

On Sat, 08 Aug 2009 22:27:07 -0700
Sam Leffler <sam_at_errno.com> wrote:

> Robert wrote:
> > On Sat, 08 Aug 2009 08:59:27 -0700
> > Sam Leffler <sam_at_errno.com> wrote:
> > 
> >> Robert wrote:
> >>> Greetings
> >>>
> >>> I have just upgraded a laptop on my network to current:
> >>>
> >>> [root_at_hp] ~# uname -a
> >>> FreeBSD hp.shasta204.local 8.0-BETA2 FreeBSD 8.0-BETA2 #1: Fri Aug
> >>> 7 11:15:24 PDT 2009     root_at_vaio.shasta204.local:/usr/ob
> >>> j/usr/src/sys/VESA  i386
> >>>
> >>> I have made the changes in rc.conf after reading UPDATING and
> >>> rc.conf defaults. Here is the bits from rc.conf
> >>>
> >>> wlans_wi0=wlan0   # I have tried with quotes around wlan0 with 
> >>>                   # no difference. 
> >>> ifconfig_wlan0="DHCP ssid MY_SSID channel any wepmode on \
> >>> deftxkey 1 wepkey 0xSecretNumber78bf" 
> >>>
> >>> # ifconfig_re0="DHCP"
> >>>
> >>> My wlan0 interface comes up but never retrieves an IP from the
> >>> router. 
> >>>
> >>> [root_at_hp] ~# ifconfig -a
> >>> plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
> >>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
> >>>         options=3<RXCSUM,TXCSUM>
> >>>         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> >>>         inet6 ::1 prefixlen 128
> >>>         ether 00:09:5b:25:5e:b3
> >>>         media: IEEE 802.11 Wireless Ethernet autoselect mode 11b
> >>>         status: associated
> >>> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
> >>> mtu 1500 ether 00:09:5b:25:5e:b3
> >>>         inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> >>>         media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11b
> >>>         status: associated
> >>>         ssid MY_SSID channel 11 (2462 Mhz 11b) bssid
> >>> 00:1c:df:f9:ad:fc country US authmode OPEN privacy ON deftxkey 1
> >>> wepkey 1:104-bit txpower 0 bmiss 7 scanvalid 60
> >>>
> >>> Searching dmesg I see this
> >>>
> >>> wlan0: Ethernet address: 00:09:5b:25:5e:b3
> >>> lock order reversal:
> >>>  1st 0xc2c04014 wi0_com_lock (wi0_com_lock)
> >>> _at_ /usr/src/sys/net80211/ieee80211_scan.c:806 2nd 0xc2bf2008 wi0
> >>> (network driver) _at_ /usr/src/sys/dev/wi/if_wi.c:1083 KDB: stack
> >>> backtrace:
> >>> db_trace_self_wrapper(c0c7746e,cca4ea78,c08c1435,c08b217b,c0c7a303,...)
> >>> at db_trace_self_wrapper+0x26
> >>> kdb_backtrace(c08b217b,c0c7a303,c292f228,c2929040,cca4ead4,...) at
> >>> kdb_backtrace+0x29
> >>> _witness_debugger(c0c7a303,c2bf2008,c2af88d0,c2929040,c0c6775c,...)
> >>> at _witness_debugger+0x25
> >>> witness_checkorder(c2bf2008,9,c0c6775c,43b,0,...) at
> >>> witness_checkorder+0x839
> >>> _mtx_lock_flags(c2bf2008,0,c0c6775c,43b,c2bf2008,...) at
> >>> _mtx_lock_flags+0xc4
> >>> wi_raw_xmit(c2cc5000,c2cd0000,cca4ebba,10,c2c9c2a4,...) at
> >>> wi_raw_xmit+0x3e
> >>> ieee80211_send_probereq(c2cc5000,c2c9c2a4,c0bfd600,c0bfd600,c2ac2018,...)
> >>> at ieee80211_send_probereq+0x488
> >>> ieee80211_probe_curchan(c2c9c000,0,c0c8aa85,326,cca4ec30,...) at
> >>> ieee80211_probe_curchan+0x93
> >>> scan_curchan(c2ac2000,190,c0c8aa85,396,246,...) at
> >>> scan_curchan+0x49 scan_task(c2ac2000,1,c0c78c6a,54,c2af4d1c,...)
> >>> at scan_task+0x33a
> >>> taskqueue_run(c2af4d00,c2af4d1c,0,c0c6a13b,0,...) at
> >>> taskqueue_run+0x10b
> >>> taskqueue_thread_loop(c2c04074,cca4ed38,c0c6f7cc,33e,c0dc60a0,...)
> >>> at taskqueue_thread_loop+0x68
> >>> fork_exit(c08ba5b0,c2c04074,cca4ed38) at fork_exit+0xb8
> >>> fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp
> >>> = 0xcca4ed70, ebp = 0 --- Starting Network: lo0.
> >>>
> >>> The PCMCIA is and older Netgear 802.11b that was working fine on 7
> >>> stable. I have searched the archives and tried changing things in
> >>> rc.conf but I can not seem to make this work.
> >>>
> >>>
> >>> Any help or direction will be greatly appreciated.
> >> Ignore the LOR.  The first thing to do is simplify your config;
> >> remove crypto.  If you can pass data frames then your problem is in
> >> the crypto setup.  If not then you have unencrypted data to examine
> >> for problems.
> >>
> >> Use tools/tools/net80211/wlanstats to check for errors.  You can
> >> trace packet traffic with tcpdump to see if frames are moving.
> >>
> >> You also don't identify your card.  wi in 8.0 works with a subset
> >> of the cards in RELENG_7 so your card may not work
> >> correctly--though since you appear to have associated that doesn't
> >> seem like the issue (cards that don't work are unlikely to
> >> successfully associate).
> >>
> >> 	Sam
> > 
> > Sam
> > 
> > Thanks for responding and for all of the fine work you are doing.
> > 
> > I thought that I had tried without the crypto before but I either
> > didn't or messed up. Anyway, The interface links up fine without WEP
> > activated.
> > 
> > I am able to get on the network and NFS loads all file systems from
> > other boxes.
> > 
> > Re-enabling WEP on the router (Belkin) and in rc.conf, causes the
> > same failure as show above: associated without an IP.
> > 
> > The interface card is old. It shows to be a Netgear MA401. I have
> > ordered a newer model of the Netgear card. It is a WG511T which is
> > supposed to have an atheros chipset. I should receive this card in
> > about a week. I really do not know if any of this is relevant to my
> > problem.
> > 
> > On this laptop, because it is old and slow, I NFS mount /usr/src
> > from a faster machine. So, wlanstats is not available when I do not
> > have an IP.
> > 
> > Running tcpdump -vv shows a whole lot of stuff. It starts with
> > wlan0: no IPv4 assigned, so I do not know if the rest is important.
> > There are many lines which contain "Unknown SSAP" and "Unknown
> > DSAP". I have copied some of it to a file which I can forward if it
> > of any help.
> 
> I can confirm WEP is broken on wi in sta mode (and probably ap
> mode).  I found at least two bugs but couldn't get it to work so am
> going to leave it as an errata for 8.0.  But what's truly odd is that
> WPA works fine despite a bug that should've caused it to not work.  I
> knew WPA worked which is probably why I ignored WEP (noone in their
> right mind  uses WEP when WPA is available :-)).
> 
> 	Sam
Sam

I never claimed to be in my right mind. I haven't been myself since I
quit smoking in 1986. :-)

I tried WPA yesterday before answering the previous email. I kept
getting and error stating: unable to start wpa_supplicant.

I was thinking (always dangerous) that this old card maybe didn't have
support for WPA. I'm probably wrong since I am not in my right mind. I
was going to try again when the WG511T arrives. But now I will try
again.

Thanks again

Robert