I've been trying to make sense of this (apparent) discrepancy in behaviour between two basically the same configs with different behaviour - stanzas are copy/paste with only one real difference. Device is a xiaomi mini freshly updated to 19.04.
I want to bridge an AP into a VLAN. port 4 (previously 'WAN') is my trunk. port 6 is the cpu - i'm using the two other physical ports to keep access to the device while playing around , they're not part of this.
note that wlan1-1 is mentioned in ifname for MGMT, but not for MGMT2.
If I understood the docs, then specifying network is the preferred way to bridge the AP into the VLAN (as opposed to specifying the wlan device in the bridge/ifname).
this works fine for vid4 but on the vlan with vid2 i need to explicitly add wlan1-1 to make it work. otherwise i get DHCP packet received on wlan1-1 which has no address and devices cannot connect.
what am I not seeing? (I do have a working config - just trying to learn
Usually vid2 is used for WAN interface. I don't know if there are scripts/programs rely on this. Same for vid1. It's usually a "special" vid on any router or switch.
Why not using anything higher then 2? Is there a need to use them? You have 4096 vids available.
Beside that the whole network and dhcp config would help to see what is going on. I would guess there is sth. wrong in dhcp config.
thanks for the reply, so yeah there is no specific reason other than curiosity how the system works. That said, it seems that the MGMT/vid2 wlan is plain unstable and i'm indeed just going to use a different VID.
for completeness sake, here's my dhcp config, it's all disabled (except for my backup "lan") as DHCP is served from my main router.
Did you delete WAN interface accordingly? So it might be not ignored because Dnsmasq is listening on all interfaces by default. In addition to that I assume that vid2 is not a good choice because I'm sure that there are things hardcoded for wan fitting on device' hardware design.
Just try another vid and see what happen.
hi pwned, yes there's indeed no wan interface definition.
But maybe I wasn't clear: i do have a working setup.
I was just curious what caused the discrepancy between VLAN2 and the higher numbered VLANs. But again, with that discrepancy in the configs taken into account everything works fine.