From owner-freebsd-current@FreeBSD.ORG Sat Sep 4 18:03:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 254F816A4CE for ; Sat, 4 Sep 2004 18:03:24 +0000 (GMT) Received: from web41406.mail.yahoo.com (web41406.mail.yahoo.com [66.218.93.72]) by mx1.FreeBSD.org (Postfix) with SMTP id E69AD43D4C for ; Sat, 4 Sep 2004 18:03:23 +0000 (GMT) (envelope-from davemac11@yahoo.com) Message-ID: <20040904180323.1762.qmail@web41406.mail.yahoo.com> Received: from [67.241.33.20] by web41406.mail.yahoo.com via HTTP; Sat, 04 Sep 2004 11:03:23 PDT Date: Sat, 4 Sep 2004 11:03:23 -0700 (PDT) From: Dave McCammon To: Gleb Smirnoff In-Reply-To: <20040904081824.GB72131@cell.sick.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-current@freebsd.org Subject: Re: 5.3 Beta2 bridging (update 2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 18:03:24 -0000 --- Gleb Smirnoff wrote: > On Wed, Sep 01, 2004 at 09:41:00AM -0700, Dave > McCammon wrote: > D> Got the bridging to work after cvsup yesterday(I > think > D> it was the rebuild but not for sure). > D> > D> em0 - has ip > D> em1 - no ip > D> > D> Anyway, with both cables plugged in, traffic > passes > D> through the box. Weird thing is, the box can't > get to > D> (ssh, ping) other machines on the em1 side but > can get > D> to machines on the em0 side. > D> Machines on the em1 side can get to machines on > the > D> em0 side. Machines on the em0 side can get to > machines > D> on the em1 side and can get to the bridging box. > > Do you have option BRIDGE in kernel? Or do you > just load module bridge.ko? > options BRIDGE in kernel. The bridge works fine now. Except that I need to "down" than "up" em1 when it has been unplugged for a great length of time. Someone mentioned to change net.inet.ip.check_interface to 0. Apparently there was a change in net.inet.ip.check_interface where, in 4.10, it is set to net.inet.ip.check_interface=0 and in 5.3 BETA2(and in 5.2.1) it is set net.inet.ip.check_interface=1. The above difference caused me alot of confusion when I was initially testing the bridge to see if traffic was passing through(I was trying to ssh out from the bridge machine to machines on the em1(no ip) side). I have a 4.10 bridge that is working fine so this change was new to me. Thanks for your time. __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail