Skip to content
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

Operation request: Improve 'Parse IP range' input options #270

Closed
n1474335 opened this issue Mar 23, 2018 · 2 comments · Fixed by #354
Closed

Operation request: Improve 'Parse IP range' input options #270

n1474335 opened this issue Mar 23, 2018 · 2 comments · Fixed by #354

Comments

@n1474335
Copy link
Member

Summary

The 'Parse IP range' operation currently accepts inputs in either CIDR notation (10.0.0.0/29) or range notation (10.0.0.0 - 10.0.0.7).

It would be useful if it could accept a list of IPs and calculate the smallest subnet which covers them all. This would simply be a matter of finding the smallest and largest IPs and constructing a range between them. e.g. the following input would generate the same output as the two examples above:

10.0.0.0
10.0.0.1
10.0.0.2
10.0.0.3
10.0.0.4
10.0.0.5
10.0.0.6
10.0.0.7
@jonebeabout
Copy link

Would this be a better improvement for 'Group IP Addresses' with a parameter to calculate smallest subnet instead of user selecting a predefined subnet?

@n1474335
Copy link
Member Author

That's certainly a possibility, but the point of the 'Group IP addresses' operation is that you can create multiple groups depending on a specific subnet size. If you want to just group the whole lot into one subnet, I think it fits the 'Parse IP addresses' operation a bit better.

BRAVO68WEB pushed a commit to BRAVO68WEB/CyberChef that referenced this issue May 29, 2022
…ored

[FIX] Don't remember collapse state, when specified in config
Fixes gchq#252
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants