From owner-freebsd-net@FreeBSD.ORG Wed Jun 22 12:53:46 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4271B16A41C for ; Wed, 22 Jun 2005 12:53:46 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1A6143D1D for ; Wed, 22 Jun 2005 12:53:45 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 53615 invoked from network); 22 Jun 2005 12:44:19 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 22 Jun 2005 12:44:19 -0000 Message-ID: <42B95F5A.DFF7F3C5@freebsd.org> Date: Wed, 22 Jun 2005 14:53:46 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo References: <42B7B352.8040806@suutari.iki.fi> <20050621170649.B82876@xorpc.icir.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Policy routing idea (Was: ipfw: Would it be possible tocontinue processing rest of rules after match ?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2005 12:53:46 -0000 Luigi Rizzo wrote: > > On Tue, Jun 21, 2005 at 09:27:30AM +0300, Ari Suutari wrote: > > Hi, > > > > I sent this to ipfw mailing list some time ago, but > > got no response. I would like to adjust ipfw behaviour > > with fwd rules to make policy routing easier (ie. make > > it separete from filtering rules). I would just like > > some input if this makes any sense (or is possible at > > all with current design). > > i suggest to implement a new action 'setnexthop' which stores the > next hop as an MTAG with the packet (so it is preserved if the > packet gets passed to dummynet). Please don't store routing table pointers. All the locking due to pointers to route entries in random places makes SMP a pain a slows down routing table lookups. > But perhaps, rather than a specific next hop, maybe you want to > pass a reference to a different routing table instead ? We don't have any at the moment. -- Andre > cheers > luigi > > > >Currently the ipfw fwd rules work so that the packet > > >is accepted when fwd rule matches. > > > > > >Would it be possible just tag the packet with > > >information about next_hop and just continue processing the > > >rules ? This would make complex rulesets with policy-based > > >routing much simpler, since one could just have relevat > > >fwd statments at beginning of rule sets and then > > >filter the packets in usual way. > > > > Ari S. > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"