How to extend BE9300 Guest Wifi to second AP (OpenWrt or GL-iNet devices)

[madnat]

Hello

How can I extend (or replicate) the Guest Wifif service running on my BE9300? I need onther access points in my property to provide the same wifi for guest moving around the property.

Thanks

[madnat]

I took a look at the interface and device settings in luci. It wasnt obvious to me whether the standard GL-iNet guest WIFI was using a specific VLAN, or ip number range with nominated DHCP server. Does anyone have more details on the way GL-INet setup guest WiFi on the BE9300??

[will.qiu]

Hi

Sorry for the delayed reply.

By default, our Guest network simply creates a new bridge, assigns it a new subnet, and adds the Guest Wi-Fi to that bridge.

If you want to extend the existing Main and Guest networks to other AP devices, you will need to configure VLANs on both the main router and the AP to achieve this.

You can refer to the following guide for the relevant configuration:

Flint 3 (GL-BE9300) as AP behind pfSense: multiple SSIDs -> VLAN + Random BSSID

Hi everyone, I’m considering Flint 3 (GL-BE9300) to use as a wired access point behind pfSense (AP/bridge mode, no NAT, no DHCP on BE9300). pfSense will provide VLAN trunk and DHCP/firewall per VLAN. My goal is: 3-4 SSIDs, each mapped to a separate VLAN (SSID → VLAN), e.g. Main / Work / IoT / Guest Randomized BSSID enabled, and I need it to still rotate in AP mode (i.e., change on reboot, not only in router mode) Questions for BE9300 owners: Have you actually achieved multiple SSID…

[madnat]

Flint 3 – Guest WiFi on Remote Access Points (VLAN Setup Guide)

I took some time to investigate this from scratch so I could properly understand how it works.

In the end, it turned out to be quite simple—once I figured out the correct commands and how the Flint 3 handles networking internally.

That said, I found this quite difficult initially because a lot of the Flint 3 wireless configuration is hidden from LuCI, and it doesn’t behave exactly like standard OpenWrt.

For context:
I’m not a developer or network engineer—just an enthusiastic home networking tinkerer. Hopefully this helps someone at a similar level.

---

Overview (What we're doing)

• One Ethernet cable per access point

• That cable carries multiple VLANs

• The AP splits them into:

  • Main WiFi (LAN)

  • Guest WiFi

---

Diagram

[ Flint 3 Router ]
        │
        │  (Single Ethernet Cable - VLAN Trunk)
        │  VLAN 1 (LAN) + VLAN 3 (Guest)
        │
   -------------------
   |                 |
[ Access Point ]  [ Access Point ]
   |      |           |      |
 LAN    Guest       LAN    Guest
SSID   SSID        SSID   SSID

Important: Each access point only needs one cable — that cable carries multiple networks (VLANs), which the AP then separates into different WiFi networks.

---

Assumptions

This guide assumes your Flint 3 is already set up with a basic working configuration:

• Internet connected via WAN port

• Main WiFi configured (SSID + security)

• Guest WiFi enabled

  (Flint UI → Wireless → Guest WiFi)

• LAN configured

  (Network → LAN)

• Guest network configured

  (Network → Guest Network)

• Port forwarding configured (if needed)

• SSH enabled

  (Security → Management Control → SSH on port 22)

• Remote SSH access disabled

---

Step 1 – Configure VLANs on Access Points

Each AP needs two VLANs:

• VLAN 1 → Main LAN (default)

• VLAN 3 → Guest network (example)

How I did it:

1. Connect AP directly to your PC

2. Set a static IP on your PC, in the same range as your AP

3. Open AP web interface

4. Configure VLANs

This is well documented online for OpenWrt-based APs.

Ultimately you want your AP bridge device to have VLANS configured similar to this:

---

Step 2 – Configure VLAN on Flint 3

Good news:

• VLAN 1 (LAN) already exists

• We only need to add VLAN 3 (Guest)

---

Step 3 – SSH into the Router

From your PC command prompt:

ssh root@<Flint3 LAN IP>

Enter your password when prompted.

---

Step 4 – Add Guest VLAN (Commands)

Run one line at a time:

uci add network switch_vlan
uci set network.@switch_vlan[-1].device='switch1'
uci set network.@switch_vlan[-1].vlan='3'
uci set network.@switch_vlan[-1].ports='4t 5t 6t 7t 3t'
uci set network.guest.ifname='eth1.3'
uci commit network
/etc/init.d/network restart

---

What These Commands Do

• Create VLAN 3

• Allow it on LAN ports (tagged)

• Link it to the guest network

• Restart networking

---

Final Result

• APs send guest traffic via VLAN 3

• Flint 3 handles:

• DHCP

• Firewall rules

• Internet access

Guest WiFi now works across all remote APs

---

Tips / Troubleshooting

• VLAN IDs must match on router + APs

• Check VLAN tagging on AP ports

• Reboot APs if needed

• You can extend this for IoT VLANs later

[will.qiu]

Thanks for sharing the guide—I think it will be very helpful for users with similar needs!