From owner-freebsd-current@FreeBSD.ORG Thu May 8 15:19:44 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 764DD106564A; Thu, 8 May 2008 15:19:44 +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 0BA6C8FC17; Thu, 8 May 2008 15:19:43 +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 m48FJd7Q034117; Thu, 8 May 2008 17:19:39 +0200 (CEST) (envelope-from ted@omval.tednet.nl) Received: (from ted@localhost) by omval.tednet.nl (8.14.2/8.14.2/Submit) id m48FJd7t034116; Thu, 8 May 2008 17:19:39 +0200 (CEST) (envelope-from ted) Message-Id: <200805081519.m48FJd7t034116@omval.tednet.nl> From: ted@tednet.nl (Ted Lindgreen) Date: Thu, 8 May 2008 17:19:39 +0200 In-Reply-To: "Coleman Kane's message as of May 8, 16:49" X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Coleman Kane , Ted Lindgreen X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (omval.tednet.nl [127.0.0.1]); Thu, 08 May 2008 17:19:39 +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 17:21:24 +0000 Cc: freebsd-current@freebsd.org, Andrew Thompson 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 15:19:44 -0000 [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. 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. 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. regards, -- ted