In-Reply-To: <CAJ-Vmomd3L%2BAtu5DbxXWKKw6zvgJkUxDgRGYx9F8gO6WTntiCg@mail.gmail.com>
| previous in thread | raw e-mail | index | archive | help
On 20/10/2025 23:38, Adrian Chadd wrote: > That's weird. I checkd mine (-head) and both are up and running. > > What's in your config files and how do you create the interfaces? This is the first time I see anything like this too. The configuration is pretty standard, everything is done via rc.conf (and per-interface hostapd config files). wlans_ath0="wlan0 wlan1" create_args_wlan0="wlanmode hostap country UA" ifconfig_wlan0="HOSTAP ssid BackupLan channel 11:ht/20 ht20 pureg indoor shortgi" create_args_wlan1="wlanmode hostap bssid" ifconfig_wlan1="HOSTAP ssid GrassLan channel 11:ht/20 ht20 pureg indoor shortgi -apbridge" > On Mon, 20 Oct 2025 at 13:35, Andriy Gapon <avg@freebsd.org > <mailto:avg@freebsd.org>> wrote: > > > This is on 14.3. > I have configured two VAPs, the configuration is almost identical except for > SSID. > hostapd-s for both interfaces are also running. > Both interfaces are UP, both have status running, but one doesn't have RUNNING > in its flags. > > What does that mean? > > wlan0: flags=8903<UP,BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=0 > ... > parent interface: ath0 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> > status: running > > wlan1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 > mtu 1500 > options=0 > ... > parent interface: ath0 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> > status: running > > > -- > Andriy Gapon > > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>