Opened 9 years ago
Last modified 9 years ago
#5492 new Bug
UDP tracker requests don't work if transmission starts up before the network interface does
Reported by: | adood | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | None Set |
Component: | Transmission | Version: | 2.82 |
Severity: | Normal | Keywords: | |
Cc: |
Description
On my system, transmission-daemon consistently manages to start up before ethernet is brought up. This leads to me having to restart transmission-daemon before it will work. #5421 is at best a workaround for this.
As http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ puts it nicely, network availability is extremely chaotic. Being able to handle changing network configurations would make Transmission even more rock solid.
Ideally fixing this means #5421 can be backed out without problems.
Change History (2)
comment:1 Changed 9 years ago by adood
comment:2 Changed 9 years ago by adood
- Summary changed from transmission-daemon doesn't work if it starts up before its network interface does to UDP tracker requests don't work if transmission starts up before the network interface does
Note: See
TracTickets for help on using
tickets.
After looking into it some more, this seems to affect only UDP tracker scrapes and announces. Everything else appears to work fine.