Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
network-debugging [2018/02/27 10:11] klueppel created |
network-debugging [2021/11/19 07:58] (current) dodenhoeft |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== **Advanced network debugging** ====== | + | ====== Advanced network debugging ====== |
| In some cases it might be useful to see the live network traffic in wireshark and not only the tcpdump output on the console. | In some cases it might be useful to see the live network traffic in wireshark and not only the tcpdump output on the console. | ||
| - | __Prerequisites:__ | + | === Prerequisites:=== |
| * Netmodule Router | * Netmodule Router | ||
| * Wireshark on your local computer. | * Wireshark on your local computer. | ||
| Line 10: | Line 11: | ||
| We can get the output of tcpdump via ssh and pipe it directly in wireshark, no need to save the dump and load it in wireshark. This can be done on linux and windows too. | We can get the output of tcpdump via ssh and pipe it directly in wireshark, no need to save the dump and load it in wireshark. This can be done on linux and windows too. | ||
| - | __Linux:__ | + | === Linux: === |
| - | ssh root@192.168.1.1 tcpdump -U -i any s0 -w - 'not port 22' | wireshark -k -i - | + | <WRAP center round box 100%> |
| - | + | ssh root@192.168.1.1 tcpdump -U -i any -w - 'not port 22' | wireshark -k -i - | |
| - | __Windows:__ | + | </WRAP> |
| + | === Windows: === | ||
| + | <WRAP center round box 100%> | ||
| plink.exe -ssh -pw admin01 root@192.168.1.1 "tcpdump -i any -vn not port 22" | "C:\Program Files\Wireshark\Wireshark.exe" -i - | plink.exe -ssh -pw admin01 root@192.168.1.1 "tcpdump -i any -vn not port 22" | "C:\Program Files\Wireshark\Wireshark.exe" -i - | ||
| + | </WRAP> | ||
| You can specify the interface with the -i parameter e.g.: "tcpdump -i lan0 -w - 'not port 22' | You can specify the interface with the -i parameter e.g.: "tcpdump -i lan0 -w - 'not port 22' | ||
| We recommend you to exclude the SSH port (22) that you only caputre the traffic you are interested in. | We recommend you to exclude the SSH port (22) that you only caputre the traffic you are interested in. | ||