Opened 11 years ago
Last modified 9 years ago
#2209 assigned bug
[BlockList] blocklist ignored on startup
Reported by: | beadon | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | Core | Version: | 1.3.5 |
Keywords: | blocklist | Cc: |
Description
It appears that the Blocklist is ignored on startup of the daemon for a short period of time -- the test here is to add a tracker to the blocklist and restart the daemon, you will see a connection established to the (supposedly blocked) tracker and torrent downloads will function for the torrent.
Change History (2)
comment:1 Changed 11 years ago by Cas
- Component changed from other to plugin
- Owner set to johnnyg
- Status changed from new to assigned
- Summary changed from BlockList not always enforced to [BlockList] blocklist ignored on startup
- Version changed from other (please specify) to 1.3.5
comment:2 Changed 9 years ago by Cas
- Component changed from Plugin to Core
- Owner johnnyg deleted
Note: See
TracTickets for help on using
tickets.
The reason is that the plugin is loaded a while after the libtorrent session has started.
I think the solution would be to have something along the lines of an option in core to block all ips on startup, as this can't be solved in the plugin code.