Proper IPv6 support?
Posted: Wed Oct 01, 2014 4:22 pm
Currently even if the OPI device has proper IPv6 globally routable address, the op-i.me name created for the device only has IPv4 address. I did verify that my OPI device did get IPv6 address and that IPv6 address pingable from outside, but unfortunately the https service is not running on the IPv6 address.
This causes some problems for me, as the default setup does not work. In my home I have proper globally routable IPv6 which are not NATed, but the IPv4 addresses are NATed by my firewall. When I try to configure the OPI it creates name only for my external IPv4 address for my device. As I do not have NAT reflection configured on in my firewall, I cannot access my public IPv4 addresses from home, only outside the network, which means the op-i.me name created for me is useless when I am at home (I think I saw some other people complaining similar issues).
In my case the problem could be solved if the OPI would include proper IPv6 support, and also would put AAAA record for the op-i.me name.
Another option would be to include both internal and external IPv4 address in the A record, i.e. the OPI box could also send the IPv4 address seen from the inside to the server, and server could put both address to the name. So when connecting to opname.op-i.me you would get both internal and external address, and then browser can try both and use whatever works.
Is the IPv6 support on the roadmap?
This causes some problems for me, as the default setup does not work. In my home I have proper globally routable IPv6 which are not NATed, but the IPv4 addresses are NATed by my firewall. When I try to configure the OPI it creates name only for my external IPv4 address for my device. As I do not have NAT reflection configured on in my firewall, I cannot access my public IPv4 addresses from home, only outside the network, which means the op-i.me name created for me is useless when I am at home (I think I saw some other people complaining similar issues).
In my case the problem could be solved if the OPI would include proper IPv6 support, and also would put AAAA record for the op-i.me name.
Another option would be to include both internal and external IPv4 address in the A record, i.e. the OPI box could also send the IPv4 address seen from the inside to the server, and server could put both address to the name. So when connecting to opname.op-i.me you would get both internal and external address, and then browser can try both and use whatever works.
Is the IPv6 support on the roadmap?