From owner-freebsd-net@FreeBSD.ORG Mon Jun 14 15:00:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1527016A4CE for ; Mon, 14 Jun 2004 15:00:53 +0000 (GMT) Received: from mx01.bos.ma.towardex.com (mx01.bos.ma.towardex.com [65.124.16.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0B0643D1F for ; Mon, 14 Jun 2004 15:00:52 +0000 (GMT) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 7297B2F8FA; Mon, 14 Jun 2004 11:00:25 -0400 (EDT) Date: Mon, 14 Jun 2004 11:00:25 -0400 From: James To: Vlad GALU Message-ID: <20040614150025.GA43698@scylla.towardex.com> References: <20040614111305.4e06f328.dudu@diaspar.rdsnet.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040614111305.4e06f328.dudu@diaspar.rdsnet.ro> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org Subject: Re: Fw: Re: A quagga-related issue X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 15:00:53 -0000 can you try running 'sh ip route a.b.c.d', where a.b.c.d is the connected route in question, to an interface that is down? Does it shown down/unavailable? (on zebra telnet port 2601 cli or vtysh) If it shows DOWN/not available, quagga will not redistribute. The problem is that quagga can't know whether tunnel is down or up. if tunnel is up, it passes packets between two endpoints. if its down, it doesn't. i think a solution to this is to provide link detection of tunneling interfaces by providing a heartbeat or keepalives, but thats more work heh. -J On Mon, Jun 14, 2004 at 11:13:05AM +0300, Vlad GALU wrote: > > > Begin forwarded message: > > Date: Mon, 14 Jun 2004 09:03:19 +0100 > From: Bruce M Simpson > To: Vlad GALU > Subject: Re: A quagga-related issue > > > Hi, > > Unfortunately I'm not a quagga developer, so you might have better luck > getting an answer to your question by posting to -net or asking on the > Quagga forums. I think there may be a configuration option to change the > behaviour you're talking about but can't recall what it might be. > > Regards, > BMS > > On Mon, Jun 14, 2004 at 09:43:43AM +0300, Vlad GALU wrote: > > > > I've set up a BGP session with a Cisco peer. For some reasons, I > > wanted > > all connected routes to be redistributed to BGP. On the same system > > that ran quagga (a FreeBSD machine) I had openvpn open several hundred > > interfaces (btw, about the minor number generation, that was OK. I > > don't know why mc kept showing strange numbers) at once. The problems > > relies in the fact that tun interfaces can't be removed. Then quagga > > parses the list of interfaces to gather the connected routes. Because > > the tun interfaces are still there, quagga reports the routes as well. > > How would you feel about changing the code a little bit, for quagga > > not adding the routes connected to interfaces marked as 'down' ? > > > > ---- > If it's there, and you can see it, it's real. > If it's not there, and you can see it, it's virtual. > If it's there, and you can't see it, it's transparent. > If it's not there, and you can't see it, you erased it. -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net