From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pascal Hambourg Subject: Re: --to-destination of DNAT issue -- or my misinterpretation? Date: Thu, 14 Sep 2006 15:59:00 +0200 Message-ID: <45096024.1050204@plouf.fr.eu.org> References: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: netfilter@lists.netfilter.org Jan Engelhardt a =E9crit : >>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? >=20 > Only one --to-destination is supported. This restriction was first introduced in kernel 2.6.11. Previous 2.6=20 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 >=3D 2.6.10" ^^ There seems to be a little mistake here, should be 2.6.11 according to=20 Linux changelog.