I have been working on my IPv6 network for my local network. I run 2 windows servers - a 2016 and a 2012. the 2016 is dual stack with IPv6 and IPv4 enabled, with both DHCP and DNS setup to support both stacks.
When a IPV6 device tries to get to the dashboard or Hubitat I get a failure
(fe80::::1535 is my hubitat hub)
Are you sure that HE actually supports IPv6? Given that several of their public web sites don't have AAAA records published, I suspect that I already know the answer.....
If Hubitat indeed does not support ipv6 (I have not done any research on whether it does or doesn't), you should be able to use the ipv6-mapped ipv4 address to connect from an ipv6 system.
In a web browser, you must put square [ ] brackets around an IPv6 host address in a URL. A colon in the hostname field is only allowed to separate the hostname from the port number. Multiple colons in the hostname field (like an IPv6 address uses) are invalid URL syntax, and will send most browsers off to their built-in web search tool as illustrated above.....
I was expecting the NAT64 functionality of the server stacks to do this translation for me - my problem my be stemming from not approaching the NATting correctly - I expected the DNS lookup to return IPv6 whenI entered 'Hubitat' but it's not coming back correctly.
I think - besides that HE doesn't support IPv6 (it's not showing up in the IPv6 DHCP reservations at least) - that I may have a more local problem that is an IO error (Inputting Operator).
I'm setting this aside for now and will come back to this at a later date. Thank you all for your inputs!
Is there a plan or roadmap in which IPv6 will be supported in future. I suspect ipv6 is turned off I wish it would not be. I rather not implement Nat64 just for my hubs.
According to my investigation (How to make Hubitat's web server listen on IPv6), the Hubitat does not currently serve up its main web interface on IPv6. It does, however, serve its diagnostic, "port 8081" web interface on IPv6.
Download the Hubitat app
