NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GS324TP S350 unable to obtain IP from unifi USG3 and UAP-AC-PRO
Hello everyone, I have been trying to configure multiple vlans to be accessible on my unifi AP. I read similar post where people indicated they were successful, however I have not been lucky enough t...
DietmarItsMe wrote:
My assumption is that the DHCP requests do not get through,
Where exactly, which VLAN, ...? The basic untagged (?) UniFi management VLAN or any other VLAN accessed by some dedicated SSID(s)?
Hi schumaku,
I have 3 WIFI Networks , lets call them WIFI_PRIVATE, WIFI_GUEST, WIFI_IOT and according to these 4 VLANs
WIFI_PRIVATE = 5 (DM Port 1 - Switch Port 1) PVID 5 Tagged 5
WIFI_GUEST = 15(DM Port 2 - Switch Port 15) PVID 15 Tagged 15
WIFI_IOT = 35(DM Port 3 - Switch Port 20) PVID 35 Tagged 35
Management LAN = 1(DM Port 4 - Switch Port 30) PVID 1 Tagged 1
AP = Switch Port 31 - Tagged for 1,5,15,35 and PVID 1
The WIFI Networs all do have wired network as well.
And there are 4 DHCP Servers configured in my Dream Machine
I use 4 uplink cables from my Dream Machine to the switch . One for each VLAN (I know this is not needed, but made it easier for mybrain :-)
The switch is configured on VLAN 1 to be management VLAN
My thought was, that the AP needs to acquire an IP Address, which should be on the Management VLAN, as this defaults to 1 (I assume) it should come through from Port 31 to 30 and should reach the DHCP there.
Then it spans the WIFI and communicates on the tagged Networks according to the LAN Config that is used on each WIFI.
But the AP just tries to communicate with my DM and then fails.
As I said, I assume it is the DHCP, bur maybe it is something that I don't see yet.
Any idea what I do wrong?
Thanks
Best guess (at least by default) the UniFi management network is untagged - so keep the port to the AP untagged for the management VLAN 1. PIVD is already set to 1, so now you should be ready to run.
Hi schumaku,
thanks a lot, now it works. I had to switch off my firewall rules between the networks and need to figure out how they need to be set, but this is a different story.
If there is a hint how to allow management traffic like DHCP requests m but no other traffic, please let me know :-)
Thanks a lot
Hi schumaku,
seems my success was called too early. IAfter rebooting the AP the problem stays as I've seen it before.
Here my question.
The DM does not TAG VLAN 1 , and it is impossible to configure it for VLAN 1. Would it be a good decision to configure the DM Management LAN with VLAN 2. The switch needs to have the Management VLAN to be tagged. If the switch defaults to 1 and DM to no Tag, would they even talk together? I assumed the PVID and an untagged Port would solve this, but does it?
Thanks
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
