From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pascal Hambourg Subject: Re: port forwarding through localhost Date: Fri, 26 Jan 2007 23:50:23 +0100 Message-ID: <45BA85AF.5010907@plouf.fr.eu.org> References: <000001c74194$d484d9b0$0d01a8c0@Mobi> <45BA7E51.40505@plouf.fr.eu.org> <000301c74199$7db871f0$0d01a8c0@Mobi> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <000301c74199$7db871f0$0d01a8c0@Mobi> 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 Andy B. a =E9crit : > Sorry about the "3333", it was a typo. Of course I meant 3306. >=20 > My rules are working when we are talking about the external interfaces > (eth0), and the SQL Server is responding when talking directly to 10.0.= 0.100 You didn't say what is the kernel version. If it is >=3D 2.6.11, you're s= tuck. As I suggested to someone else having the same problem as you, instead=20 of using a DNAT rule you may use a TCP "proxy" such as stone=20 (, supports UDP too) or 6tunnel=20 (, originally designed to relay connections=20 between IPv6 and IPv4 hosts but works between IPv4 hosts too) which=20 listens on the local port 3306 and relays the local connexions to the=20 remote SQL server.