NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Username000
Apr 27, 2020Aspirant
Can't get VLAN's working across uplink between GS110EMX switches
We have two GS110EMX switches, one each at opposite ends of a satellite office, using port 10 to provide a 10Gbe uplink between the two. On switch number 1, Port 9 is used for services by a 10Gbe NI...
- Apr 28, 2020
Well, it's almost always somethign stupid and obvious. In the process of setting up a second client per your suggestion, I discovered that the uplink and 10G workstation connections got swapped so there is no surprise as to why there was no VLAN 50 tagged traffic was not passing. Argh. Thanks for the assist, at least it made me re-check something that helped me figure it out.
schumaku
Apr 28, 2020Guru - Experienced User
Leaving alone that I have zero trust in many NIC drivers in their basic features - the amount of problems we see popping up on major OS and distros is overwhelming (problems with basic speed negotiation, flaky performance, not honouring config settings, ...) regardless if we talk Linux or Microsoft validated drivers - I can't see why one should use tagging in plain network interfaces ... configure the port to the VLAN untagged & the same PIVD.
To understand the effective issue, there are simply to many unknown variables. Trying to connect from a client interface supposedly tagging (bad policy for what should be a flat interface IMHO), connected to an switch interface connecting into two VLAN (one properly untagged/PVIDed for 1, one tagged for 50), through a trunk (which looks OK, having a trunk fully tagged is my preference but for simplicity one might do the primary VLAN untagged), to a destination port having both VLANs 1 and 50 tagged connecting to an unknown device where obviously both VLANs just be tagged.
Consider to restart your test with plain simple and clear untagged test devices run on an untagged/PVIDed port into the VLAN 50. Can't see why this should not work and allow connectivity through the trunk (both on the port #10).
That's all yet another community member can do for you.
Username000
Apr 28, 2020Aspirant
Well, it's almost always somethign stupid and obvious. In the process of setting up a second client per your suggestion, I discovered that the uplink and 10G workstation connections got swapped so there is no surprise as to why there was no VLAN 50 tagged traffic was not passing. Argh. Thanks for the assist, at least it made me re-check something that helped me figure it out.
Related Content
NETGEAR Academy

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