You can name your pipe anyway you like and place it in any folder you wish. First we created a named pipe as follows:.Ssh "tcpdump -s 0 -U -n -w -i lo not port 22" > /tmp/board įollowing are the steps that we performed on the local machine to pipe the results of tcpdump on the remote machine on the wireshark on the local machine. Just execute the following on the machine with the GUI (a.k.a.
there was a user that had remote ssh rights on the remote machine that also had the rights to execute tcpdump on the needed interfaces.ssh server was installed on the remote machine and allowed us to connect to it remotely.tcpdump was installed on the remote machine.
#Install tcpdump on unifi full
So, in order to process the results of the tcpdump command we decided to use another machine that had a full working window manager installed and was able to operate the GUI version of WireShark.įor our solution to work some requirements were expected to be met by the embedded device (a.k.a. That device was an embedded device, for which it did not make sense to even consider installing a window manager on it. Recently we needed to process the results of a tcpdump command using the GUI version of WireShark on machine that did not have a window manager installed. 30 November 2017 in Applications tagged execute over ssh / local / mkfifo / named pipe / pipe / pipe over ssh / remote / ssh / tcpdump / wireshark by Tux
0 kommentar(er)
