gopacket VS gopcap

I have seen pcap but not packetz, thanks. Pcap looks unfinished and packetz has not been updated in a long time, but they might be able to make a working capture program. However the popularity and features available in Go regarding packet capture makes it very hard to beat. E.g. the Google gopacket library has 5.6k stars on github and as pretty much every feature you'd want for this sort of stuff built in.

eCapture implements the feature of saving a pcapng file by eBPF TC, and supports TLS Master Secret Key capturing by eBPF Uprobe. Also, gopacket's DSB feature is supported, based on Decryption Secrets Block (DSB)

Well, there is https://github.com/google/gopacket/, you have a package that uses CGo, `pcap`, and then there is `pcapgo`, native Go implementation. Doesn't have all the features but in my case, I was able to use it and remove CGo.

I will capturing TCP packets by gopacket/pcap.

For example, gopacket uses libpcap by default for capturing the traffic. Libpcap doesn't support network namespaces and we can't ask it to listen to traffic on a different namespace. However, we can change the network namespace of the calling thread and then start libpcap to see the traffic on a different namespace.

https://pkg.go.dev/github.com/google/gopacket/routing - Linux only and not working correctly and not actively maintained

Among the many early review articles of pre-1.0 Go, a common criticism was the lack of generics, or parameterized types. Having used Go for my personal projects since late 2009 and professionally since 2013, I kind of understood the criticism because it was the kind of feature that you would naturally expect in a new language as other modern languages of the time would often feature generics in some shape or form. C++ went to the extreme with it, as its template system goes beyond just type parameterization and was even found to be Turing-complete. Practically though, in the several years of actively using Go pretty much every work day, writing many tens of thousands of line of code, I've only ever come across one situation where I thought that parameterized types would have been really handy and would have made it so much easier to write less repetitive code.