From owner-freebsd-net@FreeBSD.ORG Tue Feb 12 18:10:26 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6F3C62AC; Tue, 12 Feb 2013 18:10:26 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 55464842; Tue, 12 Feb 2013 18:10:26 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,650,1355126400"; d="scan'208";a="20002457" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 12 Feb 2013 10:10:26 -0800 Received: from vmwexceht05-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r1CIAPtu007794; Tue, 12 Feb 2013 10:10:26 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Tue, 12 Feb 2013 10:10:25 -0800 From: "Eggert, Lars" To: Ivan Voras Subject: Re: Problems with two interfaces on the same subnet? Thread-Topic: Problems with two interfaces on the same subnet? Thread-Index: AQHOCUb6Tp99D1R3iECoMLZWzmGEXph3AyuAgAADNoCAAAWpAA== Date: Tue, 12 Feb 2013 18:10:25 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <990AC28AA5A9AE4FA437F9D6546388BE@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 18:10:26 -0000 Hi, On Feb 12, 2013, at 9:50, Ivan Voras wrote: >> You can make this work with ipfw rules (and I guess also setfib, althoug= h I have not tried that.) >=20 > The concept of FIBs looks clean and applicable but setfib works on newly > started process, and I would need to do something like apply it to > packets coming from an interface. Assuming your default route is via igb2, you can do something like this: ipfw add fwd ip4 from to = not out (From memory, no guarantees.) Lars=