On 26 October 2015 at 01:27, Lev Serebryakov wrote:
> Hello NGie,
>
> Sunday, October 25, 2015, 11:09:03 PM, you wrote:
>
>
>> Ok, this is really not making sense from a design perspective.
>> `ifconfig_` is being overloaded for starting up hostap’s (even though
>> ifconfig
Hello NGie,
Sunday, October 25, 2015, 11:09:03 PM, you wrote:
> Ok, this is really not making sense from a design perspective.
> `ifconfig_` is being overloaded for starting up hostap’s (even though
> ifconfig itself doesn’t support hostap — only `wlanmode ap`). I don’t
ifconfig doesn't
On Monday, October 26, 2015 04:38:21 AM Adrian Chadd wrote:
> On 26 October 2015 at 01:27, Lev Serebryakov wrote:
> > Hello NGie,
> >
> > Sunday, October 25, 2015, 11:09:03 PM, you wrote:
> >
> >
> >> Ok, this is really not making sense from a design perspective.
> >>
Hm, poke glebius? He went and rototilled bits of net80211 recently and
that did touch the rc scripts.
-a
On 25 October 2015 at 12:20, Lev Serebryakov wrote:
> Hello freebsd-current,
>
>
> New version of -CURRENT try to configure wlan0 and run hostapd twice:
>
> Created
> On Oct 25, 2015, at 12:39, Lev Serebryakov wrote:
>
> Hello NGie,
>
> Sunday, October 25, 2015, 10:30:47 PM, you wrote:
>
>
>> This [the hostapd start/stop logic] all gets triggered whenever the
>> interface goes up and down.
> So, first time hostapd is started by
Hello NGie,
Sunday, October 25, 2015, 10:45:10 PM, you wrote:
> It depends on how it’s setup. Is your interface is using DHCP and are you
> using the stock devd.conf file? From etc/devd.conf:
devd.conf is stock one, but, of course, HOSTAP-interface uses static
address. One more time:
> On Oct 25, 2015, at 12:54, NGie Cooper wrote:
...
> I’ll need to double-check the rcorder and get back to you on that.
Answering this part: nope. devd still gets started after netif on my branch, so
it’ll still start hostapd twice:
$ rcorder `make -VFILES
> On Oct 25, 2015, at 12:58, NGie Cooper wrote:
>
>
>> On Oct 25, 2015, at 12:54, NGie Cooper wrote:
>
> ...
>
>> I’ll need to double-check the rcorder and get back to you on that.
>
> Answering this part: nope. devd still gets started after
Hello freebsd-current,
New version of -CURRENT try to configure wlan0 and run hostapd twice:
Created wlan(4) interfaces: wlan0.
Created clone interfaces: gif0.
em0: link state changed to UP
em0: link state changed to DOWN
ifconfig: NONE: bad value
vlan0: changing name to 'skynet'
vlan1:
> On Oct 25, 2015, at 12:20, Lev Serebryakov wrote:
>
> Hello freebsd-current,
>
>
> New version of -CURRENT try to configure wlan0 and run hostapd twice:
>
> Created wlan(4) interfaces: wlan0.
> Created clone interfaces: gif0.
> em0: link state changed to UP
> em0: link
Hello NGie,
Sunday, October 25, 2015, 10:30:47 PM, you wrote:
> This [the hostapd start/stop logic] all gets triggered whenever the interface
> goes up and down.
So, first time hostapd is started by /etc/rc.d/netif before devd, and
second time devd call /etc/rc.d/netif again on interface
> On Oct 25, 2015, at 12:30, NGie Cooper wrote:
…
> 445 # hostapif if
> 446 # Returns 0 if the interface is a HOSTAP interface and 1 otherwise.
> 447 hostapif()
> 448 {
> 449 local _tmpargs _arg
> 450 _tmpargs=`_ifconfig_getargs $1`
> 451
> 452
Hello NGie,
Sunday, October 25, 2015, 10:39:51 PM, you wrote:
> It’s documented here:
> On the other hand, if you want to configure your wireless
> interface with hostapd(8), you need to add ``HOSTAP'' to the
> ifconfig_ variable. hostapd(8)
> On Oct 25, 2015, at 12:46, Lev Serebryakov wrote:
>
> Hello NGie,
>
> Sunday, October 25, 2015, 10:39:51 PM, you wrote:
>
>
>> It’s documented here:
>
>> On the other hand, if you want to configure your wireless
>> interface with
14 matches
Mail list logo