@justine
I'm not configuring #lagg for years, so things could be changed, but when I've configured lagg for failover before, MAC addresses of all member interfaces needed to be exactly the same. So I've adjusted MAC address of WiFi to be the same as wired. Below is the remnant of the era (addresses hidden, using em0 [wired] and iwn0 [WiFi] as members).

## Network configurations for failover using lagg
ifconfig_em0="up"
ifconfig_iwn0="ether *:*:*:*:*:*"
wlans_iwn0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 *.*.*.* netmask 255.255.255.0"

@dvl hmm...

Not shure if #LAGG works across different LANs.

• Usually one LAGGs physical interfaces instead of #VLAN, so the #VLANs just get transparently spread across the overlay'd LAGG.

I guess one would have to setup Inter-VLAN routing instead...

@sodiboo instead if using proprietary SaaS like Tailscale I can recommend using #pfSense and other Networking-focussed #distros to manage your #WireGiard Setup where you can easily deploy & maange configs for clients and the clients themselves...

• Besides that you are correct: Similar to #LAGG / #LACP-#Bonding and #VLANs, WireGuard is a virtual interdace that is treated natively, unlike #tun / #tap interfaces for like #OpenVPN...