NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Some clarity on VLANs needed
So I've been struggling for a could of days trying to get a single VLAN setup and this morning I changed the VPID settings and I broke everything. I read this post from 2017 and I think it will solv...
Assuming I understand you right nd you have configured two networks on one port of the USG - what makes VLAN 1 (the "base VLAN") untagged, and the VLAN 2 taged.
You configure a so-called VLAN-trunk, the base LAN 192.168.16.0/24 is VLAN 1 is run [U]ntagged (therfore also PVID 1 - this makes uncoming untagged frames going to VLAN 1, simple!), and the voice VLAN 2 run [T]agged.
If you need a Data access port only, configure it VLAN 1 [U]ntagged, PVID 1 (no other VLAN associations, all empty).
If you need a VoIP access port only, configure it VLAN 2 [U]ntagged, PVID 2 (no other VLAN associations, all empty).
If you need a shared port for Data and VoIP (phone data pass-through), configure it VLAN 1 [U]ntagged, PVID 1 plus VLAN 2 [T]agged.
If the plan is using VoIP and data on one connection (Switch - Phone [1 Gb required typically!] - PC) I owuld suggest using the Netgear switch Auto-VoIP feature, check the phone OID is configured, ... like this you don't have to configure any VLAN tagging on the phone.
This is it. No rocket science. If UniFi is non-transparent what is going on under the sexy user interface - sorry, this is not Netgear's mistake.
schumaku wrote:
If you need a shared port for Data and VoIP (phone data pass-through), configure it VLAN 1 [U]ntagged, PVID 1 plus VLAN 2 [T]agged.
Sorry, bit confussed now. Is VLAN 2 supposed to be tagged or untagged, the quoted text suggests that it needs to be tagged.
This alone isn't sufficient.
Re-read the above.
For the testing and learning curve, I suggest to configure two access-type ports, one on VLAN 1 [U]ntgged and PVID 1, another with VLAN2 [U]ntagged and PVID 2. This gives you two ports for testing the VLANs to the router...
The above suggests untag it but set the PVID to 2.
I know from an early mistake that tagging all ports on VLAN 2 and setting PVID to 2 results in loosing connection completely.
Will set as you suggest for testing.
I should add that I can reach the VLAN configured on the USG-Pro, I get ping replies from 10.5.5.1 which is the router. But the same isn't true for any other device on the 10.5.5.0/24 range.
I'm getting strange results when switching between Tagged and Untagged for VLAN.
The above screen happens when I change the ports from Tagged to Untagged for VLAN 2. Switching back to Tagged just results in a Request timed out.
That's why i had proposed to configure two access ports into each VLAN - this allows to figure out if the VLAN config of the router and the switch VLANs are workable. A test computer plugged to each port must get an IP from the relevant VLAN and iP subnet / DHCP server, and must be able to ping each subnet default gateway.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
