-
Notifications
You must be signed in to change notification settings - Fork 63
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
Feature: Add CIDR detection #13
Comments
Hi, Thanks! I will look into this.... Best, |
Hi, Is this the output you were looking for? (edit: I see the IPV6 error you were talking about and im looking into it) Contents of
|
@Defirence I saw your now deleted comment. This project is not malicious and has various practical uses 😆 . Your Github ticket will be ignored. |
Hi, @borestad I think I got the Regex correct how does this look?
Best, |
Hi @Drew-Alleman ! Sorry for late reply, my inbox (work related) had 1600 messages, and I missed that you wrote the other day! Looks great. 👍 like:
... but for now, this is excellent! I tried to write/improve the regexp myself yesterday evening, but was apparently to tired. Great work! 😊 |
Hi, Glad to hear it works for you. I am going to update the IPV4 and IPV6 regex for what I have now.
I might create a plugin for extracting CIDR information specifically. Edit: After seeing your new issue I probably will do this, and have Best, |
This sounds great! :) |
Hi, I will try to get this rolled out this weekend. Best, |
Hi!
Currently DataSurgon can't handle CIDR-ranges:
Example:
Result
(Also, by testing this I found a bug where it doesn't detect double colon in ipv6 urls) 😁
https://www.ibm.com/docs/en/i/7.5?topic=concepts-ipv6-address-formats
The text was updated successfully, but these errors were encountered: