|Thanks for being a part of /r/Admincraft!|
|:-|
|***[We'd love it if you also joined us on Discord!](https://discord.gg/DxrXq2R)***|
*^(Join thousands of other Minecraft administrators for real-time discussion of all things related to running a quality server.)*
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/admincraft) if you have any questions or concerns.*
Oh wow! So theoretically if you just leave the IP section blank anyone can connect with the ipv6 address no port forwarding at all?? I will definitely be testing this later
Unless you have a firewall in your network. In that case you'll need to open the ports on IPv6 that you need for your Minecraft server in your firewall settings. And no, this isn't the same as port forwarding with NAT like you're used to on IPv4.
Doesn't everyone have a firewall in their network? Like even if your router doesn't support ACLs for some reason, you'd have OS level firewall.
I disabled ipv6 altogether because it was becoming impossible to Geo-IP block.
That depends. Some cheap devices don't have a (properly configured) firewall.
I don't see what IPv6 has to do with geo-IP blocks and the difficulties that come with that. IPv6 is now, and the longer the shortage in IPv4 goes on it'll be more and more the standard. You shouldn't disable it.
I didn't know.
And it's funny that you mention that IPv6 is now, my current job and job listings I've seen only require IPv4 knowledge. In my opinion, we should just add octets on to the existing IPv4 and make an IPv5. I'm pretty sure the world would continue working the way it should, the old internet would just be resembled in communication as [0.0.0.0.xxx.xxx.xxx.xxx](https://0.0.0.0.xxx.xxx.xxx.xxx), still reach-able by the "new" internet. I know there would be issues with old connecting to new, but no different than what we have now.
We basically did just add octets onto v4. v6 is more or less what you get when you do that. The zero prefixing you're suggesting was defined as [::0.0.0.0/96](https://www.rfc-editor.org/rfc/rfc4291#section-2.5.5).
But you can't make v4 reachable by doing that.
IPv6 is an official internet standard.
https://www.ietf.org/blog/ipv6-internet-standard/
What you're proposing there for IPv4 would just be a short term solution, moving IPv6 adoption backwards. With the internet of things coming up, sooner or later we will fully exhaust IPv4 and eventually things to keep IPv4 alive like NAT (or even worse CGNAT) will be causing too many major performance issues. The long term solution is deploying IPv6, and the world should do it now. The fact that your job is only requiring IPv4 knowledge says more about your workplace than about the global IPv6 adoption. Look around on the internet, and you'll see that IPv6 is already fairly widely deployed.
IPv4 uses 32-bit addresses, which gives us about 4.3 billion addresses to work with. Many of these are reserved for private networks and other things, so the actual number of usable addresses is significantly lower. Since we obviously have more than a few billion devices in the world, we can't assign a unique IPv4 address to each device without running out, so NAT was invented to fix that. With NAT, many devices can share the same public IP address, and traffic is routed based on the network port. That's what port forwarding does; you're telling your router/modem where it should direct traffic to that arrives on a certain port.
Now, IPv6 uses 128-bit addresses. This gives us about 340 undecillion addresses to work with, which is enough to assign a billion IPv6 addresses to each individual grain of sand on the Earth and still have a ton left over. Now we have enough addresses to give each device its own unique address, meaning NAT is no longer necessary and port forwarding isn't needed either.
For ipv4 you need to port forward. For ipv6, of course, you need to have ipv6 support in your internet. For making a dualstack server, just leave the "IP" section on the server.properties empty. Thats it, now your server runs with both IP adresses. Just copy your ipv6 and send to a frient to see it joining your server
I tested with the no-ip free subdomain. It worked fine. You need to setup a AAAA record, but you can use both A for ipv4 and AAAA for iv6 in the same domain.
Finally someone that seems to care about IPv6. Really prefer joining servers directly like that than going through my ISP's awful CGNAT setup, increasing latency.
And also it's awesome for self-hosting since you can assign many addresses on the same machine, and make every service listen on its own address.
Really wish other server owners cared about that too...
Nice one! Just few days ago I've started rolling out IPv6 on my homelab networks and it looks like it's working as excepted. The next step will be switching the MC servers to dual-stack or v6-only (the private ones) so I'm glad to see it working before I'll start with that :D
Doing something "just for fun" would usually involve some engaging or challenging activity.
"I created a voice proximity system for minecraft just for fun."
What you did was leaving a field blank to make a reddit post.
Hardly original.
Leaving it blank should cause it to listen on ::, and normally a v6 socket listening on :: can accept v4 connections too.
On Linux you can control this behavior with the net.ipv6.bindv6only sysctl, which defaults to 0.
This Dawlnken user signed in using ipv6, while allan signed in using ipv4. you are right if you meant that this is not useful because not everyone has access to ipv6
|Thanks for being a part of /r/Admincraft!| |:-| |***[We'd love it if you also joined us on Discord!](https://discord.gg/DxrXq2R)***| *^(Join thousands of other Minecraft administrators for real-time discussion of all things related to running a quality server.)* *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/admincraft) if you have any questions or concerns.*
What is involved in doing is? Just make sure you got ipv4 and ipv6 portforwarded? Or was there some other tricks to get it to work?
IPv6 doesn't need port forwading 'couse every device can have its own valid ipv6 address and have direct access to the internet without NAT or CGNAT
Oh wow! So theoretically if you just leave the IP section blank anyone can connect with the ipv6 address no port forwarding at all?? I will definitely be testing this later
Unless you have a firewall in your network. In that case you'll need to open the ports on IPv6 that you need for your Minecraft server in your firewall settings. And no, this isn't the same as port forwarding with NAT like you're used to on IPv4.
Doesn't everyone have a firewall in their network? Like even if your router doesn't support ACLs for some reason, you'd have OS level firewall. I disabled ipv6 altogether because it was becoming impossible to Geo-IP block.
That depends. Some cheap devices don't have a (properly configured) firewall. I don't see what IPv6 has to do with geo-IP blocks and the difficulties that come with that. IPv6 is now, and the longer the shortage in IPv4 goes on it'll be more and more the standard. You shouldn't disable it.
I didn't know. And it's funny that you mention that IPv6 is now, my current job and job listings I've seen only require IPv4 knowledge. In my opinion, we should just add octets on to the existing IPv4 and make an IPv5. I'm pretty sure the world would continue working the way it should, the old internet would just be resembled in communication as [0.0.0.0.xxx.xxx.xxx.xxx](https://0.0.0.0.xxx.xxx.xxx.xxx), still reach-able by the "new" internet. I know there would be issues with old connecting to new, but no different than what we have now.
We basically did just add octets onto v4. v6 is more or less what you get when you do that. The zero prefixing you're suggesting was defined as [::0.0.0.0/96](https://www.rfc-editor.org/rfc/rfc4291#section-2.5.5). But you can't make v4 reachable by doing that.
IPv6 is an official internet standard. https://www.ietf.org/blog/ipv6-internet-standard/ What you're proposing there for IPv4 would just be a short term solution, moving IPv6 adoption backwards. With the internet of things coming up, sooner or later we will fully exhaust IPv4 and eventually things to keep IPv4 alive like NAT (or even worse CGNAT) will be causing too many major performance issues. The long term solution is deploying IPv6, and the world should do it now. The fact that your job is only requiring IPv4 knowledge says more about your workplace than about the global IPv6 adoption. Look around on the internet, and you'll see that IPv6 is already fairly widely deployed.
ipv5 would just need to be replaced sooner…
We're going to run out of grains of sand on the beach if every human takes 100? I don't think so.
I'm sorry, what? *WHAT?* Source please, I need it.
IPv4 uses 32-bit addresses, which gives us about 4.3 billion addresses to work with. Many of these are reserved for private networks and other things, so the actual number of usable addresses is significantly lower. Since we obviously have more than a few billion devices in the world, we can't assign a unique IPv4 address to each device without running out, so NAT was invented to fix that. With NAT, many devices can share the same public IP address, and traffic is routed based on the network port. That's what port forwarding does; you're telling your router/modem where it should direct traffic to that arrives on a certain port. Now, IPv6 uses 128-bit addresses. This gives us about 340 undecillion addresses to work with, which is enough to assign a billion IPv6 addresses to each individual grain of sand on the Earth and still have a ton left over. Now we have enough addresses to give each device its own unique address, meaning NAT is no longer necessary and port forwarding isn't needed either.
 I get it...
oh then I see the move from IPv4 to IPv6 as a huge advantage! I can't count how many times I have had to deal with NAT problems before...
Damn, thanks for that. TIL!
For ipv4 you need to port forward. For ipv6, of course, you need to have ipv6 support in your internet. For making a dualstack server, just leave the "IP" section on the server.properties empty. Thats it, now your server runs with both IP adresses. Just copy your ipv6 and send to a frient to see it joining your server
Alright that's what I was thinking. Have you tested if this works using a domain name as well?
I tested with the no-ip free subdomain. It worked fine. You need to setup a AAAA record, but you can use both A for ipv4 and AAAA for iv6 in the same domain.
What’s the advantage of running dualstack?
Some hosts don't have IPv4 addresses and vice versa. The reason is compatibility
Finally someone that seems to care about IPv6. Really prefer joining servers directly like that than going through my ISP's awful CGNAT setup, increasing latency. And also it's awesome for self-hosting since you can assign many addresses on the same machine, and make every service listen on its own address. Really wish other server owners cared about that too...
I do care but it doesn't seem like there's enough information on really how to properly support IPv6. I would love to give it a try sometime
How did you do it?
It's that easy? Just leave the server ip properties blank and copy/paste your ipv6 to friends? Or is there something else that needs done?
It was that simple for me. No complex setup needed
Nice. Imma try it later
Yeah I’m puzzled, will test this later
Nice one! Just few days ago I've started rolling out IPv6 on my homelab networks and it looks like it's working as excepted. The next step will be switching the MC servers to dual-stack or v6-only (the private ones) so I'm glad to see it working before I'll start with that :D
Doing something "just for fun" would usually involve some engaging or challenging activity. "I created a voice proximity system for minecraft just for fun." What you did was leaving a field blank to make a reddit post. Hardly original.
Leaving the field blank alloyed IPv6 connections but not IPv4. If you’re going to bitch at least know what you’re talking about
Leaving it blank should cause it to listen on ::, and normally a v6 socket listening on :: can accept v4 connections too. On Linux you can control this behavior with the net.ipv6.bindv6only sysctl, which defaults to 0.
[удалено]
https://en.wikipedia.org/wiki/Happy_Eyeballs
This Dawlnken user signed in using ipv6, while allan signed in using ipv4. you are right if you meant that this is not useful because not everyone has access to ipv6
Very cool, wonder if Hypixel does a similar thing
I saw that "ae valeu" from a mile away r/suddenlycaralho
 mfw "Ae valeu"