[alcatel-nsp] Advertising prefixes to BGP peer.

[Thedin Guruge]

guys, if i understand this right, the intention is to get /23 from customer
and advertise it as 2x/24? if it's always a known /23 then why not create 2
x /24 static routes with next-hop indirect pointing at /23...

'cos aggregate isn't useful in this case is it?

On Tue, Dec 14, 2010 at 10:32 AM, Scott Weeks <surfer at mauigateway.com>wrote:

>
>
> --- surfer at mauigateway.com wrote:
> You can inject specifics that're not in the routing table by the use of a
> null route.
> -------------------------------------------
>
>
> My apologies, that's a "black-hole route" in Alcatel parlance, as shown by
> Stefano Gridelli's response, and not a null route.  Same idea, though.
>
> scott
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --------------
> > ---------------
> > --------------
> > _______________________________________________
> > alcatel-nsp mailing list
> > alcatel-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/alcatel-nsp
> >
>
>
>
> _______________________________________________
> alcatel-nsp mailing list
> alcatel-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>
>
> _______________________________________________
> alcatel-nsp mailing list
> alcatel-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20101214/d96af6ec/attachment.html>