All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: --to-destination of DNAT issue -- or my misinterpretation?
Date: Thu, 14 Sep 2006 15:59:00 +0200	[thread overview]
Message-ID: <45096024.1050204@plouf.fr.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0609141525570.25864@yvahk01.tjqt.qr>

Jan Engelhardt a écrit :
>>Hello,
>>
>>It seems I can't specify several --to-destination (like the man page
>>tells), and iptables doesn't spit any errors.
>>
>>Am I doing something wrong?
> 
> Only one --to-destination is supported.

This restriction was first introduced in kernel 2.6.11. Previous 2.6 
kernels, as well as 2.4 kernels, should support multiple ranges.

ChangeLog-2.6.11 :
" [PATCH] Remove NAT to multiple ranges
   The NAT code has the concept of multiple ranges: you can say "map this
   connection onto IP 192.168.1.2 - 192.168.1.4, 192.168.1.7 ports
   1024-65535, and 192.168.1.10".  I implemented this because we could.

   But it's not actually *used* by many (any?) people, and you can
   approximate this by a random match (from patch-o-matic) if you really
   want to.  It adds complexity to the code."

changes-iptables-1.3.4.txt :
" Print error message when multiple "--to" DNAT/SNAT args are used
   with kernel >= 2.6.10"
                      ^^
There seems to be a little mistake here, should be 2.6.11 according to 
Linux changelog.


  reply	other threads:[~2006-09-14 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c6c65ec80609131835l7d586b6r29e8226a93db7bab@mail.gmail.com>
     [not found] ` <c6c65ec80609131838x35b95470m42a61c6d6f27ec9f@mail.gmail.com>
2006-09-14 12:46   ` --to-destination of DNAT issue -- or my misinterpretation? João Fernandes Simplício
2006-09-14 13:26     ` Jan Engelhardt
2006-09-14 13:59       ` Pascal Hambourg [this message]
2006-09-14 14:01         ` Jan Engelhardt
2006-09-14 14:22           ` Pascal Hambourg
2006-09-14 14:36             ` Jan Engelhardt

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=45096024.1050204@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.