Change Details

An interface that starts with "tun" is created by a VPN running on a device. It must be ignored to avoid getting an invalid IP address and allow connection to devices with VPNs. This is related to (and in my case corrects) this bug: https://bugs.kde.org/show_bug.cgi?id=344432 (All unit tests passed but I still don't know how to show it here.)

When trying to remotely browse the device filesystem, if the device transmits all IP addresses (see https://phabricator.kde.org/D6757), in that case the desktop application needs to test and determine which one to use. We try to open a TCP connection on the addresses, one by one, using the transmitted port. When one succeeds, we break out of the loop and use this address to start sshfs. This revision can probably be refined, but I wanted to present the idea.

An interface that starts with "tun" is created by a VPN running on a device.When trying to remotely browse the device filesystem, if the device transmits all IP addresses (see https://phabricator.kde.org/D6757), It must be ignored to avoid getting an invalid IP addressin that case the desktop application needs to test and allow connection to devices with VPNsdetermine which one to use. This is related to (and in my case corrects) this bug: https://bugs.kde.org/show_bug.cgi?id=344432We try to open a TCP connection on the addresses, one by one, using the transmitted port. When one succeeds, we break out of the loop and use this address to start sshfs. (All unit tests passed but I still don't know howThis revision can probably be refined, but I wanted to show it here.)present the idea.