Enable VLAN Tagging on a Network Card
KillKool
-
KillKool -
KillKool -
Hello,
I have a very specific problem hoping that someone can help me. I will try to explain my issue more clearly :) :
I would like to capture traces using Wireshark to check what happens when my box (it doesn't matter which one) boots. However, I do not see the VLANs appearing in Wireshark (VLAN 8/38, 8/39, 8/40, 8/51 for example), because the VLAN tagging option is disabled by default in Windows.
The network card in question is: Nvidia nForce Networking controller.
I am unable to find what to enter in "regedit" to enable this.
Because on another PC that has a network card: Broadcom NetXtreme Gigabit, I found a tutorial saying to add a key in regedit: "PreserveVlanInfoInRxPacket" and set the value to "1", and once this was done, it worked very well; the VLAN display appears in Wireshark. But I would like to find the option to add for this network card: Nvidia nForce Networking controller.
If anyone has any ideas, I would appreciate it.
Thank you in advance
Best regards,
I have a very specific problem hoping that someone can help me. I will try to explain my issue more clearly :) :
I would like to capture traces using Wireshark to check what happens when my box (it doesn't matter which one) boots. However, I do not see the VLANs appearing in Wireshark (VLAN 8/38, 8/39, 8/40, 8/51 for example), because the VLAN tagging option is disabled by default in Windows.
The network card in question is: Nvidia nForce Networking controller.
I am unable to find what to enter in "regedit" to enable this.
Because on another PC that has a network card: Broadcom NetXtreme Gigabit, I found a tutorial saying to add a key in regedit: "PreserveVlanInfoInRxPacket" and set the value to "1", and once this was done, it worked very well; the VLAN display appears in Wireshark. But I would like to find the option to add for this network card: Nvidia nForce Networking controller.
If anyone has any ideas, I would appreciate it.
Thank you in advance
Best regards,
Configuration: Windows XP Firefox 2.0.0.17
2 réponses
Warning, not all network cards can handle VLANs. Additionally, to see the VLANs passing through your router, it must support them as well. In my opinion, consumer routers cannot handle VLANs (but I'm not sure).
What exactly are you trying to do?
What exactly are you trying to do?
Hi,
Actually, I set up a Telindus to trace the traffic between the Box and the DSLAM. As part of my job, I need to verify that the box is indeed sending the correct requests for its VoIP setup.
So the Telindus is configured correctly; all that's left is to enable the tagging/untagging of the VLANs set up by certain cards, including this one.
For example, all internet traffic goes through VLAN 8/35, TV traffic goes through VLANs 8/38, 8/39, and 8/40, and VoIP goes through VLAN 8/51. However, the problem is that I don't see any of this traffic because the card's option is not enabled by default.
For example, the 3Com 3C905C-TX network card untags VLANs by itself by default, so they are visible directly via Wireshark without any settings or modifications to the registry. But my problem is that my network card (integrated chipset) does not untag anything at all, and I know there is a way to force it (it's actually a kind of manufacturer limitation that Windows amplifies).
For another example, with a Broadcom NetXtreme Gigabit card, I couldn't see the VLANs via Wireshark, but after finding a method online to untag the VLANs, I was able to "see" them through this network card. For the Broadcom, it was enough to add an entry in the Windows registry. And after that, the VLANs became "visible" in Wireshark, allowing me to apply filters...
So, I think (not 100% sure but almost) that there is a similar type of manipulation for the Nvidia nForce Networking Controller.
And that's what I'm struggling to find, and perhaps someone here knows this manipulation in question, knowing that in my opinion it involves a registry modification to be done via "regedit".
Best regards,
Actually, I set up a Telindus to trace the traffic between the Box and the DSLAM. As part of my job, I need to verify that the box is indeed sending the correct requests for its VoIP setup.
So the Telindus is configured correctly; all that's left is to enable the tagging/untagging of the VLANs set up by certain cards, including this one.
For example, all internet traffic goes through VLAN 8/35, TV traffic goes through VLANs 8/38, 8/39, and 8/40, and VoIP goes through VLAN 8/51. However, the problem is that I don't see any of this traffic because the card's option is not enabled by default.
For example, the 3Com 3C905C-TX network card untags VLANs by itself by default, so they are visible directly via Wireshark without any settings or modifications to the registry. But my problem is that my network card (integrated chipset) does not untag anything at all, and I know there is a way to force it (it's actually a kind of manufacturer limitation that Windows amplifies).
For another example, with a Broadcom NetXtreme Gigabit card, I couldn't see the VLANs via Wireshark, but after finding a method online to untag the VLANs, I was able to "see" them through this network card. For the Broadcom, it was enough to add an entry in the Windows registry. And after that, the VLANs became "visible" in Wireshark, allowing me to apply filters...
So, I think (not 100% sure but almost) that there is a similar type of manipulation for the Nvidia nForce Networking Controller.
And that's what I'm struggling to find, and perhaps someone here knows this manipulation in question, knowing that in my opinion it involves a registry modification to be done via "regedit".
Best regards,
Just a necessary clarification, I think, to be precise:
the numbers 8/35, 8/38, 8/40 do not represent VLANs but rather ATM PVCs, I believe (CPI/VCI); VLANs are numbered from 1 to 4095.
However, it is logical for an ATM PVC to be mapped to a VLAN over Ethernet, as it is its equivalent in the other transmission system.
Also,
Wireshark decodes the tags by itself, provided the network card does not remove them, of course.
--
and ... There you go!
the numbers 8/35, 8/38, 8/40 do not represent VLANs but rather ATM PVCs, I believe (CPI/VCI); VLANs are numbered from 1 to 4095.
However, it is logical for an ATM PVC to be mapped to a VLAN over Ethernet, as it is its equivalent in the other transmission system.
Also,
Wireshark decodes the tags by itself, provided the network card does not remove them, of course.
--
and ... There you go!