From owner-freebsd-current@FreeBSD.ORG Thu May 8 20:27:09 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 B5EE51065676; Thu, 8 May 2008 20:27:09 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 74A988FC37; Thu, 8 May 2008 20:27:09 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m48KR8EM025023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 May 2008 13:27:09 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <4823621C.1040609@freebsd.org> Date: Thu, 08 May 2008 13:27:08 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Ted Lindgreen References: <200805081519.m48FJd7t034116@omval.tednet.nl> In-Reply-To: <200805081519.m48FJd7t034116@omval.tednet.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org, Andrew Thompson , Coleman Kane Subject: Re: 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 20:27:09 -0000 Ted Lindgreen wrote: > [Quoting Coleman Kane, on May 8, 16:49, in "Re: Problem ndis and ..."] > ... > >> 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 don't think it is related. I think you problem relates to order of the > various configurations. > Actually I disagree; I suspect there is an issue in ndis as it is presently the only "user of net80211" left that fondles the internal data structures. In the past (haven't looked recently) ndis has also tried to simulate internal work of net80211 to provide a match between the ndis driver and net80211--usually with problems like what's been described. > Yes, I have been following Sam's work and it is not trivial to set > things up. Especially when you want to connect to various > access-points with different interface (f.i. a USB with large antenne > on my ship and the internal one else) depending on where you are. > > I have tried the /etc/rc.conf advice, but that didn't work for me, so > I reverted to the trick of /etc/start_if_ndis0 and /etc/start_if_zyd0 > scripts which in turn call a /etc/start_if_wireless script. > FWIW I'm not happy w/ the rc.conf stuff. I suggest you talk to Brooks about your difficulties (I have passed along suggestions). > For your (and perhaps other interested people) information, my start file > looks like (this is a shortened version, the real version loops through > various other accesspoints): > --- > #!/bin/sh > #set -x > > #To be called by the start_if. scripts with as argument > > INTFs=`ifconfig -l` > > # Do not attempt to start ndis0 when zyd0 is present > if ( echo $INTFs | grep --quiet 'zyd0' ) > then > ifconfig ndis0 down > if [ "$1" = "ndis0" ] > then > echo $0 $*: "zyd0 found, exit 1 for ndis0" > exit 1 > fi > echo $0 $*: "zyd0 found, ifconfig ndis0 down" > fi > > if ( echo $INTFs | grep --quiet 'wlan0' ) > then > : Has already been created > else # Create wlan interface > ifconfig wlan0 create wlandev $1 > ifconfig wlan0 country NL > fi > > for SLEEP in 2 4 8 > do > echo "Try: Omval Airport" > ifconfig wlan0 ssid "Omval Airport" nwkey 0x********** up > sleep $SLEEP > if ( ifconfig wlan0 | grep --quiet 'associated' ) > then > /etc/rc.d/dhclient start wlan0 > exit 0 > fi > > echo "Try: WiFi buiten" > ifconfig wlan0 ssid "WiFi buiten" nwkey 0x********** up > sleep $SLEEP > if ( ifconfig wlan0 | grep --quiet 'associated' ) > then > /etc/rc.d/dhclient start wlan0 > exit 0 > fi > > done > > # Else, do not try to bring up the wireless > > echo $0 $*: "no association, shutdown $1" > ifconfig $1 down > exit 1 > --- > > Perhaps someone likes this idea, perhaps someother hints us to > something far more easier and/or clever than this. > Handling multiple wireless devices is not well supported right now. If you only ever have one device hooked up at a time then it should be easy to deal with. If you have multiple then it can be handled with the recent routing additions to HEAD (and which can also help the wired/wireless issues). But I make no claims that there are good auto-configuration services at the moment. Sam