Valid IPv6 ranges syntax is described in
https://aprelium.com/data/doc/2/abyssws-win-doc-html/ipv6.html .
For example aaaa:bbbb:cccc:dddd:* should be written like aaaa:bbbb:cccc:dddd::/64 .
tfh wrote
Also a feature double feature request:
* Please make it possible to also have a server-wide list of IP's you can block
* Make it possible to define a custom error page for the blocked IP's instead of using the 403 status code.
The first suggestion is easy and can be added fairly quickly.
The second one is a bit complex despite looking straightforward. When a client is blocked, the server can only send error 403 back with some HTMl or plain text body. This could be done with the custom error pages right now. But most people design such page with links and references to the same site for images and CSS. So those are blocked too but will result in an ugly broken page.
Your 403 error page should be self-sufficient or reference media/CSS files hosted on another non-blocked domain (a CDN for example.) The 403 error page should also be declared as a virtual path for it to be served as the body of a proper 403 error. Otherwise, if it's an URL, error 403 won't happen per se and the client will be redirected with a status code 302 to the declared URL.