Fix: Enable IP range configuration for FreeRADIUS API access #556
+14
−10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to issue #229 Allow IP range to for allowed freeradius hosts
Description:
This pull request updates the system to support IP address ranges (using CIDR notation) for the OPENWISP_RADIUS_FREERADIUS_ALLOWED_HOSTS setting and the organization's RADIUS settings. Previously, it only allowed individual IP addresses, which was a limitation in environments where the FreeRADIUS server’s IP address could change.
Now, administrators can specify a range of allowed IP addresses instead of just single IPs, making the configuration more flexible and reliable. The update ensures that the system correctly handles both individual IPs and ranges during authentication and adds better error handling for any incorrect IP range settings.