message-io VS sniffnet

message-io: a networking library meant to be very simple, built on mio.

Another one I know about, but have not looked into yet, is message-io.

I'm working in a transport network library that possible fits as a building block for yours and solves the problem of using different underlying transports: message-io

Here is benchmarks

I think https://github.com/lemunozm/message-io can be a good candidate.

The idea behind message-io is not to populate a current transport with a lot of options/profiles/modifications... this obfuscates the default way of working with it. Instead, if you want to build some behaviour on top of it, it is as easy as making an adapter! Following this pattern, you can split the way of using the library from the behaviour of the transport, keeping the things simple.

The initial purpose was to show the capabilities of https://github.com/lemunozm/message-io Nevertheless, Termchat is growing and needs to polish some of its features. At this point it is not for real-world use but I hope to reach this target.

Sniffnet is an open source, Rust-based network monitoring tool I’ve been working on for almost two years now.

As described in this issue the GUI library used by Sniffnet doesn't support yet text selection, but they are working on it and hopefully soon it will.

I’ll be personally talking about Sniffnet, the Rust-based network monitoring tool I’m working on: I’m so excited to share it with the world!

I'm the creator and maintainer of Sniffnet, an open-source network monitoring tool developed in Rust.

Sniffnet is a Rust-based network monitoring tool to help everyone inspect their Internet traffic.

Sniffnet, a cross-platform app to comfortably monitor your Internet traffic written in Rust, has now a website. See the related discussion on Github.

Another option is https://github.com/GyulyVGC/sniffnet if you are just trying to see what packets are flowing and who's talking. It's nowhere near as powerful as Wireshark (nor is it designed to be) but it might not be as confusing for someone who is new to network packet sniffing. I think the biggest downside is the Windows install file doesn't come with the NPCAP driver, I think they really need to bundle that with the installer the way Wireshark does, otherwise people may not get it to work.