deluge sends interface IP, not public IP
Posted: Sat Jun 05, 2021 2:58 pm
Hello all
I don't know if this is deluge or the tracker - the torrent leak tests show
that deluge sends them the public IP address.
Also deluge-gtk on the status line is showing me the correct public IP on the status bar
BUT ... BUT the deluged log file is saying that some trackers are getting the
VPN service's internal IP address (below I show what whois says about it)
- I replaced the IP address with the whois response
from the deluged log file:
When I put the public IP address in the deluge config option "Outgoing Interface"
it doesn't make a difference
I don't know if this is deluge or the tracker - the torrent leak tests show
that deluge sends them the public IP address.
Also deluge-gtk on the status line is showing me the correct public IP on the status bar
BUT ... BUT the deluged log file is saying that some trackers are getting the
VPN service's internal IP address (below I show what whois says about it)
- I replaced the IP address with the whois response
Code: Select all
[SHARED-ADDRESS-SPACE-RFCTBD-IANA-RESERVED:port]
Code: Select all
09:24:23 [DEBUG ][deluge.core.alertmanager :130 ] tracker_error_alert: torrent name XXXX
(http://XXXXX.xxx.org/xxxxx/announce)
[SHARED-ADDRESS-SPACE-RFCTBD-IANA-RESERVED:port]
tracker sent a failure message "non routable IP found" (1)
it doesn't make a difference