NEM & SYMBOL: IPv6 Support

As we all now, IPV4 public addresses are running out. Upgrading to IPV6 (with almost idefinitely many addresses available) mitigates this bottleneck.
People don’t really use it yet.
At the moment, most legacy system configurations opt to “switch off IPV6 Support” (i bet your home routers and various devices have IPV6 support but you never turned it on).

Which brings me to the question(s):
1. Is Symbol fully IPV6 compatible?
2. Can we choose and configure not to use IPV4 but only the new standard?
3. Would IPV4 nodes be talking & in sync with IPV6 nodes?

It could be easier to host one larger physical server, get a block of IPV6 public IPs and then host 100 VMs inside the server (hint: to host SYMBOL Testnet nodes :slight_smile: ) and not need to expensively purchase 100 IPV4 public IPs.

Disclaimer: I did not read through all the NEM&SYMBOL documentation and might have overlooked configuration and behaviour info on IPV6. If that’s the case, please someone guide me to the right resources.

For completeness: Link to the previous community member question regarding this (Sep/2015): Does Nem network supports IPV6?

6 Likes

Good question.

1 Like

Only IPV4 is supported at the current time.

You can open a GitHub issue for IPV6 support.

1 Like

Done. https://github.com/nemtech/catapult-server/issues/63

2 Likes