You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
On an IPv6 only network, such as TMobile data or some vlans on my home or test networks or on ISPs that offer IPv6 only with NAT64 if you open the VNC server it doesn't seem to bind to the public Ipv6
On TMobile data it uses the clat and binds to a private ipv4 for example
Describe the solution you'd like
On Linux it should be possible to bind to [::] which will accept both Ipv6 and ipv4 connections. I'm not sure if Android kernels work that way.
When doing this the server should report all the addresses that it can be reached on in the UI.
Your environment (please complete the following information):
droidVNC-NG version: 1.3.5
Android version: 11
The text was updated successfully, but these errors were encountered:
If you'd like to put out an incentive for implementing this feature, you can do so at https://issuehunt.io/r/bk138/droidVNC-NG
Is your feature request related to a problem? Please describe.
On an IPv6 only network, such as TMobile data or some vlans on my home or test networks or on ISPs that offer IPv6 only with NAT64 if you open the VNC server it doesn't seem to bind to the public Ipv6
On TMobile data it uses the clat and binds to a private ipv4 for example
Describe the solution you'd like
On Linux it should be possible to bind to [::] which will accept both Ipv6 and ipv4 connections. I'm not sure if Android kernels work that way.
When doing this the server should report all the addresses that it can be reached on in the UI.
Your environment (please complete the following information):
The text was updated successfully, but these errors were encountered: