The bug
The /ban-ip command doesn't work with IPv6 addresses and yields this error instead: Expected whitespace to end one argument, but found trailing data
How to reproduce
Run:
/ban-ip 2001:db8::1:2:3:4→ ❌ It actually doesn't ban the ip address, but throws an error instead
Linked issues
is duplicated by 1
relates to 2
Comments 10
the ban-ip should ban the first 64 bits because it's possible for the client to change the last 64 bits
@unknown: no, it should ban exactly the IP address that's provided within the /ban-ip command. But indeed, having CIDR support would be a neat feature, like /ban-ip fc00::/7
miwob: I dit not mean it that way. I am word blind
I thot of Windows's ipv6 privacy feature that generate a temporary ipv6 address to use so it doesn't make sense to ban all 128 bits in that case, so i will like to see eg /ban-ip fe80::/64
This is still a problem and RIPE NCC is soon running out of IPv4 so it is going to be a bigger problem.
Can confirm this happens on 1.10.2.
If you do /ban-ip <playername> on a player logged in over IPv6, then it will ban the ip representing the first 2 bytes, i.e. if you're logged in from 2605:xxxx:xxxx.... then it will add the ip "2605" to banned-ips.json.