From owner-freebsd-questions Mon Dec 9 9:25:26 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1BFD37B401 for ; Mon, 9 Dec 2002 09:25:24 -0800 (PST) Received: from mailout5-0.nyroc.rr.com (mailout5-1.nyroc.rr.com [24.92.226.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75F3243EA9 for ; Mon, 9 Dec 2002 09:25:18 -0800 (PST) (envelope-from cjm2@earthling.net) Received: from mail.27in.tv (roc-24-59-179-24.rochester.rr.com [24.59.179.24]) by mailout5-0.nyroc.rr.com (8.11.6/RoadRunner 1.20) with SMTP id gB9HPFF18116 for ; Mon, 9 Dec 2002 12:25:15 -0500 (EST) Received: (qmail 29711 invoked from network); 9 Dec 2002 17:27:31 -0000 Received: from localhost.lan.27in.tv (HELO 27in.tv) (127.0.0.1) by localhost.lan.27in.tv with SMTP; 9 Dec 2002 17:27:31 -0000 Received: from 216.153.202.219 (SquirrelMail authenticated user cjm2) by www.27in.tv with HTTP; Mon, 9 Dec 2002 12:27:31 -0500 (EST) Message-ID: <1863.216.153.202.219.1039454851.squirrel@www.27in.tv> Date: Mon, 9 Dec 2002 12:27:31 -0500 (EST) Subject: Re: port redirect with ipfw NOT NAT (not NAT) From: "C J Michaels" To: In-Reply-To: <44znrga9lj.fsf@be-well.ilk.org> References: <20021208010714.J77087-100000@mail.econolodgetulsa.com> <44znrga9lj.fsf@be-well.ilk.org> X-Priority: 3 Importance: Normal Cc: X-Mailer: SquirrelMail (version 1.2.10) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Some time in the recent past Lowell Gilbert scribbled: > Josh Brooks writes: > >> > Have you tried something like: >> > >> > add 01000 fwd 10.10.10.10,5050 tcp from any to 10.10.10.10 50 >> >> >> When I do this, I get: >> >> ipfw: getsockopt(IP_FW_ADD): Invalid argumentipfw: >> getsockopt(IP_FW_ADD): Invalid argument >> >> >> Any ideas ? Is there any reason why port forwarding with ipfw is >> special and annoying ? Or is there really something qualitatively >> different about this action that warrants this behavior ? I don't see anything wrong with your syntax on that command and I use a similar command to foward to my transparent proxy. The only thing *I* can think of is that you didn't compile your kernel with: options IPFIREWALL_FORWARD -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message