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...
schumaku wrote: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.
Ok, I figured it would be this: 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.
Will give it all a bash and report back, thank you.
djmohr wrote:
schumaku wrote: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.
Ok, I figured it would be this: 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.
Will give it all a bash and report back, thank you.
Sadly this didn't work for me.
All ports are tagged with VLAN 2 and PVID is set to 1. I don't seem to be able to ping or connect to any other the voice devices. What's interesting though is that I tried to untag VLAN 2 from all port then I get a single ping reply from the PBX. I've disabled Ingress Filtering as well and this made no difference.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
