openwisp / openwisp/openwisp-radius
[feature] Allow IP range to for allowed freeradius hosts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 445
- Forks
- 234
- Avg merge
- 20h 21m
- Merged PRs (30d)
- 19
Description
Currently, we can only give IP address of freeradius server allowed to interact with openwisp-radius by using the OPENWISP_RADIUS_FREERADIUS_ALLOWED_HOSTS option but this is not sufficient if the IP is not fixed, example in docker-openwisp, the IP address can be in range "172.18.0.0/16".
Hence, we need to allow user to enter IP range as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OPENWISP_RADIUS_FREERADIUS_ALLOWED_HOSTS setting and its documentation link to understand the current accepted format. Trace where allowed hosts are parsed and checked, then add support for CIDR ranges such as 172.18.0.0/16 and verify that both individual IP addresses and ranges are accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100