From owner-freebsd-ipfw@FreeBSD.ORG Wed Nov 2 21:46:33 2005 Return-Path: X-Original-To: freebsd-ipfw@freebsd.org Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0570916A41F for ; Wed, 2 Nov 2005 21:46:33 +0000 (GMT) (envelope-from routester@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF1EF43D45 for ; Wed, 2 Nov 2005 21:46:31 +0000 (GMT) (envelope-from routester@gmail.com) Received: by wproxy.gmail.com with SMTP id i27so79564wra for ; Wed, 02 Nov 2005 13:46:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=gi1jF64TQ5uZec0AN97PyXbfKPrOcUtl8Wm4X+3pRtC3CWO4+BmqiEXNpF+6uF4rfCMB8dmcVonqVi7DbwAkZtnHXZEIRwX5dsbWhum//3dtIhnmg+dNVCuzKWJyMgyKb0ryEHZCYWsbsv9idcms9e7cWkgPVjmCqdHv0OUgUQA= Received: by 10.65.230.6 with SMTP id h6mr10741qbr; Wed, 02 Nov 2005 13:46:30 -0800 (PST) Received: by 10.64.193.18 with HTTP; Wed, 2 Nov 2005 13:46:30 -0800 (PST) Message-ID: Date: Wed, 2 Nov 2005 16:46:30 -0500 From: Router Guy To: freebsd-ipfw@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Possible repost, new subscriber - IPFW+FWD X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 21:46:33 -0000 I've searched the archive, and read the man page...possible that I've misse= d something. ipfw rules... 00700 0 0 allow ip from 172.16.200.2 to 172.16.200.2 00800 9 756 fwd 172.16.200.1 ip from 172.16.200.2to any 00900 0 0 allow ip from any to 172.16.200.2 via vlan= 3 vlan3: flags=3D8843 mtu 1500 inet 172.16.200.2 netmask 0xffffff00 broadcast 172.16.200.255 ether 00:b0:d0:49:00:bd media: Ethernet autoselect (100baseTX) status: active vlan: 3 parent interface: fxp0 Kern options options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT options IPFIREWALL_FORWARD 5.4-RELEASE-p8 As you can see from the ipfw output, the fwd rules match - but the packets are still forwarded out the primary interface following the default route (verified via tcpdump). The fwd is reachable from the host, and is a router that knows what to do with the packets....