Date: Tue, 03 Jan 2006 21:35:58 +0100 From: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= <lukasz@bromirski.net> To: Julian Elischer <julian@elischer.org> Cc: freebsd-net@freebsd.org Subject: Re: Reverse Path Filtering check in ip_input.c Message-ID: <43BAE02E.2020401@bromirski.net> In-Reply-To: <43BAC24C.9050702@elischer.org> References: <43B9C7CC.7090703@mr0vka.eu.org> <20060103115120.GG840@bashibuzuk.net> <43BA82F7.7070408@bromirski.net> <43BAC24C.9050702@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > Several routes with the same dest would be interesting but how do you > select between them? Via some sort of load-balancing or policy routing mechanism on network stack level? There is so much we miss in current FreeBSD stack in this area it's hard to say some single feature will change everything completely. I only mentioned OpenBSD KAME import because they are clearly going for having multihomed router fully operable and we're lacking in this area. Also, Henning, Claudio and other team members push for routing protocols interoperability (OpenOSPFd and OpenBGPd integration) which again is far from what we're currently able to do and integrate. Andre as I understand is cleaning code and making everything run a lot faster (especially routing operation optimization is great thing), but I'm worried that being able to have things like administrative distance for various routing protocols (which would enable router with for example OSPF and BGP to choose routes from both protocols in clear selection process), ability to store few paths for the same destination via different interfaces or next-hops is a long road ahead. But there's always someone who has to do first step... ;) -- this space was intentionally left blank | Łukasz Bromirski you can insert your favourite quote here | lukasz:bromirski,net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43BAE02E.2020401>