tshark[0][1] has been the go-to standard for CLI packet analysis for a long time. It'd be really nice if Gosniff provided some kind of documentation on how it differentiates itself from tshark.
[0] https://tshark.dev/ [1] https://blog.wireshark.org/2014/07/to-infinity-and-beyond-ca...
reminds me of termshark at https://github.com/gcla/termshark also written in golang
Neat project.
How does it compare to Wireshark' console cousin tshark?
I like how each packet is broken out into layers. Would be helpful for learning about new protocols on the wire.
Looks pretty good! Some suggestions: it should support tcpdump's command line arguments and start with them as defaults. It would be neat if packets from different interfaces can be shown in different windows.
Great project, have you seen what Etherape does? It would be interesting to include a text based scaling of what's talking to your computer.
Hey everyone, I'm the original author of this library. This is actually my first software project ever-- I'm a full-time officer in the military who was just messing around. It's extremely flattering to see this shared so publicly, but I feel the need to pre-emptively apologize to readers. This is just a hobby project for now, but I would appreciate feedback.