Domoticz

I have defined a local network for ipv6 in the Domoticz settings, but it seems like Domoticz doesn't accept it as a local network. I have to login all the time even when I access with http port 8080

I also discovered that if I access (locally) my domoticz, I get an password prompt if I connect to the server with dns name, but if I access writing the ip address I can access the website without having to enter my name and password. (This is due to the fact that the browser preferres ipv6, when getting the ip address from the DNS)

So http://servername.mydomain.se:8080 makes me have to login even though this is on the local network but if I enter
http://192.168.0.45:8080 I come to the website without name and password, as expected.

the different behaivour depends on your internet provider:
if you are not propted with user and pass, I assume you have all your local network in the Domoticz server IP list (or at least the PC source IP address)...

if you call you server using the ddns you access it through the wap IP address... in some cases the router itself will tranaslate the wan IP to local IP, in some other (vodafone Italy) the gateway wil drop your request (you will be never able to get into your LAN using the WanIP from your lan...)

Domoticz is an app... running on a web server (apache)... so the rules are apache driven, not domoticz
with my previous ISP (fastweb) I was able to connect using v6 addresses (both local and external)

ciao
M

P.S.
it is anyway recommend that you disable v6 stack on the PI... because it could have some issue using apt-get

You're totally wrong here! My internet provider is not by any means involved in my internal local network!

I run my own name servers internally, and my network is configured for both ipv4 and ipv6. The problem seems to be that, since ipv6-connection is the preferred way in decent operating systems i.e the browser will use ipv6-address from DNS name, and Domoticz does not recognize the local ipv6-network I have defined in the settings. That's why it assumes it is not the local network.

And rpi works perfectly with apt-get and ipv6 networks. As far as I know. Has been running ipv6 on my local network the last 6 or more years. And several RPi's during that time running with both ipv4 and ipv6.

emme wrote: ↑Monday 09 October 2017 9:54 the different behaivour depends on your internet provider:
if you are not propted with user and pass, I assume you have all your local network in the Domoticz server IP list (or at least the PC source IP address)...

if you call you server using the ddns you access it through the wap IP address... in some cases the router itself will tranaslate the wan IP to local IP, in some other (vodafone Italy) the gateway wil drop your request (you will be never able to get into your LAN using the WanIP from your lan...)

Domoticz is an app... running on a web server (apache)... so the rules are apache driven, not domoticz
with my previous ISP (fastweb) I was able to connect using v6 addresses (both local and external)

ciao
M

P.S.
it is anyway recommend that you disable v6 stack on the PI... because it could have some issue using apt-get

I'm sorry, but I am struggeling with the same issue as the original poster of this topic. I do run a fully configured dual-stack environment (IPv4 and IPv6) without any issues at all, regarding any program I use.

As your setup is described, you do not use a "split-dns" setup, ergo, you use the DNS settings from an outside DNS server, to resolve to addresses on the inside. A properly configured network has a split-dns setup. All hosts that resolve on the inside, get the information from the internal dns servers, and are pointed to the inside IP addresses of the host. (Both IPv4 and IPv6 in my case). Example:

Inside (LAN) host request: Outside (Internet) host request: Inside (LAN) host request on outside hostname: Outside (internet) host request on external domain name: This, however, doesn't solve the issue that is described. The code within Domoticz doesn't recognize IPv6 address-space, as being LOCAL networks. What you try to formulate is a way to force the browser to connect to the IPv4 address, not understanding, that current operating systems will prioritize IPv6 over IPv4.

Because the browser within the LAN will get my first example of resolving, and therefor, because I use a recent OS, my browser will start to communicate with the host on the IPv6 address. Upto now, no ISP is involved. And why do you want to connect to your WAN IP to get to an internal system? That is odd? Direct traffic is preferred at any time.

Even @Thomasdc claims, that there will be more traffic on your network with IPv6. He only forgets that IPv6 is much more sophisticated and smarter than IPv4, so you actually WILL benefit from IPv6.

Example: I have a Pi located in NYC (USA) and in NL. I do have on both sides serious firewall equipment. There is an IPv4 tunnel in between, and both sides have IPv6 (Public Addresses). The latency over the IPv4 tunnel from Pi to Pi is around 170 ms. From Firewall to Firewall on IPv4 it is around 145 ms. Then, using IPv6, Pi to Pi, I am around 90 ms.

Ergo, using IPv6 is a bit more "talking" on the net, resulting in faster connections.

The issue that @gflygt and I have, (and probably more people) is the fact, that Domoticz runs fine on IPv6. There is only a small part missing, and that is the Local Networks setting, not recognizing IPv6 address space. (Or I am doing something wrong, which is also a huge probability)

Slowly but surely there comes a need for IPv6 support, due to the fact that it will be used more often. And I am patient about it, due to the fact that all developers put in a huge amount of effort and time to make Domoticz better every day!

So, please do not try to solve an issue with ductape, bandaids and chewing-gum, because that is not solving the issue where it should be solved. It should be solved in the code, and that might take a while.