Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Tom <gunsuper@atm.cyberec.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Problem for Bittorrent Application behind Linux Firewall
Date: Fri, 3 Oct 2003 13:03:52 +0200	[thread overview]
Message-ID: <20031003110352.GI5758@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <049201c381b3$672939f0$5a01a8c0@wireless.cheung.com>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

On Tue, Sep 23, 2003 at 05:16:41PM +0800, Tom wrote:
> The following is my iptables rules.According to my understanding, BT
> use the ports 6881 to 6889,Then I forward these ports to my machines
> in LAN.

I have no idea about bittorrent and it's protocol, sorry.
> 
> #! /bin/sh
> iptables -t nat -A PREROUTING -i ppp0 -p tcp --dport 6881:6889 -j DNAT --to 192.168.1.90:6881-6889
> iptables -A FORWARD -p tcp -s 192.168.1.90 --dport 6881:6889 -j ACCEPT
> 

Those rules say 'nat any port between 6881:6889 to any port between
6881:6889'.  i.e. port 6881 can be NAT'ed to 6884, happening in a
non-deterministic manner.

try 9 seperate rules for every port if you want to have that guarantee.
 
> Tom Cheung
> 23 Sept 2003
-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-10-03 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23  9:16 Problem for Bittorrent Application behind Linux Firewall Tom
2003-09-23  9:46 ` Eric Leblond
2003-10-03 11:03 ` Harald Welte [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=20031003110352.GI5758@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=gunsuper@atm.cyberec.com \
    --cc=netfilter@lists.netfilter.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