I’m following these instructions for Flint 3 ( How to Add a LAN Port to the Guest or IoT Network via LuCI ) to change chassis LAN4 to be in the Guest Network but when I get to Add the VLAN Device to the IoT Network Go to Network → Interfaces → Devices. Find br-guest br-guest is not there. If I try to manually make one it says br-guest is already used…. so if I jump over to Network > Interfaces I see it in the gui and can edit and add it via that but when I do so routing all “guest network” devices via VPN doesnt work for the items on the LAN they do get the guest network IP’s of 192.168.9.XXX but are not being routed to the VPN.
Hi,
You do not need to create a separate interface for eth1.2. If you previously created one manually, please delete only that newly created interface and keep the built-in Guest interface.
Based on the current port mapping, the chassis LAN4 port is displayed as LAN1 on the LuCI Switch page.
After saving the VLAN configuration, connect to the router through SSH and add
eth1.2 to the existing Guest interface:
uci -q del_list network.guest.ports='eth1.2'
uci add_list network.guest.ports='eth1.2'
uci set network.guest.type='bridge'
uci set network.guest.bridge_empty='1'
uci commit network
/etc/init.d/network restart
The SSH connection may be temporarily interrupted while the network service restarts.
After reconnecting the Ethernet cable, a device connected to chassis LAN4 should receive an address from the Guest Network, normally 192.168.9.x.
You may confirm its current status with:
ip link show br-guest
ls -1 /sys/class/net/br-guest/brif/
If the configuration is correct, eth1.2 should be listed as a member of br-guest.
Hey Charles,
I had already reverted what I did so it was back the way I had it and just now tried the steps you outlined. Unfortunately the SSH session ran into several issues:
root@GL-BE9300:~# uci -q del_list network.guest.ports='eth1.2'
root@GL-BE9300:~# uci add_list network.guest.ports='eth1.2'
root@GL-BE9300:~# uci set network.guest.type='bridge'
root@GL-BE9300:~# uci set network.guest.bridge_empty='1'
root@GL-BE9300:~# uci commit network
root@GL-BE9300:~# /etc/init.d/network restart
1
Disable ol_stats for Lithium platforms
/sbin/wifi: eval: line 3148: : Permission denied
OK
1
Disable ol_stats for Lithium platforms
/sbin/wifi: eval: line 3148: : Permission denied
OK
1
Disable ol_stats for Lithium platforms
/sbin/wifi: eval: line 3148: : Permission denied
command failed: Operation not permitted (-1)
device: wifi0 vifs: wifi2g guest2g wlanmld2g wlanmldguest2g iot2g
device: wifi1 vifs: wifi5g guest5g wlanmld5g wlanmldguest5g iot5g sta sta
device: wifi2 vifs: wifi6g guest6g wlanmld6g wlanmldguest6g
Read from remote host 192.168.8.1: Connection reset by peer
Connection to 192.168.8.1 closed.
client_loop: send disconnect: Broken pipe
snoots@Snoots-Pi:~ $ ip link show br-guest
Device "br-guest" does not exist.
Hi,
Thank you for update.
The SSH connection was disconnected because /etc/init.d/network restart restarted the router’s network interfaces. This is expected and does not necessarily indicate that the configuration failed.
After the connection was closed, the command prompt changed to snoots@Snoots-Pi, so the subsequent ip link show br-guest command was executed on your Pi rather than on the Flint 3. Therefore, the message that br-guest does not exist is expected.
Could you please connect a device to the chassis LAN4 port and check whether it receives a 192.168.9.x address and is routed through the VPN as expected?
If it is working correctly, no further commands are required.
If it is still not working, please reconnect to the Flint 3 via SSH and run the following commands so that we can check the current br-guest configuration:
uci show network.guest
ip link show br-guest
ls -1 /sys/class/net/br-guest/brif/
ubus call network.interface.guest status
Thank you for your cooperation and patience.