On 2023-02-08, Martin Kjær Jørgensen <m...@lagy.org> wrote: > > When configuring the athn0 with no IP address, and adding the interface to a > bridge0 interface along with the em1 device and a vether0 device, clients > still connects fine to athn0 SSID but when clients ask for IP over DHCP, > ethernet frames does not propagate to vether0 where the dhcpd listens.
Don't expect great performance, but athn hostap ought to work. Likely you will have better luck replacing the bridge interface with veb(4) and vether with vport(4), e.g. hostname.veb0: add vport0 add athn0 add em1 up hostname.vport0: inet 192.168.1.1/25 up > vether0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > lladdr fe:e1:ba:d0:cd:4a > index 9 priority 0 llprio 3 > groups: vether > media: Ethernet autoselect > status: active > inet 192.168.1.1 netmask 0xffffff80 broadcast 192.168.1.127 > athn0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:26:82:61:87:c9 > index 5 priority 4 llprio 3 > groups: wlan > media: IEEE802.11 autoselect mode 11g hostap > status: active > ieee80211: nwid TEST chan 2 bssid 00:26:82:61:87:c9 -58dBm wpakey > wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > bridge0: flags=0<> mtu 1500 > index 8 llprio 3 > groups: bridge > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp > designated: id 00:00:00:00:00:00 priority 0 > athn0 flags=3<LEARNING,DISCOVER> > port 5 ifpriority 0 ifcost 0 > em1 flags=3<LEARNING,DISCOVER> > port 2 ifpriority 0 ifcost 0 > vether0 flags=3<LEARNING,DISCOVER> > port 9 ifpriority 0 ifcost 0 > Addresses (max cache: 100, timeout: 240):
