Thanks for the advice. Filtering and route manipulation hasn’t been a
problem for me. I’m very careful to prevent leakage, etc. My current issue
is scaling my management of our prefix announcements. Every time I add a
new block, I need to modify all of my edge routers etc. I understand I can
use IR
To elaborate slightly on what others have said in terms of protecting
against leaks;
it's a good idea to filter outbound in a conservative way such that you
only send
what you "expect" in terms of community values and/or prefixes and/or
AS-paths.
For instance, if something gets into your BGP that
Thanks Mark,
This helps and definitely shows Im heading in the right direction.
Thanks,
On Tue, Jan 31, 2012 at 2:17 AM, Mark Tinka wrote:
> On Tuesday, January 31, 2012 03:04:15 PM Joe Marr wrote:
>
> > What do you use for reflectors, hardware(Cisco/Juniper)
> > or software daemons(Quagga)?
>
On Tuesday, January 31, 2012 03:04:15 PM Joe Marr wrote:
> What do you use for reflectors, hardware(Cisco/Juniper)
> or software daemons(Quagga)?
We operate 2x networks.
One of them runs Cisco 7201 routers as route reflectors,
while the other runs Juniper M120 routers.
The large Juniper router
Thanks Mark
What do you use for reflectors, hardware(Cisco/Juniper) or software
daemons(Quagga)?
I've been toying with the idea of using Quagga route servers to announce
our prefixes to our edge routers and redistribute BGP annoucements learned
from downstream customers. Only drawback is the lack
On Tuesday, January 31, 2012 01:01:30 AM Joe Marr wrote:
> I currently use static routes and tags on my edge routers
> to inject route into BGP. The tags correspond to
> communities that reflect how the routes are announced
> per region.
> I would love to heat from others on how they handle this.
6 matches
Mail list logo
