It runs and I can see that it listens but no packets on Wireshark. Tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes So this is the command that I'm using (from Wireshark directory): 'c:/Program Files/Putty/plink.exe' -ssh -batch 'ssh -q tcpdump -s 0 -U -i eth0 -w - 'not port 22''|'Wireshark.exe' -k -i.

I have to capture traffic from the QNX system and, in order to do that, I need to go through the Linux system. The scenario is: Windows10 -> SSH to Linux -> SSH to QNX #14 direct-tcpip: listening port 8080 for port 80, connect from 127.0.0.1 port 55456 to 127.0.0.So I'm trying to capture traffic from a remote system but I get no packets on Wireshark. I have tried changing the 80 to 8080 or similar and still the same issue.ĭebug1: Connection to port 8080 forwarding to port 80 requested.Ĭhannel 13: open failed: administratively prohibited: open failedĭebug1: channel 13: free: direct-tcpip: listening port 8080 for port 80, connect from 127.0.0.1 port 55455 to 127.0.0.1 port 8080, nchannels 15ĭebug3: channel 13: status: The following connections are open: This results in 'channel 14: open failed: administratively prohibited: open failed' that seem to match the port 80 request.

I use this to connect to a KVM port on a remote server. Ssh port forwarding broken? Did some thing change that would prevent me from port forwarding privileged ports?

Wireshark tcpdump