From owner-freebsd-net@FreeBSD.ORG Mon Jun 14 08:11:47 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 804DB16A4CE for ; Mon, 14 Jun 2004 08:11:47 +0000 (GMT) Received: from diaspar.rdsnet.ro (diaspar.rdsnet.ro [213.157.165.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2F4243D4C for ; Mon, 14 Jun 2004 08:11:46 +0000 (GMT) (envelope-from dudu@diaspar.rdsnet.ro) Received: (qmail 88698 invoked by uid 89); 14 Jun 2004 08:13:08 -0000 Received: from unknown (HELO diaspar.rdsnet.ro) (dudu@diaspar.rdsnet.ro@213.157.165.224) by 0 with AES256-SHA encrypted SMTP; 14 Jun 2004 08:13:08 -0000 Date: Mon, 14 Jun 2004 11:13:05 +0300 From: Vlad GALU To: freebsd-net@freebsd.org Message-Id: <20040614111305.4e06f328.dudu@diaspar.rdsnet.ro> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Mon__14_Jun_2004_11_13_05_+0300_dL7/BCNTB4+mygu=" Subject: 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 08:11:47 -0000 --Signature=_Mon__14_Jun_2004_11_13_05_+0300_dL7/BCNTB4+mygu= Content-Type: multipart/mixed; boundary="Multipart=_Mon__14_Jun_2004_11_13_05_+0300_9nthHlJcxcq4Cx5h" --Multipart=_Mon__14_Jun_2004_11_13_05_+0300_9nthHlJcxcq4Cx5h Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit 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. --Multipart=_Mon__14_Jun_2004_11_13_05_+0300_9nthHlJcxcq4Cx5h Content-Type: application/pgp-signature; name="00000000.mimetmp" Content-Disposition: attachment; filename="00000000.mimetmp" Content-Transfer-Encoding: base64 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KQ29tbWVudDogJycKCmlEOERCUUZBelZ2R3Vl VXBBWVlOdFRzUkFzOC9BSjlpb0kxUXBIblVUd3lPQ08yWG1aV05lMWQ3OEFDZEd5bjEKOHJ2eGV5 eDZQQkZXeVFuelQrdDZxVHc9Cj10aVllCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQoK --Multipart=_Mon__14_Jun_2004_11_13_05_+0300_9nthHlJcxcq4Cx5h-- --Signature=_Mon__14_Jun_2004_11_13_05_+0300_dL7/BCNTB4+mygu= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAzV4UP5WtpVOrzpcRAuC/AJ9ISxyN200WQ2gZfzp1IcWcPfyBcQCfZ5lh N3cTgXcs5t/hSPbhmlP5ntw= =uck0 -----END PGP SIGNATURE----- --Signature=_Mon__14_Jun_2004_11_13_05_+0300_dL7/BCNTB4+mygu=--