xnoreq

simple_client binds to 0.0.0.0:6881 just like qbittorrent did with libtorrent before 1.2.4 so it probably doesn't care if the interfaces goes down or the IP address is removed from it....

The vpn uses openvpn with a script that executes on up: ``` ip link set dev "tun0" up mtu "$tun_mtu" # setting up network schedulers # setting up firewall rules...

Anyway, I'm stuck on af12f5d6b8dc47add564d7ce544bbaf26cd1de1e for the time being until these issues are fully resolved.

@arvidn No, I initially pasted the wrong hash. I guess you're reading the mails and corrections through edits are not sent as mails again. The commit is from 11th of...

I think the issue is with qbittorrent(-nox). Not sure what needs to be implemented to get the reconnection working on the side that uses libtorrent.

Update: latest libtorrent and qbittorrent master doesn't even connect to peers anymore.

@arvidn Yes, RC_1_2 branch of libtorrent, qbittorrent master. Going back to af12f5d6b8dc47add564d7ce544bbaf26cd1de1e works also with qbittorrent master.

The only recent relevant commit I can spot is https://github.com/qbittorrent/qBittorrent/commit/bf1c9e34d7a7361fec844a4412a0bdd4b8b12d4c ("Fix outgoing interface is not getting assigned"). They also changed something about resume data, not holding torrent (?) files in...

@swejuggalo Nope, the original issue is not fixed. Still trackers "not working" and DHT nodes sticking to 0 after VPN reconnect.

Check your trackers. I am also retaining limited connectivity to some peers (to which there already was a connection before the reconnection).