Ahmed Elsabbahy

@petemounce Any thoughts on this?

Marked as approved. Windows and Mac are community supported, so I'll review/merge changes but I won't be the one making the change on this one.

The attribute model does seem cleaner, but doesn't handle collisions or duplicates. Another option is the ability to overwrite the key attribute, there's already work that's been done on this...

This is still being discussed, not stale

Going to just mark the 2nd approach as the approved one for now. I'll work my way towards it a resource at a time, and will accept PRs that move...

I think this would be great once the #576 lands. At that point, there can be a custom matcher `cidr-constraint` or something like that.

> because the hypothesis is that the output rendering is trivially fast That would be my vote too. Once cache on the results should be enough for now.. if later...

GOnetstat isn't really "netstat" per say, but rather a low level library that parses `/proc/net/*` files. I'll look into the impact of `net.ipv6.bindv6only` on the proc files and see if...

`ss` does not print out the correct values either, it just says tcp for all, for example: netstat: ``` $ netstat -lna|grep 8080 tcp6 0 0 :::8080 :::* LISTEN ```...

**Copied from duplicate thread:** Random thought.. maybe it would be simpler to get rid of the whole `tcp:` vs `tcp6:` thing all together. We can collapse the tests into two...