Re: Dynamically Changing Exit Policy (iBGP)

2007-10-30 Thread Benjamin Howell
On Tue, Oct 30, 2007 at 12:55:24AM -0400, Jon Lewis wrote: > > On Mon, 29 Oct 2007, Benjamin Howell wrote: > > >On Mon, Oct 29, 2007 at 04:53:50PM -0400, Deepak Jain wrote: > >>You can "nail" down your announcements to external peers by tying their > >>network blocks to a route-of-last resort on

Re: Dynamically Changing Exit Policy (iBGP)

2007-10-29 Thread Jon Lewis
On Mon, 29 Oct 2007, Benjamin Howell wrote: On Mon, Oct 29, 2007 at 04:53:50PM -0400, Deepak Jain wrote: You can "nail" down your announcements to external peers by tying their network blocks to a route-of-last resort on one of your loopbacks. This will prevent flapping externally. Point tak

Re: Dynamically Changing Exit Policy (iBGP)

2007-10-29 Thread Deepak Jain
Perhaps a drawing of your architecture might make your travails more clear? Benjamin Howell wrote: On Mon, Oct 29, 2007 at 04:53:50PM -0400, Deepak Jain wrote: You can "nail" down your announcements to external peers by tying their network blocks to a route-of-last resort on one of your loopba

Re: Dynamically Changing Exit Policy (iBGP)

2007-10-29 Thread Benjamin Howell
On Mon, Oct 29, 2007 at 04:53:50PM -0400, Deepak Jain wrote: > You can "nail" down your announcements to external peers by tying their > network blocks to a route-of-last resort on one of your loopbacks. This > will prevent flapping externally. Point taken, but it's actually difficult to nail d