From owner-freebsd-stable Mon Feb 12 13: 3:13 2001 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 306DD37B491 for ; Mon, 12 Feb 2001 13:03:06 -0800 (PST) Received: from diala11 (unverified [200.255.108.11]) by www3.infolink.com.br (Vircom SMTPRS 4.2.181) with SMTP id ; Mon, 12 Feb 2001 19:03:02 -0300 Message-ID: <00b401c0953f$92453020$0b6cffc8@infolink.com.br> From: "Antonio Carlos Pina" To: "Luigi Rizzo" Cc: References: <200102120825.f1C8PLH84645@iguana.aciri.org> Subject: Re: BRIDGE breaks ARP? Date: Mon, 12 Feb 2001 19:03:02 -0300 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 Luigi, I'm running a Bridge+IPFW+Dummynet box between my lan and my router (which is my default gateway). I access the box via SSH and everything is working great. I would like to do some routing in this box too (offloading the router), but I would like to do that WITHOUT have to change all default gateways in our Workstations. I thought the best option here would be to configure the DEFAULT GATEWAY IP ADDRESS in the Bridge Box, but in this scenario I would have to change the router ip address also (since I will be using it in our bridge box). Is there any way you know that I can intercept and re-route packets using the box as bridge ? I mean, the default gateway is still my router, but some packets don't arrive in it, because the bridge box can send them to another ethernet card. Thanks for listening and best regards, Antonio Carlos Pina apina@infolink.com.br ----- Original Message ----- From: "Luigi Rizzo" To: "Vincent Poy" Cc: ; ; ; Sent: Monday, February 12, 2001 5:25 AM Subject: Re: BRIDGE breaks ARP? > > > whether or not you have "options BRIDGE' in your kernel config file. > > > (or a message saying "BRIDGE ..." when the system boots) > > > > My kernel config doesn't have the BRIDGE option so I guess the > > bridging code is part of ET's drivers. > > yes, i suspected so... > > luigi > > > > > Cheers, > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > WurldLink Corporation / / / / | / | __] ] > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 > > > > > > bg0: flags=8843 mtu 1500 > > > > > > inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 > > > > > > inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 > > > > > > inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 > > > > > > ether 00:00:00:03:00:00 > > > > > > > > > > > > I've asked Dennis at ETinc the question and his response was: > > > > > > > > > > > > if you want to route from one DLCI to the other then you have to put them > > > > > > in separate bridge groups with their own subnet. You are creating isolated > > > > > > segments with the ipmap functionality...the mechanism is designed for end > > > > > > users who get 1 or 2 addresses. > > > > > > > > > > > > You COULD fix the O/S to route back to the same interface, but I dont know > > > > > > how complicated that would be. I dont think there is an easy way to > > > > > > disable > > > > > > split-horizon. > > > > > > > > > > > > Dennis > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > I'm not sure if this is related but we're using FreeBSD with a > > > > > > > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > > > > > > > where for example, if a bridge group was like... > > > > > > > > > > > > > > > > 216.235.44.1 255.255.255.0 > > > > > > > > > > > > > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > > > > > > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > > > > > > > can't see each other if they are in the same subnet. So it seems all > > > > > > > > machines in the bridge group can see the gateway and the rest of the > > > > > > > > world but not each other. Is there a way around this? This is with > > > > > > > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message