-
-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bogon tag (and detailed address type identification) #209
Labels
enhancement
New feature, request, or improvement
Comments
@nitefood I gave a more in depth look to your |
@GyulyVGC you're welcome, I'm glad you like it! Keep up the great work :-) |
@all-contributors please add @nitefood for ideas. |
I've put up a pull request to add @nitefood! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: