Bogon tag (and detailed address type identification)

[GyulyVGC]

Discussed in #208

^{Originally posted by nitefood May 21, 2023}
Just like for multicast addresses (which you already identify and tag accordingly), I'd like to suggest a bogon tag, along with more detailed address type identification (e.g. RFC1918 private space, or RFC6598 CGN space), to get rid of many unnecessary "unknown location" occurrances.

For example, these are some regex patterns I used for a similar purpose.

[GyulyVGC]

@nitefood I gave a more in depth look to your asn project and it does really cool stuff.
I'm looking forward to integrate in Sniffnet next major release some other features, such as IP reputation.
Thank you for such an inspiring resource 🙏

[nitefood]

@GyulyVGC you're welcome, I'm glad you like it! Keep up the great work :-)

[GyulyVGC]

@all-contributors please add @nitefood for ideas.

[allcontributors]

@GyulyVGC

I've put up a pull request to add @nitefood! 🎉

[GyulyVGC]

Hey @nitefood I'm about to implement this feature in Sniffnet.
It seems that your code is tagging bogon IPv4 addresses but not IPv6 ones.
Any reason for this?

For reference, here I've found a list of the relevant bogon ranges, both IP v4 & v6.

[nitefood]

Hey @GyulyVGC,

there's no particular reason, asn only accounts for the ULA range (fc00::/7) in the privateregex expression and judging from the comment I wrote back then (4 years ago), I snatched this regex off StackOverflow as-is.
I remember meaning to expand to other bogon IPv6 ranges, but didn't add a TODO remark and therefore never got around to.

Coming soon, I guess!

[nitefood]

I've added the relevant IPv6 bogon patterns in the latest commit. If it can be of any help, in order to better visualize the text patterns required, I used this CIDR-to-range calculator.

Thanks for the handy bogon list you linked!

[GyulyVGC]

Awesome! Thanks for the resources!