From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 19:31:06 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C7C416A4CE for ; Sat, 11 Sep 2004 19:31:06 +0000 (GMT) Received: from priv-edtnes57.telusplanet.net (outbound01.telus.net [199.185.220.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AAD543D31 for ; Sat, 11 Sep 2004 19:31:05 +0000 (GMT) (envelope-from pfak@telus.net) Received: from hartkiem2nnl7x ([206.116.24.146]) by priv-edtnes57.telusplanet.netSMTP <20040911193104.TWRT14797.priv-edtnes57.telusplanet.net@hartkiem2nnl7x>; Sat, 11 Sep 2004 13:31:04 -0600 Message-ID: <002d01c49835$e157c1d0$bb01a8c0@hartkiem2nnl7x> From: "Peter Kieser" To: "SharkTECH Maillists" , References: <006001c497fa$08f971c0$dec2fea9@psyxakias> Date: Sat, 11 Sep 2004 12:31:03 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-7"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: Interface Bonding & Bridging problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2004 19:31:06 -0000 BRIDGE and bonding (ng_fec, etc.) don't work together. This was *supposed* to be fixed for 5.3-RELEASE, but I don't believe it has been. -- Peter Kieser Opticate Technologies Home: 604.338.9294 / Pager: 604.205.0182 / Email: peter@opticate.net // "Learn from yesterday, live for today, hope for tomorrow." // ----- Original Message ----- From: "SharkTECH Maillists" To: Sent: Saturday, September 11, 2004 5:22 AM Subject: Interface Bonding & Bridging problem > Hello, > > I have been running a FreeBSD 4.10-STABLE server having 3 nics installed > but > was using only 2 of them (1 for uplink and 1 for switch) to monitor, > filter > and shape my network and had absolutely no problems at all. > > However, in order to increase the ability of handling even more packets > (especially while filtering incoming DDoS), I decided to get a 2nd uplink > from backbone, connect it to em1, bond em0/em1 (uplinks) to ngeth0/fec0 > (virtual interface) and bridge ngeth0/fec0 with em2 (switch link). In > order > for this to work, etherchanneling is enabled between uplink1/uplink2 at > the > backbone side. > > The problem is although bonding seems to work fine as I can assign IPs at > fec0/ngeth0 and send/receive packet with both cards using the virtual > interface, I cannot get bridging to work at all between > ngeth0/fec0(virtual) > and em2(switch). There are no errors in logs, it just doesn't seem to > bridge. > > After doing a 2 days research in Google, FreeBSD maillists, web articles > and > asking for help in freebsdhelp IRC channels, I ended up that someone in > FreeBSD maillists may be able to help me providing me a different > bonding/bridging way or even by applying a patch. > > I was thinking that the solution may be to do both bonding & bridging > using > netgraph, and not bridging using FreeBSD's kernel bridge. I'd be glad to > try > this but unfortunately I haven't figured out how, even after reading > several > articles. So if anyone can help me on this step-by-step, please do. > > I will appreciate any replies after you take a look at the diagrams and > settings below, that are showing what exactly I have done until now. > > > Best Regards, > > Angelos Pantazopoulos > freebsd@sharktech.net > SharkTECH Internet Services