toasta

Hi @arvidn, > > hmm.. I think it should still respect the fib. > What's "the fib"? Forwarding Information Base. It's basically the condensed and/or optimized form of the routingtable...

k.. some small infos, after battling with deluge vs. python3.7/logging on a python3.8 machine.... ``` 22:10:33 [DEBUG ][deluge.core.alertmanager :130 ] add_torrent_alert: added torrent: someFile 22:10:33 [DEBUG ][deluge.core.alertmanager :130 ] torrent_added_alert:...

does this have anything to do with it? http_tracker_connection.cpp:272 ``` // endpoints is an in-out parameter void http_tracker_connection::on_filter(http_connection& c , std::vector& endpoints) { // filter all endpoints we cannot reach...

> Are you saying there's another issue? Does it affect TCP? yup.. just look at the tcpdump: ``` bf@$ sudo tcpdump -ni tun0 "port 67535" tcpdump: verbose output suppressed, use...

> Tracker announces are different. Then we attempt to announce from every active listen interface. i.e. every IP that we _accept_ incoming connection on, we attempt to announce to the...

> 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...

rfc > what do you mean by "RFC IPs". Do you mean reserved IP ranges? the rfc1918 ips, 10/8, 172.16/12, 192.168/16

but i might have already figured out my problem: docs say >If an IP address is the unspecified address (i.e. 0.0.0.0 or ::), libtorrent will enumerate > Listen IP addresses...

I was wondering if this could have something to do with the "information leak" i mentioned above and described in https://github.com/arvidn/libtorrent/issues/4803. openvpn does this "two /1" routes thing to be...

> No, I don't think so. Any route that has a gateway, finally managed to get it to compile (just my own stupidity or unfamiliraty with b2) tried to download...