Date: Thu, 25 Sep 2008 16:41:30 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: "John Hay" <jhay@meraka.org.za> Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode Message-ID: <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> In-Reply-To: <20080922132500.GA25677@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/22/08, John Hay <jhay@meraka.org.za> wrote: > Hi > > I'm trying out the new ath/wlan stuff in current. Should one still be > able to set the bssid in adhoc mode? We normally lock the bssid in > an adhoc network because of problems that the network split and does > not merge, if you do not do it. > > What I have done is this: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > # ifconfig wlan0 ssid ptamesh up > > Up to here works well. It will scan and if it finds another node with the > same ssid, it will "lock" on that channel and use the correct bssid. > > If it does not find another node with the same ssid, it will start it > own thing on channel 10. But it looks like one cannot set the bssid. > > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > ifconfig: 02:07:ca:fe:ba:be: bad value I had similar experience with STA mode, instead I use ap (ap is alias for bssid, at least it works in STA mode) I never bothered is this bug in manual page, ifconfig or in something else ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750809250741j7b9003e4q539618d1c9407def>