• Hello,

    I am trying to pipe tcpdump over ssh to my nix laptop running wireshark. The first problem I had was the console coming up when I used the admin account so I created a new user via the user manager. My new user was able to ssh in but could not run tcpdump so I added the new user to the wheel group. I can elevate this user from su - but when I run su tcpdump I get a response of "su Sorry". I wish I was better with BSD but everything I find online and running the command groups username this should be working. This is the command I am trying to use:

    ssh user@XXX.XXX.XXX.XXX su tcpdump -U -w - 'not port 22' | wireshark -k -i -

    Thanks in advance

  • @rfinterference:

    ssh user@XXX.XXX.XXX.XXX su tcpdump -U -w - 'not port 22' | wireshark -k -i -

    su is not sudo and sudo is not present in pfSense.
    You need to give the remote system two commands:
    1. su to switch to super user mode
    2. tcpdump to get the packet capture.

    I don't know how you would get the two commands to the remote session: maybe you need to dump a shell script on the remote system and start that.

  • Netgate Administrator

    Just use root to avoid the menu?  :-\


  • Root and admin  both start with the console.

  • Netgate Administrator

    You can usually use services such as SCP using root to avoid the console menu issue. The admin account cannot be used for that.
    Have you actually tried using root?


  • Yes I tried using root but just as with the admin account it goes to the console. I took another guys advice and tried to script it but su - or su root completely breaks the script.

  • I am trying to script this using expect currently. Hopefully this will work.

  • Rebel Alliance Developer Netgate

    I've done that before, using root and ssh keys. I cover the technique in the book in the packet capturing chapter.

    wireshark -k -i <(ssh root@192.168.x.x tcpdump -i em0 -U -w - not tcp port 22)

    Using su would really break that. If you must use an alternate account, you'll need to install sudo on the firewall and set it to allow at least tcpdump to run without a password for your user/group.

  • Thanks everyone that replied. I had looked into installing sudo but decided I didn't want to take the chance on breaking anything with the production machine.

    In case anyone is interested the solution I used "fastest implementation" was to put taps in place on both sides of the pfsense box with a tiny linux computer connected to both taps and the lan. Now I can troubleshoot till my eyes bleed.

    Best Regards