Date: Tue, 17 Jan 2006 19:26:37 +0100 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: Bill Paul <wpaul@FreeBSD.ORG> Cc: freebsd-stable@freebsd.org Subject: Re: ndis0 does not associate since update to RELENG_6 Message-ID: <20060117192637.540a72c6@localhost> In-Reply-To: <20060117173145.78DF416A420@hub.freebsd.org> References: <20060117150024.45318963@localhost> <20060117173145.78DF416A420@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_Ma33eM=gKfW/B3DY4Ww+84T Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable wpaul@FreeBSD.ORG (Bill Paul) wrote: > > I fail to get the following device working since my update > > from RELENG_5 to RELENG_6 a few days ago: > >=20 > > ndis0@pci2:2:0: class=3D0x028000 card=3D0x27128086 chip=3D0x42208086 > > rev=3D0x05 hdr=3D0x00 vendor =3D 'Intel Corporation' > > device =3D 'PRO/Wireless 2200BG Network Connection' > > class =3D network > >=20 > > It worked fine with 5.4 and was recognised as > >=20 > > ndis0: <Intel(R) PRO/Wireless 2200BG Network Connection> mem > > 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci > > ndis0: NDIS API version: 5.0 > > ndis0: Ethernet address: 00: ... :00 > > ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps > > ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps > > 54Mbps > >=20 > > On 6.0 it is still recognised, but the last two lines are missing. >=20 > That's normal. > =20 > > I'm using GENERIC, the driver module was generated with ndisgen > > out of w22n51.inf and w22n50.sys. This is the combination I alway > > used.=20 > >=20 > > ndis0 can scan for access points, but can't associate with or > > without WEP encryption. >=20 > What command do you type to try to get it to associate? kldload wlan_wep.ko kldload w22n50_sys.ko ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up =20 > > fk@TP51 ~ $ifconfig ndis0 list scan > > SSID BSSID CHAN RATE S:N INT CAPS > > ec60bfg3b4 00: ... :a8 11 54M 149:0 100 > > EP ??? ??? ??? ??? ??? ??? WME > >=20 > > fk@TP51 ~ $ifconfig ndis0 > > ndis0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > inet 192.168.0.32 netmask 0xffffff00 broadcast 192.168.0.255 > > inet6 fe80: ... :7500%ndis0 prefixlen 64 scopeid 0x5=20 > > ether 00: ... :00 > > media: IEEE 802.11 Wireless Ethernet autoselect > > status: no carrier > > ssid "" channel 1 > > authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit > > txpowmax 100 protmode CTS > >=20 > > I found a similar problem which should be fixed in current, > > but I don't know if the changes already hit stable. =20 > > http://freebsd.rambler.ru/bsdmail/freebsd-current_2005/msg11802.html > >=20 > > My problem is not exactly the same though, I have no trouble setting > > the bssid.=20 >=20 > You should be able to do: >=20 > # ifconfig ndis0 ssid ec60bfg3b4 wepmode on wepkey "0123456789123" up It was my experience that ifconfig on 6.0 will not chose the first key by default. I always have to add deftxkey 1. I can't use your exact command because I know my wepkey only in hexadecimal. But if I disable WEP in the access point and use ifconfig ndis0 ssid ec60bfg3b4 up it fails to associate (or even to set the ssid) as well: root@TP51 ~ #ifconfig ndis0 =20 ndis0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet6 fe ... 7500%ndis0 prefixlen 64 scopeid 0x3=20 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel 1 authmode OPEN privacy OFF txpowmax 100 protmode CTS =20 > You don't state what command you actually use. You should have > specified it in your e-mail. Note that usually the WEP key has to be > either 5 or 13 characters. You're right, sorry. I use the hexadecimal notation and my key is correctly recognised as 104-bit. =20 ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up=20 The two commands above work for iwi0, wi0 and ath0.=20 I use the same shell script I used on 5.4. The only change I made was adding "deftxkey 1" which wasn't needed before.=20 > > Is anybody else using this device with FreeBSD 6.0? >=20 > I've tested the 2200BG myself with the NDISulator 6.0 and I've been > able to get it to associate with 11g networks. I don't know what's > wrong in your case. Is there a way I can provide more information? Fabian --=20 http://www.fabiankeil.de/ --Sig_Ma33eM=gKfW/B3DY4Ww+84T Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDzTbmjV8GA4rMKUQRAjYRAJwJ3IyrdboqvSwYnsHMstd5gty7owCgiXEK DCjkLle8tYaRy0f2qyzm3wg= =3iIS -----END PGP SIGNATURE----- --Sig_Ma33eM=gKfW/B3DY4Ww+84T--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060117192637.540a72c6>