#1453: If binding to specified network adress fails, daemon defaults back to
0.0.0.0
------------------------------+----------------------------
Reporter: Sian | Owner:
Type: feature-request | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: 1.3.0
Resolution: | Keywords:
------------------------------+----------------------------
Comment (by firewing1):
I've observed this behavior on my roommate's machine. I believe it has to
do with the default interface being 0.0.0.0. When an interface has been
specified in the preferences, the default should be to fallback to
127.0.0.1 instead of 0.0.0.0.
We fixed the issue without modifying deluge source code by altering the
startup of deluged to bind to 127.0.0.1 on boot, and later re-bind to the
intended interface as it becomes available.
Looking at the source code, I see 0.0.0.0 is the default interface in
server.py line 56.
In case it is helpful, qBittorent (also based on libtorrent) experiences
the same issue: https://github.com/qbittorrent/qBittorrent/issues/2741.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/1453#comment:7>
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.
