
Somehow, having BOTH monitor mode enabled in NICs (which allows me to see the VLAN tag in RX frames in wireshark) and wireshark in capture mode, the pinging fails. If I stop wireshark capture, the pings start right back up.Īlso, if I go back into registry and turn monitor mode off, then pinging is successful even if wireshark is running. Refer to the Windows section of the Wireshark CaptureSetup/WLAN wiki page for more information. There are other ways too though, such as by purchasing an AirPcap adapter from Riverbed. And it still does, except when I start capture with wireshark (on either PC), then the pings fail. Probably the easiest and cheapest way is to uninstall WinPcap and install Npcap. I then decidd to ping between the two PC's, which normally works fine. After doing so, I could see the VLAN tagged packets in wireshark when using packet generator - which is great. I saw I could enable monitor mode in registry for the Intel NICs, which would prevent the NIC/driver from stripping the VLAN tags. I then read about NIC/drivers stripping the VLAN tag before sending up stack, which was why I did not see the VLAN tags in wireshark on receiving PC.


Initially, I was using packet generator to send vlan tagged packets and would see the packets arrive untagged at receiving PC.

They both have wired Intel NICs (I217-LM) connected to to switch with CAT 5 cables.
