Ipv6 drives me crazy

Hi Forum,
since my internet connection changed to fiber with ds-lite i can’t connect to my homeasssistant from external. I’ve tried all i could find.

via ssh Home Assistant command line gives me three ipv6 adresses : fd6f:95dc:3a80:e9b1:xxxx:xxxx:2e23:4c4a/64, 2a01:xxxx :xxxx:200:cbd1:4985:81f4:53ea/64, fe80::xxxx:xxxx:9273:6792/64,
my fritzbox shows me 4 different(!) ipv6 for the homeassistant device
IPv6-LLA-Temporary: fe80:…
IPv6-GUA-Temporary 2a01:…
IPv6-ULA-Temporary fd6f:…
IPv6-GUA: 2a01:…
in port sharing i find the last one. I know ipv6 doesent need port frowarding but it has to be enabled, to open the firewall. So i should reach the ipv6 that is in ipv-gua and the port forwarding enabled or not?
From my internal network i can reach the first three ipv6 but not the ipv-gua, that is also used in port forwarding. From external i get of course a timeout too. My handy is online via t-online and has native ipv6 (checked with ipv6-test.com)

i’vo no more ideas. Has anyone tips for me?

many thanks for ervery tipp

is the one to care about, while you don’t need port forwardings, you still need to allow connections to that address and port from the outside in your router’s firewall.

BUT, for security reasons I’d suggest not doing all that, instead of simply setting up a road-warrior style (incoming) VPN (wireguard) on your router. Then you can connect into your home network securely and talk to all of your home devices, including home-assistant.

2 Likes

maybe i’ve not found the correct way, but i think the firewall in the fritzbox should open the port with a “forwarding rule” even if it is no forwarding in ipv6.
The rule “World to HA” TCP 2a01:41e3:51e9:6700:xxxx:xxx:xxxx:e5e5 port 443 should open that port through the firewall or not?

But i can’t reach this ip, even not from my lan and i realy wonder about that :thinking: :worried:

I’ve wireguard running for the moment but homeassistant send’s and get some vars every some minutes, fpr example my position “on the world” :joy:. So for that i had to enable a 24/7 Wireguard connection for every phone with the homeassistant app.

It should be posible to open the port?! Additional I’ve enabled ping6 for this ip in the forwarding section but the ping also doesen’t work even not from internal lan :woozy_face:

Hi all,
it was a Problem with the IPv6 Interface-ID of the fritz box. you have to change this to generate an ipv6 that ist reachable from intern and extern.

I can connect to homeassistant via ipv6 from lan and wan now.
I can’t get the amazon lamda funktion connected. The test fails with

HTTPSConnectionPool(host='xxxx.duckdns.org', port=443): Max retries exceeded with url: /api/alexa/smart_home (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f3b59889a90>: Failed to establish a new connection: [Errno -5] No address associated with hostname')

changing the domain to the ipv6 brings
Failed to establish a new connection: [Errno -9] Address family for hostname not supported.
Like other posts lambda should work with ipv6 since some month. Python is updated to 3.13.

Any ideas?

Can’t help with the lambda, but as I have a fritzbox too, what exactly did you change?


I had to change the interface id twice, after the second try it matches the end of the ipv6 gua and then it worked…

the ipv4 chekbox is not needed. the value is the “IPv6-Interface-ID”

1 Like