Arvid Norberg

> with what should i test, current master? It seems this issue affects 1.2.x, so `RC_1_2` is the branch this should be fixed in. > the data in the tcpdump...

also, trackers and peer connections are different. for trackers libtorrent attempts to announce all IPs that can reach the tracker. There is no filtering for special address ranges. But a...

> i think you should narrow this down to "we only announce it to the interface the routing to this tracker points at". The whole point of doing this is...

what do you mean by "RFC IPs". Do you mean reserved IP ranges?

> is this correct so far? No, I don't think so. Any route that has a gateway, is assumed to be able to reach the internet. Any such routes will...

[this](https://github.com/arvidn/libtorrent/blob/RC_1_2/src/enum_net.cpp#L497) also gives access to the interfaces. and [this](https://github.com/arvidn/libtorrent/blob/RC_1_2/src/enum_net.cpp#L823) gives access to the routing table. You seem to have figured out that you can't omit the IP or interface name...

> My error seems to arise from the different ways you can use to add routes. > there's > `ip r add 3.4.5.0/24 dev tun0` > and > `ip r...

@toasta I really appreciate your help in improving this. It sounds so far I should: * make sure down interfaces are not considered * skip over 0 length route messages...

if `recv()` returns 0, it means end-of-file, and it would seem to be an error to get an EOF rather than an `NLMSG_DONE` message, indicating we received all messages

actually, looking at your strace again, it really looks like the problem is that libtorrent uses a fixed size buffer to read the netlink response into, and your routing table...