Stefan Agner

> @pvizeli is there anything I might be able to do in order to help this PR move forward? I have built an addon that would benefit greatly from being...

This turns out to be problematic for OTBR if multiple Home Assistant OTBRs are used in the same network: Currently, they all get the hostname of the add-on, which leads...

@frenck yes, thanks for reminding! I've reopened the existing PR https://github.com/home-assistant/developers.home-assistant/pull/1310. Documentation still applies as is.

Implemented by #4514.

> Not being able to use IPv6 is a real bummer to me as well. @bikeshedder just to be clear: Home Assistant OS supports IPv6 just fine! You can also...

> Many do unintentionally, because the provider only allows full IPv6 and crippled IPv4. I guess you talk about CGNAT? That use case is handled well by the current implementation...

> I think it's (unfortunately) still important to consider and have checks for broken IPv6 connectivity with fallbacks for addons. Well but the same could be said for Home Assistant...

I've started a related discussion about `macvlan` support in Supervisor, see https://github.com/home-assistant/architecture/discussions/1034. As the title of this discussion says, this issue is about IPv6 for network isolated add-ons. Introducing `macvlan`...

@mraerino I guess this is more or less what #3780 implements then, no? What I am a bit worried is how add-ons typically behave in environments which do not have...

I have the same concern as @Giga-Pudding has here: How do the add-ons behave in absence of IPv6 support on the host side... @mraerino I don't quite understand your setup...