Date: Thu, 08 May 2008 10:37:29 -0400 From: Coleman Kane <cokane@FreeBSD.org> To: Ted Lindgreen <ted@tednet.nl> Cc: freebsd-current@freebsd.org, Andrew Thompson <thompsa@FreeBSD.org> Subject: Re: Problem ndis and 11b since May 1 Message-ID: <1210257449.1745.11.camel@localhost> In-Reply-To: <200805081409.m48E91tS033752@omval.tednet.nl> References: <200805081409.m48E91tS033752@omval.tednet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-NYV5vOZ9gbRyiQc5GS8U Content-Type: multipart/mixed; boundary="=-DFZEV97glnf/CS+E+INH" --=-DFZEV97glnf/CS+E+INH Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2008-05-08 at 16:09 +0200, Ted Lindgreen wrote: > Hi, >=20 > Since May 1 my Broadcom BCM43 wlan interface, using the ndis-driver, > does not associate with my (old) Apple Airport anymore. >=20 > Working out the various changes, I found that a change in if_ndis.c > from version 1.135 to 1.136 caused the problem. In other words: > a kernel, generated from an uptodate source as of May 7 does not > associate, by only reverting if_ndis.c to version 1.135 produces > a kernel that works fine as ever before. >=20 > Further info: there is NO problem with a few other access-points I > have access to. One of the differences between the Airport and the > other access-points is that the old Airport supports only 11b, while > the others support both 11b and 11g. I'm not sure, of course, but it > looks like the change between 1.135 and 1.136 forces the ndis-driver > into 802.11g mode exclusively. >=20 > regards, > -- ted >=20 Hi Ted, I've been talking to Andrew Thompson about a similar problem recently. I'm not sure if it is related, but it did keep me from being able to associate to anything. I am attaching a patch that has worked for me. Maybe it will work for you too. The problem I found is that wpa_supplicant needs to be run (against wlan0, using ndis driver) after the ndis0 interface has been upped. Additionally, if you are trying to manually ifconfig the interface, I have found that after a boot you'll need to ifconfig down, then ifconfig up the ndis0 before you attempt to do any associating with the wlan0 interface. Additionally, bringing wlan0 down/up/down/up/..., checking associated status after each up until it works has helped me in the manual case. A good way to discern whether wlan0 will associate (or needs to be kicked) will be to run "ifconfig wlan0 scan". If it hangs forever, then it didn't work... However... you listed your AP as 802.11b, and mine is 802.11g, so YMMV. Make sure that you're using (in /etc/rc.conf): wlans_ndis0=3D"wlan0" ifconfig_wlan0=3D"WPA" You may want to read /usr/src/UPDATING for a summary of what has changed and what needs to be done about it, if you haven't already followed those instructions. --=20 Coleman Kane --=-DFZEV97glnf/CS+E+INH Content-Disposition: attachment; filename=wpa_supplicant-ndis-wlan.patch Content-Type: text/x-patch; name=wpa_supplicant-ndis-wlan.patch; charset=UTF-8 Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL2V0Yy9yYy5kL3dwYV9zdXBwbGljYW50IGIvZXRjL3JjLmQvd3BhX3N1cHBs aWNhbnQNCmluZGV4IDYzMTQyNzguLjFkM2Q0ZGMgMTAwNjQ0DQotLS0gYS9ldGMvcmMuZC93cGFf c3VwcGxpY2FudA0KKysrIGIvZXRjL3JjLmQvd3BhX3N1cHBsaWNhbnQNCkBAIC0xMSw2ICsxMSw3 IEBADQogLiAvZXRjL25ldHdvcmsuc3Vicg0KIA0KIG5hbWU9IndwYV9zdXBwbGljYW50Ig0KK3Bh cmVudD0NCiByY3Zhcj0NCiANCiBpZm49IiQyIg0KQEAgLTMzLDcgKzM0LDExIEBAIGlzX3dpcmVk X2ludGVyZmFjZSgpDQogaXNfbmRpc19pbnRlcmZhY2UoKQ0KIHsNCiAJY2FzZSBgc3lzY3RsIC1u IG5ldC53bGFuLiR7MSN3bGFufS4lcGFyZW50IDI+L2Rldi9udWxsYCBpbg0KLQkJbmRpcyopIHRy dWUgOzsNCisJCW5kaXMqKQ0KKwkJCXBhcmVudD1gc3lzY3RsIC1uIG5ldC53bGFuLiR7MSN3bGFu fS4lcGFyZW50IDI+XA0KKwkJCQkvZGV2L251bGxgDQorCQkJdHJ1ZQ0KKwkJOzsNCiAJCSopIGZh bHNlIDs7DQogCWVzYWMNCiB9DQpAQCAtNDIsNiArNDcsNyBAQCBpZiBpc193aXJlZF9pbnRlcmZh Y2UgJHtpZm59IDsgdGhlbg0KIAlkcml2ZXI9IndpcmVkIg0KIGVsaWYgaXNfbmRpc19pbnRlcmZh Y2UgJHtpZm59IDsgdGhlbg0KIAlkcml2ZXI9Im5kaXMiDQorCWlmY29uZmlnICR7cGFyZW50fSB1 cA0KIGVsc2UNCiAJZHJpdmVyPSJic2QiDQogZmkNCg== --=-DFZEV97glnf/CS+E+INH-- --=-NYV5vOZ9gbRyiQc5GS8U Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkgjECcACgkQcMSxQcXat5fvbgCfeQdX9ggp76Dc2YVDXO/aeWyC h7wAnRJKfDbwXvXGZfmvNYSzWQByXMM6 =F2g9 -----END PGP SIGNATURE----- --=-NYV5vOZ9gbRyiQc5GS8U--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1210257449.1745.11.camel>