Date: Tue, 21 Oct 2025 08:51:03 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: Cy Schubert <Cy.Schubert@cschubert.com>, "freebsd-wireless@freebsd.org" <wireless@freebsd.org> Subject: Re: wlan: UP but not RUNNING ? Message-ID: <CAJ-Vmoko9BcX3Vdz4hujf-y3y5gQmJqbCci0_5EG6FqJFe-3Ww@mail.gmail.com> In-Reply-To: <ede875c1-044f-407d-b2a6-2bcc55c974da@FreeBSD.org> References: <8ed936d2-242a-4dca-a38b-1117b41e87ef@FreeBSD.org> <6a2e22ae-b8f9-46de-8a0f-881d7c01ceb0@FreeBSD.org> <81321964-801f-497b-ab46-d8866401e900@FreeBSD.org> <CAJ-VmonbRK1-mVcHs83sHNQYwXqxoy3nAGiQDmJ0mNaBw_eP8A@mail.gmail.com> <fb65a8f3-bfa6-46a7-82ca-58eebbc65cff@freebsd.org> <c621ce9d-9956-4a14-bf7f-d37aa7cd4b0e@FreeBSD.org> <20251021154031.89840380@slippy.cwsent.com> <ede875c1-044f-407d-b2a6-2bcc55c974da@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, 21 Oct 2025 at 08:45, Andriy Gapon <avg@freebsd.org> wrote: > On 21/10/2025 18:40, Cy Schubert wrote: > > Yes, there was at the time. Looking at the commit log, it was you who > > reported the initial problem. > > Interesting... I didn't remember that. > > The commit message says: > hostapd: Fix wlan interfaces not UP/RUNNING > > Like wpa_supplicant, hostapd does not automatically UP the interface > when configured. The fix is similar to 5fcdc19a8111. > > Looks like hostapd does automatically UP the interface now (and > wpa_supplicant > does too). > Just tested with hostapd_poststart commented out and everything came up > nicely. > Ah cool. I'd still like you to file a PR though with the above info and steps. Having the interface be brought up if it's up already shouldn't break things, and we should handle it happening across multiple VAPs without them stepping on each other. -adrian > -- > Andriy Gapon > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 21 Oct 2025 at 08:45, Andriy Gapon <<a href="mailto:avg@freebsd.org">avg@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 21/10/2025 18:40, Cy Schubert wrote:<br> > Yes, there was at the time. Looking at the commit log, it was you who<br> > reported the initial problem.<br> <br> Interesting... I didn't remember that.<br> <br> The commit message says:<br> hostapd: Fix wlan interfaces not UP/RUNNING<br> <br> Like wpa_supplicant, hostapd does not automatically UP the interface<br> when configured. The fix is similar to 5fcdc19a8111.<br> <br> Looks like hostapd does automatically UP the interface now (and wpa_supplicant <br> does too).<br> Just tested with hostapd_poststart commented out and everything came up nicely.<br></blockquote><div><br></div><div>Ah cool.</div><div><br></div><div>I'd still like you to file a PR though with the above info and steps. Having the interface be brought up if it's up already</div><div>shouldn't break things, and we should handle it happening across multiple VAPs without them stepping on each other.</div><div><br></div><div><br></div><div><br></div><div>-adrian</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> -- <br> Andriy Gapon<br> </blockquote></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmoko9BcX3Vdz4hujf-y3y5gQmJqbCci0_5EG6FqJFe-3Ww>