From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BitTorrent and iptables (was: Can not read UDF CD)
Date: Mon, 16 Aug 2004 15:50:33 -0400 [thread overview]
Message-ID: <cfr2qh$8lf$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <200408131314.02352.jk-lkml@sci.fi>
Jan Knutar wrote:
> On Thursday 12 August 2004 23:33, Bill Davidsen wrote:
>
>
>>I used torrent to pull something the other day, and while I could pull,
>>no one could connect to get data from me. I have my iptables set to
>>ESTABLISHED,RELATED so iptables may not know about torrent.
>
>
> You probably need to explicitly ACCEPT incoming to the port that Bittorrent
> uses. A tracker module to sniff traffic to known outbound tracker ports, to
> detect which port Bittorrent is using, and allow that inbound, seems a little
> bit excessive to me, not to mention that people set up trackers on the most
> varying range of seemingly random ports :-)
>
> Either way, common sane principles of TCP/IP apply with Bittorrent too,
> if both parties are firewalled, you wont transfer any data between eachother.
> If one party (out of two) is unfirewalled, data can be transfered both ways
> between them, the firewalled party will established connection to the unfirewalled
> to get communication going.
The desired behaviour is that incoming BT connections would be accepted
while an outgoing BT connection is in place. You can't open the port at
any other time, there's no (legitimate) process listening and the
firewall wouldn't know where to forward the socket in any case.
This belongs on another list.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2004-08-16 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:27 Can not read UDF CD David Balazic
2004-08-12 20:33 ` BitTorrent and iptables (was: Can not read UDF CD) Bill Davidsen
2004-08-13 10:14 ` Jan Knutar
2004-08-16 19:50 ` Bill Davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='cfr2qh$8lf$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox