Copy, search and packets specification

[mtms39]

Is there an existing issue for this?

• I have searched the existing issues.

Describe the solution you'd like

Three ideas.
On GUI you can't copy an IP or MAC to further research the connection.
A search bar for search through the log of connection for an IP, MAC or ASN.
A way to see which packets were dropped and/or filtered. It could give an output in pcap format so there could be a way to identify the source information about dropped packets. Information would be what is captured in a normal pcap, such as L3 protocol, IP and MAC address.

Is your feature request related to a problem?

No

[GyulyVGC]

Hi @mtms39, thanks for having shared so many different ideas!

Let's go in order:

On GUI you can't copy an IP or MAC to further research the connection.

This request is a duplicate of #406, which has already been implemented in #409; this is merged into the main branch and will be officially release in version 1.3.0.

A search bar for search through the log of connection for an IP, MAC or ASN.

This request was recently implemented as part of #442, which enables to filter connections by several parameters. Also this feature is merged in main and will be release in version 1.3.0.

A way to see which packets were dropped and/or filtered. It could give an output in pcap format so there could be a way to identify the source information about dropped packets. Information would be what is captured in a normal pcap, such as L3 protocol, IP and MAC address.

PCAP read & write support is planned and it's the only big missing feature before v1.3.0 (see #283 and #162).
PCAP export will allow to gain more insights about the content of each packets, but note that dropped packets won't be seen in any case, since if they are dropped it means they were never even received by Sniffnet.

---

I'm closing this issue as duplicate, but feel free to leave other suggestions if want or open an alternative issue if you have other more specific requests!