bunkerity / bunkerity/bunkerweb
[FEATURE] Allow banning IP ranges / subnets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11k
- Forks
- 642
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 42
Description
### What's needed and why?
Hi,
I would like BunkerWeb to support banning IP ranges / subnets (for example 192.168.1.0/24) in the same way it already supports them for whitelist and blacklist rules.
At the moment, banning through the UI appears to work only IP by IP. There are cases where I want to temporarily ban an entire subnet or IP range through the UI, rather than adding many individual IP bans one by one.
### Implementations ideas (optional)
It should be possible to add a ban for:
- a single IP, as today,
- a CIDR subnet such as `192.168.1.0/24`,
- possibly other supported range formats (`192.168.1.10-100` for example).
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
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 by tracing the UI ban flow and compare it with the existing whitelist and blacklist handling for IP ranges or subnets. Confirm where bans are validated and persisted, then verify that single IPs and CIDR subnets work through the UI; support for other range formats should be resolved from the existing project behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100