/ban-ip doesn't work with IPv6 addresses
Linked Issues
is duplicated by1
- Unresolved
henrik
- 21
- 12
- Confirmed
Normal
- Platform
- Commands Networking
- ban-ip command ipv6
1.9-pre2 - 1.21
1.9-pre2 1.9-pre3 1.9 1.9.1-pre3 1.10-pre1 1.10 1.10.2 16w32b 16w38a 16w42a 1.11 16w50a 1.11.1 1.11.2 17w06a 17w13a 17w17b 1.12-pre1 1.12-pre2 1.12-pre3 1.12-pre5 1.12-pre7 1.12 1.12.1 1.12.2 17w45b 17w47a 18w09a 18w22c 1.13.2 19w08a 1.14.2 1.15-pre4 1.15 1.15.2 1.16.1 20w27a 20w49a 21w03a 1.16.5 1.17-rc1 1.17 21w38a 1.19.2 1.21
Created Issue:
/ban-ip don't work with IPv6
/ban-ip don't work with IPv6
What I expected to happen was...:
The ip i put in in /ban-ip is bandWhat actually happened was...:
the ban-ip command reported an invalid ip for an valid ipv6 addressSteps to Reproduce:
1. type /ban-ip ::1 on a server ware you have op. ::1 is equals to 127.0.0.1
2. errorEnvironment
Windows 10
java 1.8.0_74
/ban-ip doesn't work with IPv6 addresses
/ban-ip don't work with IPv6
What I expected to happen was...:
Theipi put inin/ban-ip is bandWhat actually happened was...:
the ban-ip command reported an invalidipfor anvalid ipv6 addressSteps to Reproduce:
1. type /ban-ip ::1 on a server ware you have op. ::1 is equals to 127.0.0.1
2. error/ban-ip don't work with IPv6
What I expected to happen was...:
The IP i put into /ban-ip is bandWhat actually happened was...:
the ban-ip command reported an invalid IP for a valid ipv6 addressSteps to Reproduce:
1. type /ban-ip ::1 on a server whare you have op. ::1 is equals to 127.0.0.1
2. error
/ban-ip don't work with IPv6
What I expected to happen was...:
The IP i put into /ban-ip is bandWhat actually happened was...:
the ban-ipcommand reported an invalid IP for a valid ipv6 addressSteps to Reproduce:
1. type /ban-ip ::1on a server whare you have op. ::1 is equalsto 127.0.0.1
2. error/ban-ip doesn't work with IPv6 addresses
What I expected to happen was...:
The IP i put into /ban-ip is bandWhat actually happened was...:
The ban-ip command reported an invalid IP for a valid ipv6 addressSteps to Reproduce:
1. type /ban-ip ::1 on a server where you have op. ::1 is equal to 127.0.0.1
2. error
/ban-ip doesn't work with IPv6 addresses
What I expected to happen was...:
The IP i put into /ban-ip is bandWhat actually happened was...:
The ban-ip command reported an invalid IP for a valid ipv6 addressSteps to Reproduce:
1. type /ban-ip ::1 on a server where you have op. ::1 is equal to 127.0.0.1
2. error
is duplicated by
Thank you for your report!
We're tracking this issue in MC-97885, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
π Bug Tracker Guidelines – π¬ Community Support – π§ Mojang Support (Technical Issues) – π§ Microsoft Support (Account Issues)
π Project Summary – βοΈ Feedback and Suggestions – π Game Wiki
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.
the ban-ip should ban the first 64 bits because it's possible for the client to change the last 64 bits
henrik: 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
Yes. That's why I said support for CIDR notation would be an awesome feature to have.
Please do not mark unreleased versions as affected.
You don't have access to them yet.
This is still a problem and RIPE NCC is soon running out of IPv4 so it is going to be a bigger problem.
This is still a bug in 1.15 pre-releace4. Both the RIPE NCC and ARIN is completly out of IPv4.
Affects 20w49a
also οΌpardon-ip doesn't work with ipv6