Hi, > Starting xrdp (at boot, or manually via the initscript) ends up > with this in syslog: > > Nov 11 14:11:13 tglase-nb xrdp-sesman[2540]: (2540)(140396101784768)[DEBUG] libscp initialized > Nov 11 14:11:13 tglase-nb xrdp-sesman[2543]: (2543)(140396101784768)[INFO ] starting xrdp-sesman with pid 2543 > Nov 11 14:11:13 tglase-nb xrdp-sesman[2543]: (2543)(140396101784768)[ERROR] bind error on port '3350': 22 (Invalid argument) > Nov 11 14:11:13 tglase-nb xrdp-sesman[2543]: (2543)(140396101784768)[DEBUG] Closed socket 7 (AF_INET6 :::0) > Nov 11 14:11:15 tglase-nb xrdp[2546]: (2546)(140371933928256)[INFO ] starting xrdp with pid 2546 > Nov 11 14:11:15 tglase-nb xrdp[2546]: (2546)(140371933928256)[ERROR] xrdp_listen_main_loop: listen error, possible port already in use > Nov 11 14:11:15 tglase-nb xrdp[2546]: (2546)(140371933928256)[DEBUG] Closed socket 11 (AF_INET6 :::0) > > The network configuration at that point is: > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 > link/ether 00:1d:72:84:b1:b1 brd ff:ff:ff:ff:ff:ff > 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 > link/ether 00:1f:3b:0d:cb:b1 brd ff:ff:ff:ff:ff:ff > 4: tap4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 > link/ether 6e:51:4f:7e:09:f2 brd ff:ff:ff:ff:ff:ff > inet 192.168.10.205 peer 192.168.10.206/32 brd 192.168.10.205 scope global tap4 > valid_lft forever preferred_lft forever > > […] > > /etc/hosts contains my hostname (also FQDN) on 127.0.0.1, so this > is a bug as this *can*, and should, work with just the loopback > interface. I think this is not related to only the loopback interface being up, as eth4, in your config above, also has an address (the interface being down is irrelevant to binding a socket to an address it). I rather think that this is the same issue as #839266 [0], because no interface having a link-local IPv6 address is also true in your config posted above. Can you try setting an alibi link-local address on eth4 and see whether the problem goes away? That would prove it is the same bug as #839266. If you can't, I propose we try again when #839266 is fixed (it is fixed upstream, so the next upload will fix it). Cheers, Nik [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839266 -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Contributor LPIC-3 Linux Enterprise Professional (Security)
Attachment:
signature.asc
Description: PGP signature