Bug#475643:

Did/will the patch from message #24 of this bug be applied? It seems to have right effect here. Although, it would be nice to use the --bind for tracker connections too, since don't those connections tell remote peers where to connect to to get to one's own peer? signature.asc Description: This

Bug#475643: bittornado: patch to support --bind on outgoing connections

Package: bittornado Version: 0.3.18-8 Followup-For: Bug #475643 An update to the previous patch. This now works for btlaunchmany too. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (750, 'stable'), (700, 'testing'), (600, 'unstabl

Bug#475643: bittornado: patch to support --bind on outgoing connections

Package: bittornado Version: 0.3.18-8 Followup-For: Bug #475643 Here's a patch to add support for binding to the first address listed in --bind. It only affects data connections, but afaic that's more important than tracker connections (tracker connections can always be 'fixed&#

Bug#475643: bittornado: --ip not working

severity 475643 normal retitle 475643 bittornado: --bind not working thanks On 4/11/08, Thomas Creutz <[EMAIL PROTECTED]> wrote: > i started yesterday the btdownloadcurses.bittornado with > > --bind X.X.X.X --ip X.X.X.X --minport 6881 --maxport 6999 TORRENTFILE > > But the tracker report my not

Bug#475643: bittornado: also on the version from testing

Package: bittornado Version: 0.3.18-5 Followup-For: Bug #475643 now i tested the version from testing... same result... :( -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (900, 'stable'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /b

Bug#475643: bittornado: --ip not working

Package: bittornado Version: 0.3.17-1 Severity: important i started yesterday the btdownloadcurses.bittornado with --bind X.X.X.X --ip X.X.X.X --minport 6881 --maxport 6999 TORRENTFILE But the tracker report my not the ip that i used in the bind and ip args Also with "netstat -naptu|grep python