Flint 2 - Extend stock guest network with vlan

[jaunt-omen]

Hey all,

First time GL.iNet router user here!

I am trying to extend the "built-in" Guest wifi on a Flint 2 to a dumb access point (in another building also running Openwrt). By "built-in", I mean the Guest wifi network already pre-configured by GL.iNet that can easily be toggled on/off via the Flint 2 web-UI.

Normally I would go into Luci, and enable vlans on the appropriate device (br-lan etc), and tag the trunk port, and assign the same vlan id on the DAP side.
However, I cannot see a device for the Guest interface (in the Devices tab). The interface itself is attached to the "br-guest" (bridging) device, but there is no "br-guest" in the Devices tab!
I'm clearly missing a piece of the puzzle and am a little lost.

I have some experience with Openwrt, but in no way a professional!

Is it possible to extend the default (built-in) Guest wifi via vlans on this model/setup?
Or do I need to setup another (eg: Guest-2) wifi for the other building?

I would prefer to keep them on the same wifi network if possible to enable fast roaming.

Any help appreciated.

Thanks in advance

[DaWeav]

If your router is not running the OP24 firmware version which I’ve heard natively shows the br-guest bridge device, then you could do it manually like I did on the non-OP24 firmware to expose the br-guest bridge device.

Setting up LAN Guest Network on MT6000

@bruce I glad to hear that the version 24 gl firmware shows the ‘br-guest’ bridge device natively now, sweet. However, I was able to make the ‘br-guest’ bridge device show up on the devices tab of the gl version 21 firmware’s LUCI GUI on my Flint 2. The way I got the ‘br-guest’ device to appear on the LUCI GUI’s devices tab on the version 21 gl firmware, was to edit the ‘/etc/config/network’ file to change the Guest interface from being the ‘br-guest’ bridge, and adding a few lines to create t…

[jaunt-omen]

@DaWeav Thank you for your response, much appreciated

So, that means adding your own device and calling it 'br-guest'.
I was originally thinking of doing that, but wasn't sure if that would break any of the proprietary parts of the GL.iNet software (ie: their own updates made to OpenWrt 21.02 that comes installed as factory default).
However, if this is the only way to go then I will just add an additional vlan (on br-lan) and assign that as the device on the guest interface.

@DaWeav

If your router is not running the OP24 firmware version

I was thinking of updating to OP24 (as my DAP is running stock Openwrt v24.10), but having read [4.7.5-OP24] Known Bugs I'm not sure now is the time. Maybe wait a few more months and hope some of those bugs are cleared out!?

Once again, thank you for your help

[DaWeav]

Ya, I’m not considering trying the O24 either.

BTW, I have an issue when modifying the br-lan bridge on version 4.7.x firmware since I have VLANs configured on it because of the confusion with the VLAN Filtering checkbox. So you might experience this situation as well.

New firmware version 4.7 being released for beta testing

@bruce I have 4.7 on the Flint 2 and the ‘Enable VLAN Filtering’ checkbox is confusing to me. I think this is related to what @miraben was discussing earlier in this thread about VLAN filtering. Whenever I edit the ‘br-lan’ interface that has some VLANs configured, it automatically puts a checkmark in the ‘Enable VLAN Filtering’ box for the bridge device. When I apply the changes with the checkbox checked, it kills the br-lan network and I have to wait 90 seconds for the changes to be reverted.…

[jaunt-omen]

Thank you for that info.

I'm on 4.7.7 running Openwrt v21.02 (that came factory installed) and thankfully I have not faced the same issue, although I did SSH into the router and made the VLAN changes there rather than via Luci.

Once again thank you for your help.
I have managed to achieve my objective.