From owner-freebsd-current@FreeBSD.ORG Fri Mar 5 11:08:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id A69FB16A4CF; Fri, 5 Mar 2004 11:08:14 -0800 (PST) In-Reply-To: <20040305012447.GA774@cactus.homeunix.org> from "jqdkf@army.com" at "Mar 5, 2004 09:24:47 am" To: jqdkf@army.com Date: Fri, 5 Mar 2004 11:08:14 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040305190814.A69FB16A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: current@freebsd.org Subject: Re: adhoc doesn't work with centrino X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 05 Mar 2004 19:08:14 -0000 > Hi, > > My wireless card is "Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter". > With ndiswrapper, it works fine in BSS mode, but I can't make it work in > adhoc mode. Here is my configuration: > > $ ifconfig ndis0 inet 10.0.0.1 netmask 255.255.255.0 \ > ssid CACTUS mode 11b mediaopt adhoc up [...] Uhm... leave out the "mode 11b" part. You don't have to do anything to force 11b mode (especially since most Centrino NICs are 11b only anyway). Just do: # ifconfig ndis0 inet 10.0.0.1 netmask 255.255.255.0 \ ssid CATCUS mediaopt adhoc up I have gotten ad-hoc mode to work on the Centrino with my home network (it was the first thing I tested) so you ought to be able to get it to connect. Be wary of getting too clever with setting media options with ifconfig on if_ndis at this point: it needs work. The two things which I know will work are: # ifconfig ndis0 mediaopt adhoc <-- select adhoc mode # ifconfig ndis0 media autoselect <-- select BSS mode If it doesn't associate right away, you might try doing "ifconfig ndis0 down; ifconfig ndis0 up" once or twice to reset it, though in my tests I don't think this was necessary. Also, the only useful thing you can do with wicontrol(8) at this point is an AP scan: # wicontrol -i ndis0 -l The only reason wicontrol does this is... er... well... we don't have any other standard utility in FreeBSD that can do it. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose =============================================================================