[SOLVED] IPv6RD working but not able to detect external IP?

[jafinn]

I'm not sure if this is an issue or if I'm just misunderstanding something.

I've got IPv6 set up and it's working fine. I can ping6 google.com and I can access ipv6.google.com just fine from any device on my network. IPv6 test sites also reports everything fine.

So today I decided to include my IPv6 in my DNS. I've got a CNAME pointed at DuckDNS which works fine for IPv4 but fails for IPv6 with "Aborted IPv6 detection: no address for re1"

When checking the WAN interface (Interface widget and Interfaces -> Overview) it does in fact seem like it doesn't have a global IPv6, just a link-local address. The LAN interface has a global address.

I can however ping6 google.com just fine from my WAN interface, it also shows me the WAN IPv6 address.

--- google.com ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 16.717/16.789/16.884/0.070 ms


So, shouldn't OPNsense show that the WAN interface does in fact have an IPv6 configured or is it just something misconfigured at my end?

[tbandixen]

I have the same occurance.

Although I can't acces ipv6.google.com from a device, but I can ping it from WAN/LAN/DMZ interface, but this is another issue (on my side I think).

[jafinn]

Have you tried http://ipv6-test.com/ ?

Might help you understand where it fails.

Have you enabled IPv6 on your devices? Do you have a link-local address at least?

[tbandixen]

Yes, I did, IPv4 is default in browser, ipv6 enabled on the device, IPv6 connectivity not supported, DNS4 + IP6 and DNS6 + IP6 unreachable, but DNS6 + IP4 is reachable.

[jafinn]

Can you ping 2606:4700:4700::1111 ?

[tbandixen]

On the FW directly yes:

Code Select Expand

--- 2606:4700:4700::1111 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 2.514/2.566/2.616/0.042 ms

To check that from a device I have to test it from inside my LAN. I dont have VPN with IPv6 support yet.

[jafinn]

Yeah, I was thinking from a LAN device to see if it's simply a DNS issue. Thinking about it it's most likely not since you can ping6 google.com from the firewall itself.

I'd check if your device actually has an IPv6 first. They'll have an fe80 or something address at least but you'll also need a global one in the same scope as your LAN interface.

Have you enabled RA and DHCPv6? Have you allowed IPv6 ICMP through your firewall?

Just a heads up, I'm fairly new to IPv6 myself and are still figuring things out so I'm probably not the best person to help troubleshoot this

[franco]

Think I found the bug, but cannot fix this week:

https://github.com/opnsense/plugins/issues/1202

There's no special IPv6 handling present but required for e.g. 6rd.


Cheers,
Franco

[jafinn]

That's great;) This was just for me playing around so definitely no rush on my part, appreciate all the hard work you do:)

Could this also be related to the interfaces widget not showing an IPv6?

[franco]

Yes, I think so. Please ping me next week if I'm being lazy.  :)

Thanks,
Franco

[jafinn]

Hi

It's been a little more than a week:) DDNS works as expected now with IPv6. Thank you very much for that:)

It's not really an issue but just thought I'd let you know that the Interfaces widget still doesn't show an IPv6 (at least for me) and the WAN interface doesn't either (Interfaces -> Overview). I can't really be more helpful than that though.

[franco]

Ok, getting closer. :)

I have to ask for a ticket here, not too high on priority, but should not be forgotten.


Thanks,
Franco