Closed klmhsb42 closed 2 years ago
Maybe automatically isn't easy. I would like to have the extension (user's decision): IPv4 (private): IPv4 (public): IPv4 (off)
I don't want disable IPv6. I want the ability to switch off IPv4. In the meantime don't know which is the right isse number.
I don't want disable IPv6.
I know, so this would be the right issue. I just thought the solution could be combined with the other issue. I thought disabling Ipv6 extern access could be useful to test own apps (like websites) which you don't want to publish yet. I would integrate this in the extern access button, which switches then from ipv6 to privat ipv4 and local hostname.
In this issue, we need a extra button in the syncloud UI, which switches ipv4 on and off.
IPv4 (private): IPv4 (public): IPv4 (off)
Or between private, public and off.
Do you have an additional reason/case why you would like to have private ipv4 on/available? Accept the user's decision freedom...
Do you have an additional reason/case why you would like to have private ipv4 on/available? Accept the user's decision freedom...
As the syncloud UI should be simple as possible (less buttons). In best case, you even don't have to say that there are two IP versions. So that a user can setup without even knowing what a IP address is (I know it's sad, but there are also smartphone users who don't care about it).
Remove entry of local IPv4 address
Remove from where?
My problem is the delay (example of openvpn above) or fail in case the client tries to connect an invalid IPv4 address. In my case both ipv4 addresses are invalid, the public one cannot be chosen, since you make a reachability test and the private address in a pubic environment is also useless and confuses clients. Also disabling IPv6 might be reasoned. Some user (e.g. Deutsche Telekom with dualstack with a router called speedport) cannot open the IPv6-firewall at the moment.
As the syncloud UI should be simple as possible (less buttons). In best case, you even don't have to say that there are two IP versions. So that a user can setup without even knowing what a IP address is (I know it's sad, but there are also smartphone users who don't care about it).
Then you have to integrate more checks at syncloud infrastructure site. E.g. at the moment there is only an IPv4-Port check. That has to be extended to IPv6. Only if the tests succeeds - A and or AAAA-Records should be published/assigned.
But people have to make port forwardings (ipv4) / firewall configurations(ipv6) anyway...
Remove entry of local IPv4 address
Remove from where?
From A record? Sorry, I'm not the expert on this.
IPv4 (private): IPv4 (public): IPv4 (off)
Or change A record by button. That's how I understand this...
OK, looks like more users want to control which IP version is enabled for external access mostly because only one of them is allowing incoming connections on device port (default 443) (which should be fixed on either router or ISP but does not allow users to start using the device right away)
Our DNS server at syncloud.it validates that the connection to device port can be made before creating DNS A/AAAA records.
I think I could add the following options to External Access:
It will not disable IPs on the device.
The name of the page External Access
is a bit confusing as it does not really enables external but rather helps you to validate if it is possible, but maybe that is ok for now.
It sounds good. If possible add a clear indication if UPnP is used.
Not sure how useful UPnP is as it does not always work or available so it will be dropped for now.
Remove entry of local IPv4 address, when there is dual stack lite and use always IPv6.