Giuliano Bellini

@phxyz12 @rafal06 after some delays, I've finally come up with an rpm package for Sniffnet. Could you kindly try if it works fine? Thanks in advance. [sniffnet-1.2.0-1.x86_64.rpm.zip](https://github.com/GyulyVGC/sniffnet/files/11492415/sniffnet-1.2.0-1.x86_64.rpm.zip)

[A new release](https://github.com/GyulyVGC/sniffnet/releases/tag/v1.2.0) including the RPM package has just been published!

For the "No traffic has been observed yet. Waiting for network packets..." I can do nothing: it depends on what pcap is actually able to sniff in term of kind...

> Not sure if it's the same issue, but I get the same message for the `any`, `wg0` (wireguard), and `tailscaled0` interfaces. `wlan0` works though. > > For reference, i'm...

If no packets are received through a given interface, the problem is not related to Sniffnet itself but to what [rust-pcap](https://github.com/rust-pcap/pcap) is actually able to sniffs.

If you click on the network host you are interested in, you will see a list of its connections. Isn't it?

Sniffnet currently defines a "connection" by the network-5-tuple: - Source IP - Source port - Destination IP - Destination port - Transport protocol If you see only one connection it...

Sniffnet can see everything directly incoming/outgoing to/from your network card. If it doesn't see some specific interfaces, it's a problem related to pcap which I'd like to better understand myself.

I think I've finally understood the nature of this problem: so far Sniffnet was only able to read interfaces whose "link_type" was Ethernet. Today I've found out that I wasn't...

Related issue: https://github.com/JulianSchmid/etherparse/issues/78