Capture VLAN tag with wireshark

Wireshark is widely used for Ethernet communication development. (My industry is power system and substation automation) I have some projects clearly require supporting the Ethernet packets with & without VLAN tag.  In this case, we need consider the following conditions for validation.
1. The publisher send the packets with/without VLAN tag
2. The Ethernet Switch can be setup to keep/remove the VLAN tag
3. The subscriber may see / not see the VLAN tag depend on the OS and driver configuration.

Typically wireshark is used as an validation tool. Here is the link from wireshark
https://wiki.wireshark.org/CaptureSetup/VLAN

My environment is windows + USB3 Ethernet Adapter (ASIX AX88179), there is an solution from the vendor:


Please set the "Packet Priority & VLAN" parameter of ASIX USB to LAN Windows drivers to "Packet Priority & VLAN Disable" to capture the VLAN tagged packets on WireShark.



Comments

Post a Comment

Popular posts from this blog

Debug embedded application over GDB Server by VS Code

Image
  You can debug target Linux process in VS Code over remote gdbserver. Open image-20231107-141631.png This page is done base on chatGPT + manual tweak to make it work. Debugging an embedded application over GDB Server in Visual Studio Code (VS Code) involves setting up the necessary configurations and using the GDB extension for VS Code. Here's an example of how to debug an embedded application using VS Code and GDB Server (my setup is windows vs code -> wsl2 ubuntu 22.04 -> SAM9X60 Curiosity at 10.0.0.4 Prerequisites: An embedded target device connected to your development machine. (Our SAM9X60 Curiosity is connected by Ethernet 10.0.0.4) Follow vendor procedure to flash the image to target and make sure GDB Server installed and running on your target machine. Include GDB server by update /poky-distro/build/conf/local.conf ” EXTRA_IMAGE_FEATURES ?= "debug-tweaks tools-profile tools-debug" ” Or you can use a prebuild if you do not want to rebuild yocto image VS Co
Read more

How to print your log in Vxworks6.x

For embedded software developer using printf  is the most used debug method on target. But in vxworks6.x, it start to change because the default stdout/stderr is redirected. If you connect to device by shell/telnet, printf in the code will not put to the stdout/stderr in the current shell. Solution: You can put a the following code in the debug version. Once you have connect to target by shell/telnet, call the function to redirect some task /all task io to the current shell. void ioRedirect ( void ) { int shellTid = 0 ; int shellOpFd = 0 ; int globalStdFd = 0 ; shellTid = taskIdSelf (); shellOpFd = ioTaskStdGet (shellTid, 1 ); globalStdFd = ioGlobalStdGet ( 1 ); ( void ) logMsg ( "LM:Initial task output.shellFd %d, GlobalFd %d. \n " , shellOpFd, globalStdFd, 0 , 0 , 0 , 0 ); printf ( "p:Initial task output.shellFd %d, GlobalFd %d. \n " , shellOpFd, globalStdFd); /*you can specify the task who need pr
Read more