4 ms·

In my career I have found IPv6 simply to be unnecessary. Running a network of 7 buildings with approximately 2,300 computers for now almost 2 decades and this

In my career I have found IPv6 simply to be unnecessary. Running a network of 7 buildings with approximately 2,300 computers for now almost 2 decades and this is still true. Setting edge routers to simply drop all ipv6 packets and running only ipv4 works, is simpler, is faster (than dual stack) and easier to troubleshoot. I don’t have any inheritant issues with IPv6 other than is has failed to make a case for why people like me should bother rolling it out.

UltraSane 2y ago
I've worked at companies big enough to start running out of private IPs. That isn't fun.
akvadrako 2y ago
Although it sounds like keeping IPv4 is a reasonable choice in your situation, if you merge with another company (or otherwise connect your networks) that uses overlapping private IPs it will cause issues.
- diggan 2y ago
  > , if you merge with another company (or otherwise connect your networks) that uses overlapping private IPs it will cause issues. Wouldn't this be true with IPv6 as well, assuming that both companies happened to have chosen some overlapping ranges?
  - remram 2y ago
    You don't "choose" your IPv6, they are assigned to you. Even if you used private IPs (ULA) for whatever reason, there are enough of those too not to conflict. By comparison my company uses the entirety of the private IPv4 space. `docker compose up` often fails because there is no private IP range left that is not directed through the VPN.
impeplague 2y ago
For your use case is fine today IPv4. In my case, I would love to get rid of my CGNAT IPv4 ISP address and use only IPv6.
tremon 2y ago
Imagine running a VPN hub for about ~800 customers that your IT people do remote administration for. We moved to this model because each customer tends to use their own preferred VPN agent, and multiple VPN agents installed on the same machine tend to fight each other to the death (and the host's). To avoid ip-range clashes between customers, traffic inside the hub was IPv6-only, with each customer given their own prefix. Routing permissions were based on group membership, so we had a very easy and secure way to make sure each of our users was only able to reach their own customers, and personnel changes did not require any customer-side changes.

UltraSane 2y ago

I've worked at companies big enough to start running out of private IPs. That isn't fun.

akvadrako 2y ago

Although it sounds like keeping IPv4 is a reasonable choice in your situation, if you merge with another company (or otherwise connect your networks) that uses overlapping private IPs it will cause issues.

diggan 2y ago
> , if you merge with another company (or otherwise connect your networks) that uses overlapping private IPs it will cause issues. Wouldn't this be true with IPv6 as well, assuming that both companies happened to have chosen some overlapping ranges?
- remram 2y ago
  You don't "choose" your IPv6, they are assigned to you. Even if you used private IPs (ULA) for whatever reason, there are enough of those too not to conflict. By comparison my company uses the entirety of the private IPv4 space. `docker compose up` often fails because there is no private IP range left that is not directed through the VPN.

impeplague 2y ago

For your use case is fine today IPv4. In my case, I would love to get rid of my CGNAT IPv4 ISP address and use only IPv6.

tremon 2y ago

Imagine running a VPN hub for about ~800 customers that your IT people do remote administration for. We moved to this model because each customer tends to use their own preferred VPN agent, and multiple VPN agents installed on the same machine tend to fight each other to the death (and the host's). To avoid ip-range clashes between customers, traffic inside the hub was IPv6-only, with each customer given their own prefix. Routing permissions were based on group membership, so we had a very easy and secure way to make sure each of our users was only able to reach their own customers, and personnel changes did not require any customer-side changes.