From owner-freebsd-net Fri May 24 6: 8:57 2002 Delivered-To: freebsd-net@freebsd.org Received: from optima-hyper.com (s2.optima-hyper.com [12.111.39.156]) by hub.freebsd.org (Postfix) with ESMTP id 0C6B037B403 for ; Fri, 24 May 2002 06:08:39 -0700 (PDT) Received: from HQWKSTYV (blackhole.optima-hyper.com [12.111.39.146]) by optima-hyper.com (8.12.3/8.12.2) with SMTP id g4OD8a4G064772; Fri, 24 May 2002 09:08:36 -0400 (EDT) Message-ID: <007501c20324$40ca4920$6c00a8c0@OPTIMA.HQ> From: "Yuri Victorovich" To: "Rocco Lucia" , References: <57047D2A-6ECD-11D6-A953-000393B296CE@iscanet.com> Subject: Re: ng_fwdswitch netgraph node Date: Fri, 24 May 2002 09:09:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org And why make it one-directional only? It shouldn't improve performance. So it's rather an "IP router" than "fwdswitch". many2many IP routing node would be useful in many situations. Yuri > The fwdswitch node, could be imagined as a 'many2many' node but > monodirectional only: packets flow from 'in' hooks to 'out' hooks > only. The decision about which 'out' hook to choose to forward a > packet is taken going through a forwarding table that associates > an IPaddress/netmask to an output hook index. Packets that are not > matched or frames that are not IP packets will be forwarded to the > 'default' hook. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message