Package: network-manager-iodine Version: 1.2.0-1 Severity: normal Tags: upstream
Hi Guido, as discussed at FOSDEM the plugin is able to connect, but afterwards the connection is unusable and gets killed after a minute: ** Message: iodine started with pid 26383 ** Message: Enter password: ** Message: Interface: dns0 ** Message: Opened IPv4 UDP socket ** Message: External gw: 192.168.101.1 ** Message: Autodetecting DNS query type (use -T to override). ** Message: Using DNS type NULL queries ** Message: Version ok, both using protocol v 0x00000502. You are user #0 ** Message: Address: 172.16.0.2 ** Message: MTU: 1130 ** Message: PTP address: 172.16.0.1 ** Message: Testing raw UDP data to the server (skip with -r) ** Message: Server is at XXX.XXX.XXX.XXX, trying raw login: OK ** Message: Overwrite ext. gw. address: XXX.XXX.XXX.XXX ** Message: Parsing done, sending IP4 config ** Message: iodine: No downstream data received in 60 seconds, shutting down. Routes are set like this automatically: Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.16.0.1 0.0.0.0 UG 50 0 0 dns0 0.0.0.0 192.168.101.1 0.0.0.0 UG 600 0 0 wlp4s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlp4s0 172.16.0.0 0.0.0.0 255.255.255.224 U 50 0 0 dns0 192.168.101.0 0.0.0.0 255.255.255.0 U 600 0 0 wlp4s0 192.168.101.1 0.0.0.0 255.255.255.255 UH 600 0 0 wlp4s0 If the access to YYY.YYY.YYY.YYY is blocked, the raw mode is not available and the connections works as expected: ** Message: iodine started with pid 27789 ** Message: Enter password: ** Message: Interface: dns0 ** Message: Opened IPv4 UDP socket ** Message: External gw: 192.168.101.1 ** Message: Autodetecting DNS query type (use -T to override). ** Message: Using DNS type NULL queries ** Message: Version ok, both using protocol v 0x00000502. You are user #0 ** Message: Address: 172.16.0.2 ** Message: MTU: 1130 ** Message: PTP address: 172.16.0.1 ** Message: Testing raw UDP data to the server (skip with -r) ** Message: Server is at XXX.XXX.XXX.XXX, trying raw login: ....failed ** Message: Using EDNS0 extension ** Message: Switching upstream to codec Base128 ** Message: Server switched upstream to codec Base128 ** Message: No alternative downstream codec available, using default (Raw) ** Message: Switching to lazy mode for low-latency ** Message: Server switched to lazy mode ** Message: Autoprobing max downstream fragment size... (skip with -m fragsize) ** Message: 768 ok.. 1152 ok.. ...1344 not ok.. ...1248 not ok.. ...1200 not ok.. 1176 ok.. 1188 ok.. will use 1188-2=1186 ** Message: Setting downstream fragment size to max 1186... ** Message: Parsing done, sending IP4 config ** Message: Terminated iodine daemon with PID 27789. It is also possible to create a usable raw connection by setting an additional route for XXX.XXX.XXX.XXX using the local gateway, in the aboe example 192.168.101.1. So it appears that in case the iodined server is reachable directly, raw mode is detected to be working and afterwards the routing is changed in a such a way that the server is not reachable anymore at all. Cheers Matthias -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager-iodine depends on: ii adduser 3.115 ii iodine 0.7.0-7 ii libc6 2.24-9 ii libglib2.0-0 2.50.2-2 ii libnm0 1.6.0-1 network-manager-iodine recommends no packages. network-manager-iodine suggests no packages.
