Correct way to combine untagged and tagged networks on one port?
Hi everyone,
I have a netgear managed switch (GS752TPv2) with different VLANs.
On one port I do want to have two VLANs, one untagged (VLAN 10) and one tagged (VLAN 40).
The untagged is used by a physical notebook, the tagged on is used by a VM running on the physical notebook.
So far everything seems to work - only strange issue: My monitoring system starts sending me alerts regarding to network input errors on my hypervisor network card (which should even not be part of this traffic) as soon as the computer is connected to the port... So I guess there must be some packets wrongly deliviered...
What is the correct way to combine an untagged and tagged vlan on the same port?
On one port I do want to have two VLANs, one untagged (VLAN 10) and one tagged (VLAN 40).
The untagged is used by a physical notebook, the tagged on is used by a VM running on the physical notebook.
Port g41 looks about right, untagged access port for VLAN 10, tagged trunk for VLAN 40.
Tell us a little bit more about the config of this VM nd the host for example. Also what is the source of the packets in question, and why these could end up in the wrong VLAN.... Looks more like a config issue on that VM host and VM itself.
Re: Correct way to combine untagged and tagged networks on one port?
Actually, any switch that has a web UI log in and user configurations, regardless of features or specs IS a managed switch. Smart vs Managed is just marketing. All switches that have a log in WEB UI and user configurations are managed. Been like this for a long time. Simple vs complex and specs don't change this. There all managed. Just some differences in features and specs is all. There all managed. NG community even titles this as well "
The VM is running on windows 11 pro - host inside hyper-v (not on windows server).
All we did was adding the VLAN ID to the virtual machine in hyper-v configuration.
From VM and host side everything is working fine.
If I would not run a monitoring on my server-hypervisor I would not even have noticed that there are errors on the network card.
I am just not the guy that likes to ignore errors, even if they does not make themselves noticeable. That is why I though something must be wrong with my switch configuration.
I am just not the guy that likes to ignore errors, even if they does not make themselves noticeable. That is why I though something must be wrong with my switch configuration.
...or whatever else. You still have not told the interested reader where and what kind of errors you recognize.
Start with the Power Shell and get a list of network adapter (physical and logical) for example. Modern Windows systems can be extremely informative.
