From owner-freebsd-stable Fri Dec 15 18:23:28 2000 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 15 18:23:26 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www3.infolink.com.br (www3.infolink.com.br [200.255.108.4]) by hub.freebsd.org (Postfix) with ESMTP id CD6E237B400 for ; Fri, 15 Dec 2000 18:23:25 -0800 (PST) Received: from diala11 (unverified [200.255.108.11]) by www3.infolink.com.br (Vircom SMTPRS 4.2.181) with SMTP id for ; Sat, 16 Dec 2000 00:23:18 -0300 Message-ID: <002601c06707$280f0980$0b6cffc8@infolink.com.br> From: "Antonio Carlos Pina" To: Subject: Bridge + Firewall + Dummynet (all Working) + ... routing ???? Date: Sat, 16 Dec 2000 00:23:19 -0200 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.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I would like to know if anybody here did tried that before: I have a Bridge+Firewall+Dummynet box working wonderfully (4.2-Stable) between one of our networks and a CISCO router (a default gateway) to Internet. We have chosen the Bridge model because using the transparent bridge we didn't even change all "default gateway" in all boxes inside our Network. Is there any way (perhaps using Divert and Natd ?) to implement some basic static routes in this bridge ? The reason is I nowadays we have many IP classes and I feel it is a shame that one packet must go through the bridge to reach the Router, than come back through the bridge again to be delivered to an Access Server, for instance. The way I know to achieve that is changing the bridge's IP address and disabling the bridge code (assigning another IP address to the Router), but before I go this way, I'm trying to keep just one hop to get out of my Network ;-) Best Regards, Antonio Carlos Pina To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message