#3114: DNS resolution doesn't use the correct network interface
------------------------+----------------------------
Reporter: oxguy3 | Owner:
Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: libtorrent | Version: 1.3.13
Keywords: |
------------------------+----------------------------
When you set an IP address as the Interface in the Network tab of Deluge's
Preferences, all traffic that Deluge sends out is supposed to go via that
IP address. However, DNS resolution for trackers does not use this
interface, and instead uses the system's default interface.
This bug is critical for me, as I have firewall settings that restrict
Deluge from making connections on any interface besides my VPN connection
(except on port 58846). Deluge entirely fails to resolve all hostnames
unless I add an exception for port 53 in my iptables settings.
----
I did a bit of digging to figure out why this happens. Deluge lets
libtorrent handle hostname resolution, and libtorrent uses Boost.ASIO's
[http://www.boost.org/doc/libs/1_43_0/doc/html/boost_asio/reference/ip__tcp/resolver.html
ip::tcp::resolver] for its DNS resolution (see
[https://github.com/arvidn/libtorrent/blob/master/src/resolver.cpp
libtorrent/src/resolver.cpp]). ip::tcp::resolver is basically a blackbox
-- it doesn't allow you to configure what DNS servers it uses or how it
connects to them, and it just does whatever it wants. I don't know enough
about Deluge/libtorrent to know how this might be resolved...
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3114>
Deluge <http://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
