-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipv6 support for xrdp. #30
Comments
👍 I also happy if xrdp had ipv6 support. Anything new? |
In other words, what should we do to re-enabling IPv6? What tasks remained? |
I broke some systems. I didn't have enough experience using ipv6. For example, BSD is a bit different. |
I did --enable-ipv6 option. I'll give it a try for BSDs and other systems as much as I can. Please tell me how was it broken if you remember. |
I think it was something like mint 64 bit that would not accept connection. For the BSD issue, This is from I second thing I observed: Linux uses one socket for all - v4 and v6. If I remember correctly BSD does not so behave. e.g. sshd does so: tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2574/sshd xrdp tcp 0 0 :::3389 :::* LISTEN 5311/xrdp Regards, Thomas |
After further investigation, BSD (at least FreeBSD) can handle both IPv4 and IPv6 in one socket.
|
The problem looks quite simple (at least on FreeBSD). IPv6 auto detection appeared in 54463af is not suitable for FreeBSD.
This always fails. NO_ARPA_INET_H_IP6 is always 1 in FreeBSD and xrdp will always by built IPv6 support disabled. |
OpenBSD behaves a little bit different. Jay and Thomas talked on the mailing list. |
IPv6 implementation in xrdp has been improved a lot (#714 etc). Let's close this once. |
Miscellaneous fixes for the next release
Hello guy's
We need to add ipv6 support into xrdp
The text was updated successfully, but these errors were encountered: