more specific routes in today reality
Mirta Matic mirta.matic at hinet.hr
Tue Oct 9 15:55:06 CEST 2001
Hello, have you ever heard for RADWARE solution for that problem? Some RADWARE box can check distance to destination via both ISP's and makes decision from what IP address range have to get address for NAT (of course, customer have to have two ranges of addresses). If connection via one ISP failed, all traffic will be rerouted via another using IP address from IP address range of that ISP. Mirta Matic mirta.matic at hinet.hr tel: +385 1 4914 207 fax: +385 1 4914 222 ----- Original Message ----- From: "Gert Doering" <gert at space.net> To: "Sascha E. Pollok" <sp at iphh.net> Cc: "Gert Doering" <gert at space.net>; "Vladimir A. Jakovenko" <vovik at lucky.net>; <lir-wg at ripe.net>; <routing-wg at ripe.net> Sent: Tuesday, October 09, 2001 1:44 PM Subject: Re: more specific routes in today reality > Hi, > > On Tue, Oct 09, 2001 at 01:22:43PM +0200, Sascha E. Pollok wrote: > > >> "- If PI is requested for multi-homing please explain why the second > > >> provider cannot route PA space as a more specific route (with the > > >> PA block holder adding a more specific route too)." > > > > > >This doesn't specify who is originating the BGP prefix. Both providers > > >have to *route* it, of course. > > > > We got this reply to a PI-space request for a customer that does > > not have his own ASN therefore ISPs would need to originate the > > route. Don't you think that this implies originating the prefix > > from two different ASes? (would appear when doing "sh ip bgp incons"). > > Yes. But this would not be any different from getting a PI space and > announcing it inconsistently, that is, originating it from both ISPs. > > Which is not a good practice in any case - I agree on that. > > Gert Doering > -- NetMaster > -- > SpaceNet AG Mail: netmaster at Space.Net > Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 > 80807 Muenchen Fax : +49-89-32356-299 > >
[ lir-wg Archives ]