new wi driver problems

2003-01-18 Thread David Thiel
A couple things regarding this new wireless driver - the
wepkey option to ifconfig no longer seems to work; I get a 
"SIOCS80211: Invalid argument".  Secondly and more importantly,
even when the wepkey is set via wicontrol, I can't seem to get 
any connectivity at all anymore.

ifconfig wi0:

flags=8843 mtu 1500
inet6 fe80::202:2dff:fe0c:ec4b%wi0 prefixlen 64 scopeid 0x3
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
ether 00:02:2d:0c:ec:4b
media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps)
status: associated
ssid myssid 1:myssid
stationname "FreeBSD WaveLAN/IEEE node"
channel 7 authmode OPEN powersavemode OFF powersavesleep 100
wepmode MIXED weptxkey 1
wepkey 1:128-bit

dmesg:

wi0:  at port 0x100-0x13f irq 11 function 0 config 1 on pccard0
wi0: 802.11 address: 00:02:2d:0c:ec:4b
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent Firmware: Station (7.52.1)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps

uname:

FreeBSD sartre.redundancy.org 5.0-CURRENT FreeBSD 5.0-CURRENT #5: Fri Jan 17 12:15:30 
PST 2003  root@:/usr/obj/user/src/sys/SARTRE  i386

But I'm unable to ping my gateway, a -STABLE box with the same card.  I
did recompile with device wlan, and tried the generic kernel as well. 
Disabling WEP has no effect.

Could someone give me a pointer as to how to debug this?

Thanks,
David


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: new wi driver problems

2003-01-18 Thread Sam Leffler
> A couple things regarding this new wireless driver - the
> wepkey option to ifconfig no longer seems to work; I get a
> "SIOCS80211: Invalid argument".  Secondly and more importantly,
> even when the wepkey is set via wicontrol, I can't seem to get
> any connectivity at all anymore.
>

I fixed the setting of the wepkey by ifconfig but still have to track down
why wep doesn't work (looks like xmit is fine but rcvd packets are being
dropped by the card).  FWIW you can enable debugging info for the 802.11
state machine with:

sysctl debug.ieee80211=1

and get 802.11 frames by the driver printed with:

ifconfig wi0 debug link2

Setting the sysctl value to >1 will give more verbose output which is
unlikely to be useful.  I have to commit some mods to tcpdump and bpf before
you can use tcpdump to tap packets at the 802.11 link layer.

Sam


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message