Ban assistant to avoid mistakes #2340

New issue

Open

opened 2026-02-20 22:04:59 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 22:04:59 -05:00

Owner

Originally created by @promi on GitHub (Dec 17, 2021).

Context

I have banned an IPv6 address from the log (see also #3540), but accidently set the address mask to /32 because that is the default for the ip mask, but only makes sense for IPv4 addresses.

Description

To fix this problem I propose that a ban assistant be written where you have a selection like this:

I would like to ban:
a) A user based on her user name
b) A user based on his certificate
c) An IPv4 address or IPv4 address range
d) An IPv6 address or IPv6 address range

The assistant can then create a ban entry with sane defaults based on the selection. In a second step there could also be an option to select a time limit in a human way (e.g. 1 hour, 1 day, 30 days, etc.)

Mumble component

Client

OS-specific?

Additional information

No response

Originally created by @promi on GitHub (Dec 17, 2021). ### Context I have banned an IPv6 address from the log (see also #3540), but accidently set the address mask to /32 because that is the default for the ip mask, but only makes sense for IPv4 addresses. ### Description To fix this problem I propose that a ban assistant be written where you have a selection like this: I would like to ban: a) A user based on her user name b) A user based on his certificate c) An IPv4 address or IPv4 address range d) An IPv6 address or IPv6 address range The assistant can then create a ban entry with sane defaults based on the selection. In a second step there could also be an option to select a time limit in a human way (e.g. 1 hour, 1 day, 30 days, etc.) ### Mumble component Client ### OS-specific? No ### Additional information _No response_