From owner-freebsd-current@FreeBSD.ORG Thu May 8 14:09:06 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC9C2106566C for ; Thu, 8 May 2008 14:09:06 +0000 (UTC) (envelope-from ted@omval.tednet.nl) Received: from omval.tednet.nl (omval.tednet.nl [IPv6:2001:7b8:206:1:200:39ff:fe59:b187]) by mx1.freebsd.org (Postfix) with ESMTP id 545688FC2E for ; Thu, 8 May 2008 14:09:06 +0000 (UTC) (envelope-from ted@omval.tednet.nl) Received: from omval.tednet.nl (localhost [127.0.0.1]) by omval.tednet.nl (8.14.2/8.14.2) with ESMTP id m48E92vI033753; Thu, 8 May 2008 16:09:02 +0200 (CEST) (envelope-from ted@omval.tednet.nl) Received: (from ted@localhost) by omval.tednet.nl (8.14.2/8.14.2/Submit) id m48E91tS033752; Thu, 8 May 2008 16:09:01 +0200 (CEST) (envelope-from ted) Message-Id: <200805081409.m48E91tS033752@omval.tednet.nl> From: ted@tednet.nl (Ted Lindgreen) Date: Thu, 8 May 2008 16:09:01 +0200 X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-current@freebsd.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (omval.tednet.nl [127.0.0.1]); Thu, 08 May 2008 16:09:02 +0200 (CEST) X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on omval.tednet.nl X-Mailman-Approved-At: Thu, 08 May 2008 14:19:34 +0000 Cc: Ted Lindgreen Subject: Problem ndis and 11b since May 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2008 14:09:06 -0000 Hi, Since May 1 my Broadcom BCM43 wlan interface, using the ndis-driver, does not associate with my (old) Apple Airport anymore. 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. 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. regards, -- ted