Node on IPv4 and IPv6

[Vicente]

I’ve changed internet providers. I now have IPv4 and IPv6.

Can I configure the node to work using IPv6? With IPv6, is it no longer necessary to open ports?

I now have the nodes unconfigured. If I add IPv6 to the configuration, they appear unconfigured.

[arrogantrabbit]

You can have dual stack, yes. You don’t need to masquerade with IPv6 but you still need to allow incoming traffic on that port on the firewall. You also need to add AAAA dns record.

What do you mean by “unconfigured”? If the status shows Online you are good. If it does not - you are not.

But why are you trying to add ipv6? There is nothing to be gained except more complexity with your setup.

[Vicente]

@arrogantrabbit

dual stack

He looked at the router. The router was misconfigured. I changed the settings. It now appears configured and online.

Is it difficult to set up dual stack?

[arrogantrabbit]

Once you get lan devices assigned IPV6 addresses, (all the SLAAC or DHCPv6, prefix delegation. etc), then it’s just this:

@arrogantrabbit

you still need to allow incoming traffic on that port on the firewall. You also need to add AAAA dns record.

Check this too:

IPv6 does not work?

To use a dual stack, your external address should be resolved to the both stacks. It’s nothing to do with config.yaml, except update the external address, if you don’t have a DDNS domain yet before. You can use this article for noip: https://www.noip.com/support/knowledgebase/create-hostname-ipv6-address-aaaa-record-support-question-day/ To enable IPv6 on docker you can use this article: https://docs.docker.com/config/daemon/ipv6/ But I don’t think it’s needed. I don’t have a IPv6 to check

[RecklessD]

@Vicente

Is it difficult to set up dual stack?

It’s a learning curve, but once setup, works mostly like ipv4. Most of my internet traffic still uses ipv4 though (around 80%).

[Vicente]

I use dynu ddns. It detects IPv4 and IPv6.

IPv6 detects me with the port closed.

Is this okay?

Do you mean firewall on the router or in Windows?

I’m not going to configure it; there’s nothing to gain.

[arrogantrabbit]

@Vicente

port closed.

Is this okay?

Obviously, not.

@Vicente

firewall on the router or in Windows

Both. You need to do everything you did for IPv4, except DNAT).

When you create “port forwarding” rule on most routers two things are happening:

• a firewall rule is created to allow traffic on that port to pass through
• A DNAT rule is created to translate traffic for lan machines.

With IPv6 you don’t need the latter, but (hopefully!) still need the former.

[RecklessD]

@Vicente

Do you mean firewall on the router or in Windows

You will need to run Dynamic DNS on client, not router, they will be different IPv6 addresses.

On router/firewall you need to allow the inbound IPv6 traffic to client ip/port(s). No DNat or port forwarding.

on client firewall you need to allow the inbound IPv6 traffic to IP/ports for the interface. Same as for ipv4.

There are benefits to IPv6. After going dual stack, my kids complain less about lag on the xboxs.
No more reverse proxy to run multiple services on same port, as you have as many “external” IP addresses as you have IPv6 enabled devices.