Hi. I'm trying to setup VLANs
I was using this guide mentioned in another post
I've enabled vlan filtering in the lan-bridge
I have VLANs working on the native GL Firmware.
Instead of doing it the way it is described in the video, I left the LAN interface on the ‘br-lan’ bridge device, and just checkmarked the ‘br-lan.1’ VLAN to be a bridge port member of the ‘br-lan’ bridge device so that I had an untagged native management VLAN for my managed switches. I then checkmarked the other ‘br-lan.#’ VLANs I created as a bridge port member on other bridges, like br-guest and br-IOT which are assigned to other LAN interface networks. I then tagged those VLANs on the LANx ports of the ‘br-lan’ bridge device where my managed switches are connected so that I could put wired devices connected to my managed switches on the different IP networks.
This may be of some help also.
Can you show which interface is assigned on the wireless settings in luci?
It needs to be interface lan, not br-lan.1 or br-lan.
Since the vlan isn't a newly created interface this should work, on new interfaces the firewall zone input needs to be set to accept.
the interface lan has a child vlan device br-lan.1, hostapd/wifi always require a bridge to hook into or a child device from the bridge (a vlan device), the only thing I see you are missing is the keep up bridge checkbox being checked.
When you are done, also on the wireless part, restart the router because the MTK SDK is buggy on the luci part and sometimes only works properly after a restart.
From the vlan stanza I don't see really a issue.
What you want to avoid though:
creating vlans on br-lan, and then mixing br-lan.x in a different bridge, the developers did not intend this, and it is not known how deep in the kernel it could break potential things it all comes down how well it is implemented in OpenWrt.
I also readed what some people on the OpenWrt forums said you only want one bridge to handle vlans and nothing more, given that a router often only has one switch cpu, although it works it kinda makes sense.
Though I did not experience strange symptoms especially with the first one, but it makes sense, it is very likely it now works and once in a sudden this breaks and results into looping.
Thanks to all who replied. It was wireless adapter bug indeed. Reboot helped
