Date: Sun, 19 Jun 2005 10:48:46 +0200 From: Michal Vanco <vanco@satro.sk> To: Gleb Smirnoff <glebius@freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Jose M Rodriguez <josemi@freebsd.jazztel.es> Subject: Re: Routes not deleted after link down Message-ID: <200506191048.49883.vanco@satro.sk> In-Reply-To: <20050619082944.GA11972@cell.sick.ru> References: <51688.147.175.8.5.1119105461.squirrel@webmail.satronet.sk> <200506182214.33279.josemi@redesjm.local> <20050619082944.GA11972@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart93270823.9id32FKxkg Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 19 June 2005 10:29, Gleb Smirnoff wrote: > On Sat, Jun 18, 2005 at 10:14:32PM +0200, Jose M Rodriguez wrote: > J> Second, you may need a route daemon for this. ospf is a well known > J> canditate where convergence in case of lost link is a must. > > While an OSPF daemon may stop advertising the affected route to its > neighbors, the kernel will still have the route installed and thus > the box won't be able to contact other hosts on the connected net, > while they are reachable via alternate pass. Routing protocol should be responsible for removing affected routes from FI= B.=20 =46or example quagga should remove all routes learned via particular ospf=20 neighbour when that neighbour is not reachable anymore due to link goes dow= n.=20 But in case when no daemons are used (`static' and `connected' are also=20 `routing protocols'), kernel should be responsible for doing that. > > I've checked that Cisco routers remove route from FIB when interface > link goes down. I haven't checked Junipers yet. Junipers do the same. It is the only feasible behaviour for router. > > From my viewpoint, removing route (or marking it unusable) is a correct > behavior for router. Not sure it is correct for desktop. > Sure. > My vote is that we should implement this functionality and make it > switchable via sysctl. I'd leave the default as is. > Agree. --nextPart93270823.9id32FKxkg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBCtTFx2/VqJwUsLAMRAuBlAKChluaPjo3qwcqw9oNQ2Z4m2v4cQgCgjUQH 1Jmp7EE0WxJBY9RJjsyqk8M= =Vm+C -----END PGP SIGNATURE----- --nextPart93270823.9id32FKxkg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506191048.49883.vanco>