Skip to content
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

Closed
itamarjp opened this issue Jul 1, 2012 · 10 comments
Closed

ipv6 support for xrdp. #30

itamarjp opened this issue Jul 1, 2012 · 10 comments
Labels

Comments

@itamarjp
Copy link
Member

itamarjp commented Jul 1, 2012

Hello guy's

We need to add ipv6 support into xrdp

@metalefty
Copy link
Member

👍 I also happy if xrdp had ipv6 support. Anything new?

@metalefty
Copy link
Member

@jsorg71
You disabled IPv6 at cd0a872, but why? Do you have a plan to re-enable IPv6?

@metalefty
Copy link
Member

In other words, what should we do to re-enabling IPv6? What tasks remained?

@jsorg71
Copy link
Contributor

jsorg71 commented Mar 9, 2015

I broke some systems. I didn't have enough experience using ipv6. For example, BSD is a bit different.
I think until it's tested more, we should add --enable-ipv6

@metalefty
Copy link
Member

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.

@jsorg71
Copy link
Contributor

jsorg71 commented Mar 10, 2015

I think it was something like mint 64 bit that would not accept connection.

For the BSD issue,

This is from
Thomas
on mailing list 04/04/2013

I second thing I observed:

Linux uses one socket for all - v4 and v6.

If I remember correctly BSD does not so behave.
In the case the xrdp needs compatibility with bsd, it could be necessary
to implement two sockets.

e.g. sshd does so:

tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2574/sshd
tcp 0 0 :::22 :::* LISTEN 2574/sshd

xrdp

tcp 0 0 :::3389 :::* LISTEN 5311/xrdp

Regards,

Thomas

@metalefty
Copy link
Member

After further investigation, BSD (at least FreeBSD) can handle both IPv4 and IPv6 in one socket.
SSH, PostgreSQL demon have independent socket for v4 and v6 . However, MySQL daemon seems to listen v4 and v6 in one socket.

Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address          Foreign Address        (state)
tcp4       0      0 *.ssh                  *.*                    LISTEN
tcp6       0      0 *.ssh                  *.*                    LISTEN
tcp46      0      0 *.mysql                *.*                    LISTEN
tcp4       0      0 *.rdp                  *.*                    LISTEN
tcp4       0      0 localhost.postgresql   *.*                    LISTEN
tcp6       0      0 localhost.postgresql   *.*                    LISTEN

@metalefty
Copy link
Member

The problem looks quite simple (at least on FreeBSD).

IPv6 auto detection appeared in 54463af is not suitable for FreeBSD.

AC_CHECK_MEMBER([struct in6_addr.s6_addr],
                [],
                [AC_DEFINE(NO_ARPA_INET_H_IP6, 1, [for IPv6])],
                [#include <arpa/inet.h>])

This always fails. NO_ARPA_INET_H_IP6 is always 1 in FreeBSD and xrdp will always by built IPv6 support disabled.

@metalefty
Copy link
Member

OpenBSD behaves a little bit different. Jay and Thomas talked on the mailing list.
We need to implement two sockets for OpenBSD but one socket is enough for others.

@metalefty
Copy link
Member

IPv6 implementation in xrdp has been improved a lot (#714 etc). Let's close this once.
I don't think we don't need to listen IPv4 and IPv6 in separate socket right now.

Nexarian pushed a commit to Nexarian/xrdp that referenced this issue Sep 26, 2021
Miscellaneous fixes for the next release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants