Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Packet Capture GUI interface

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 613 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      martin.k
      last edited by

      Hi All

      The packet capture interface has drastically changed in the latest versions. Before I was able to input an IP address I wanted to capture and also input NOT IP addresses I wanted to exclude so I could reduce "noise" and get only the data I wanted. Now that ability is gone and I can only select to include or exclude an IP address but not at the same time. Example: Before I could type 192.168.1.100, !192.168.1.200, !8.8.8.8, !123.123.123.123 . This would capture anything to/from 192.168.1.100 that was NOT to/from those IP addresses marked with !. Made for much easier troubleshooting. Now it looks like I would have to capture everything, export it and then perform exclusions in wireshark or some other program like that where before I could do this all in the GUI. Is there any way to get the old GUI functionality back or have that functionality in this new GUI?

      Thank You

      JKnottJ 1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott @martin.k
        last edited by

        @martin-k

        Don't you just love it, when they "improve" things? I'm also trying to figure out the new interface.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 1
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          The previous interface did not allow filtering at all for tagged traffic. But did not show that, it just failed to capture anything! That was the primary driver here.

          But, yes, there were likely to be some cases omitted and excluding specific address looks like one. Open a bug report: https://redmine.pfsense.org/

          Steve

          JKnottJ 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @stephenw10
            last edited by

            @stephenw10

            I still prefer to use Wireshark when I can. It allows for complex searches. Even when I use Packet Capture, I download and examine the capture with Wireshark. I also configured a small switch to use as a data tap.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            NollipfSenseN 1 Reply Last reply Reply Quote 1
            • NollipfSenseN
              NollipfSense @JKnott
              last edited by

              @JKnott said in Packet Capture GUI interface:

              I still prefer to use Wireshark

              Same here.

              pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
              pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                https://redmine.pfsense.org/issues/14679

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.