Guest network on AP not connecting to internet

Software SW help
#1

Hello, I’m experimenting with TP-Link EasyMesh AP HC220-G5 connected to Turris Omnia. Turns out guest network is not working on it at all when in AP mode with DHCP disabled, turris just assigns guests in 192.168.1.x subnet and devices can see everything on the network.

However if I enable DHCP on the TP-Link AP it starts assigning guests with 192.168.33.x subnet, but there is no connectivity. Is there anything I need to set on Turris to make this work or it’s TP-Link’s fault? In Turris logs I see DHCPREQUEST & DHCPNAK which says either wrong server-ID or wrong network (I’ve tried to change guest network on turris to 192.168.33.x)

Feb 26 13:00:18 turris dnsmasq-dhcp[10480]: DHCPREQUEST(br-lan) 192.168.33.201 22:88:3d:b3:55:1c 
Feb 26 13:00:18 turris dnsmasq-dhcp[10480]: DHCPNAK(br-lan) 192.168.33.201 22:88:3d:b3:55:1c wrong network
#...
Feb 26 13:08:06 turris dnsmasq-dhcp[10480]: DHCPDISCOVER(br-lan) 22:88:3d:b3:55:1c 
Feb 26 13:08:06 turris dnsmasq-dhcp[10480]: DHCPOFFER(br-lan) 192.168.1.185 22:88:3d:b3:55:1c 
Feb 26 13:08:06 turris dnsmasq-dhcp[10480]: DHCPREQUEST(br-lan) 192.168.33.201 22:88:3d:b3:55:1c 
Feb 26 13:08:06 turris dnsmasq-dhcp[10480]: DHCPNAK(br-lan) 192.168.33.201 22:88:3d:b3:55:1c wrong server-ID

image

#2

[OpenWrt Wiki] Wireless Access Point / Dumb Access Point this is the instructions for main network. In order to use guest network you will have to use VLANs and make port connected to your AP a trunk with two separate VLAN id

#3

That was my thought but alas I don’t think this thing is capable of separating VLANs.

#4

If your guest network is at the same ip range 192.168.1.xxx, then it is apparently not guest network - devices on the guest network should see only internet.

But I am little bit confused which of the device (TP-Link or Turris) is the MAIN device, connected to the internet. This main device should have DHCP enabled, and all other should have DHCP disabled.

#5

In that case, VLAN capable switch plugged between omnia and TP-Link AP would help.

Or perhaps, if that is feasible, you could use additional ethernet cable just for the guest network and connect AP directly to designated port (member of guest bridge) on omnia.

#6

Guest network on Omnia is set only for WiFi ( and uses DHCP at 10.111.222.0 )… If your TP-Link is connected to Omnia by wire, you need to do exactly what “mmtj” wrote - remove one LAN port from the bridge “br-lan” and associate this LAN port to “br-guest” bridge. Then connect TP-Link to this port and it will be on guest network getting addresses from 10.111.222.0 … I am using the guest network right this way.

1 Like
#7

On turris I have LAN in 192.168.1.x subnet and of course guest network there uses by default 10.111.222.x, but I don’t really need that, what I wanted to achieve is to attach AP mesh WIFI with both local & guest networks. I assumed I could use the LAN port and let the mesh create it’s own guest network that would be isolated (it’s assigning 192.168.33.x when it has DHCP enabled). But turris won’t let those devices connect through. So I guess my only option is to either mesh main LAN or the guest network depending on how I set the port on the turris but it’s impossible for me to run both with this setup.