NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PBG_from_TN
Jun 30, 2021Aspirant
GS324TP - VLAN setup for Guest WiFi
Needing some guidance on somewhat basic setup. The GS324TPs are what are confusing me. I've followed some KBs, were slightly helpful and confusing at the same time. 2 offices, main and remote - c...
PBG_from_TN
Jun 30, 2021Aspirant
the 2 switches are purposefully for only what is plugged in, nothing else will be plugged into them except the WAPs, the fiber, CloudKey controller, and the uplink port.
Sorry if I'm short, I'm frustrated to say the least.
So remove any U/T from a port that is unused?
Main Office
Switch
VLAN1 - 192.168.1.0/24
VLAN99 - 10.255.0.0/24
- waps are broadcasting both VLANs
g17 - WAP - tag on VLAN99??
g19 - WAP - tag on VLAN99??
g21 - WAP - tag on VLAN99??
g23 - Unifi CloudKey G2- ??
g24 - uplink to firewallG25/G26 - ??
g25 - T/U or blank?
g26 - T/U or blank?
Remote Office
g1 - WAP
g25 - T/U or blank?
g26 - T/U or blank?
schumaku
Jun 30, 2021Guru - Experienced User
PBG_from_TN wrote:
Sorry if I'm short, I'm frustrated to say the least.
Understood.
However I can't take away the learning curve for your UniFi system and the basic VLAN requirements, plus what is configured on the firewall my friend. The config work is the same if oyu use a Netgear, a UniFi, a more generic Ubiquity, a Cisco or whatever other brand VLAN capable switch.
The UniFi management runs on the primary untagged network (well, unless one does go and try to change it - but this will add more issues for non-experienced network people). Trouble is they don't tell this the unexperienced users 8-)
Said that,
- the CloudKey must reside on an [U]ntagged port on your VLAN 1, PVID 1, not member of any other VLAN, so all empty for VLAN 99 [ ] - making the office network also the UniFi management network.
- the WAP management and primary SSID does again reside on an [U]ntagged port on your VLAN 1 (office and management), PIVD 1 _plus_ for the guest SSID [T]agged VLAN 99.
- the trunk between the two offices as above for the WAP, keep the primary VLAN 1 [U]ntaggged, PVID 1, the guest VLAN 99 [T]agged - ok.
- Ports not intended to provide guest network access [ ] empty on the guest VLAN 99, just let the unused ports be just office network ports - you can keep the VLAN 1 [U]ntagged, PIVD 1.
Uplink to the firewall ... well, trying to read the crystal ball again:
- unclear why you talk of two ports here
- one could guess one port is for the office network VLAN 1 [U]ntagged, PVID 1 again _or_ the firewall is configured for VLAN 1 [T]agged, and the
- other is the Guest network VLAN 99 [U]ntagged, PIVD 99 again _or_ the firewall port is configured for [T]agged.
Said that - whatever switches you are going to deploy, these switch ports must be configued to work with your firewall and it's two links and two security zones and/or interfaces, your WAC of choice, and your wireless system controller. Nothing of this is coming from Netgear so a lot of grey guessing zone here. Can' take away the burden of exactly knowing what and how a conneced device is configured, being the firewall, the WAC, the CloudKey, ...
So don't blame the messenger who is managing bunches of small and medium businesses and venues with Netgear, and some large venues with UniFi, plus some more in my spare time... beyond nursing some network manufacturers on making thier stuff better.
Last but not least, the question on what to do with "unused" ports - this requires some policy how to handle these ports. Experienced security and network people have a capture all VLAN, a dummy black hole VLAN, for such purposes. So nothing cna go wrong if a random person is connecting his computer there .... Another layer of complexity in network management.
- PBG_from_TNJun 30, 2021Aspirant
Uplink isn't 2 ports, that was a typo...
I've installed numerous UBNT networks, numerous vendor firewalls (sonicwall, fortinet, watchguard, sophos, palo alto) mostly using Meraki, HP or UBNT switches, etc... I've just hit a wall on this Netgear.
As I started out, my intention was to K.I.S.S. - but as it turns out, somehow it has turned into a P.I.T.A
I'm going to try to reconfigure tomorrow, not likely to get it working, as much as I'd like to say it will...
- schumakuJun 30, 2021Guru - Experienced User
So I can even less follow you here. Nothing specifically difficult - these are mainstream industry standard switches. We can dispute the PVID part adding complexity on an untagged port config, it's just defining the VLAN where untagged frames are assigned to - what allows interesting things (but I don't like to talk about these asymetric VLANs).
Convinced you get it sorted!
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!