Arvid Norberg

> with "outgoing interface" set to tun0 and the defaultroute over tun0, it is still trying to announce over all interfaces. > Some torrents somehow get stuck in "Announce sent",...

> dunno. seems a bit dirty or at least "not pretty". As privacy concerns arose with failing vpns i'd avoid any announcements if they are not "configured" (as in 'use...

> there should be a route to it, but as far as i understood the "do i announce to that tracker over that interface"-logic, it'll only look for the netmask...

> I have no incoming connections, only outgoing. > So "outgoing_interface" is not considered for tracker announcements? Correct. https://libtorrent.org/reference-Settings.html#outgoing_interfaces

> with all routes removed and one defaultroute via the ip of the interface configured in deluge, client-traffic possible but most of the tracker announcements go over the wrong interface...

actually, I have one more question, apart from the issue of peer connections over uTP not honoring the routing table, can the other issues you experience be solved by the...

> hmmk.. i read that but imho it's not clear, that tracker-announcements are completely separate. Yeah, I agree that it's not all that clear. The mutli-homed section of the documentation...

> tried that, i would expect it to not use any other interface for tracker-announcements, too, but this is what it does with both set to tun0 What's the log...

@toasta there are a few steps involved, and I realise some of the things I've said can easily be misinterpreted. I would like to clarify. ### Step 1, to establish...

@mhertz thanks for the report. Announcing both the VPN and the direct connection is a somewhat separate issue, and I think it deserves its own ticket, feel free to create...