Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Oct 2015 10:58:12 -0700
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-current@freebsd.org
Cc:        Adrian Chadd <adrian.chadd@gmail.com>, Lev Serebryakov <lev@freebsd.org>, NGie Cooper <yaneurabeya@gmail.com>
Subject:   Re: What changed in rc.d infrastructure in last months?
Message-ID:  <10965004.5DFcuHMnDm@ralph.baldwin.cx>
In-Reply-To: <CAJ-VmomdSBD93dtnVfqNCc%2BNGknrcGsyW66_QeEcUMyHhPqmVA@mail.gmail.com>
References:  <16610120144.20151025222025@serebryakov.spb.ru> <1648746569.20151026112745@serebryakov.spb.ru> <CAJ-VmomdSBD93dtnVfqNCc%2BNGknrcGsyW66_QeEcUMyHhPqmVA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, October 26, 2015 04:38:21 AM Adrian Chadd wrote:
> On 26 October 2015 at 01:27, Lev Serebryakov <lev@freebsd.org> 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_<foo>` is being overloaded for starting up hostap=E2=80=99=
s (even though
> >> ifconfig itself doesn=E2=80=99t support hostap =E2=80=94 only `wla=
nmode ap`). I don=E2=80=99t
> >  ifconfig doesn't support dhcp either, but dhclient is run via "DHC=
P" in
> >  `ficonfig_<foo>`
> >
> >> understand why it was done this way instead of just creating addit=
ional
> >> variables for `hostapd_<foo>`
> >  Long time ago there was simple `hostapd_enable` and `hostapd_inter=
faces` :)
> >  But it doesn't allow to automagically start hostapd for hotplugged=
 (i.e.
> >  USB) interfaces. On the other hand, automatic DHCP on hot-plugged
> >  interfaces have sense and automatic hostapd doesn't, IMHO.
>=20
> This sounds like the same issue as double-running wpa_supplicant.
>=20
> I thought this was fixed already :( Would someone please figure out a=

> cleanish solution to this? I'd really appreciate it.

Note that /etc/pccard_ether bails right away if the interface is marked=
 up
without doing anything.  That is what is supposed to make devd events a=
t
boot get ignored.  (See the initial loop in pccard_ether_start().)

--=20
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10965004.5DFcuHMnDm>