Serial Sniffer Example
in a few steps (2/3)
> sudo serialdump-linux -b115200 /dev/ttyACMx |
./convert-to-binary | wireshark -k -i -
Linux PC setup (Ubuntu)
using “serialdump-linux” utility
1. run Cygwin as administrator
2. serialdup-windows.exe utility is provided pre-compiled, but in
case you need to recompile it:
• cd serialdump-src
• make
• (or gcc –o serialdump-windows.exe serialdump.c)
• mv serialdump-windows.exe ..
3. Run the following command chain (it is ONE line of three
commands in pipe “|” one with the next one)
12/18/2018
20
Windows PC setup (Win 7/8)
using “serialdump-windows.exe” utility
Setup the PC
running Wireshark
application
6
From: [ROOT]/Utilities/serial-sniffer
OR
> serialdump-windows.exe -b115200 /dev/ttySz |
./convert-to-binary | wireshark.exe -k –i -
1. serialdump-linux utility has to be compiled:
• cd serialdump-src
• make
• (or gcc –o serialdump-linux serialdump.c)
• mv serialdump-linux ..
2. Run the following command chain (it is ONE line of three
commands in pipe “|” one with the next one)
NOTES:
Mind the trailing dash (-), it is mandatory, not a typo!
The ttySz / ttyACMx numbers depends on the device enumeration of the Nucleo board running the Serial-sniffer firmware, you can
use tab auto completion under both Linux and Cygwin
It is mandatory to invoke the above commands from the “serial-sniffer” folder (actually, the “header.pcap” file is supposed to be in
the same folder of the “convert-to-binary” script)
Perl is needed in order for the “convert-to-binary” script to work
• You can install it either via Cygwin setup or your Linux Package Manager
Wireshark application is required, a recent version it is recommended in order to have state of the art protocols dissectors
• In the above commands, Wireshark is supposed to be in System’s Shell PATH, if it is not the case you must provide the full
command path or create a proper link
• Under Windows, if you need to use the full path for wireshark.exe and this contains spaces, use '' as escape char before
spaces and parenthesis
Serial-sniffer firmware must be compiled with the same radio (channel, modulation, …) settings as the network under investigation
Under Windows you may need to hardcode the baudrate (115200) in the serialdump.c code and recompile