[j-nsp] BGP import policy to accept prefixes from advertising ASonly.

[Patrik Joly]

Hi
How about:
^.$
But that only works if your'e direcly connected and there is no prepending.
/Peter
----- Original Message ----- 
From: "John Senior" <js at irishbroadband.ie>
To: <juniper-nsp at puck.nether.net>
Sent: Thursday, October 14, 2004 2:21 AM
Subject: [j-nsp] BGP import policy to accept prefixes from advertising
ASonly.


> Hi all,
>
> I am sure I came across this a while ago but can't now find it, I don't
think
> I imagined it!
>
> Anyway, is it possible to create a BGP import policy statement that will
> only accept prefixes from the advertising AS without having to specify
> the AS number?  I.e. can I create a policy statement that is generic that
> I can apply to a bunch of peers without having to create a specific one
> for each peer?
>
> e.g.
>
> policy-statement only-allow-routes-originating-in-peer-as {
> term 10 {
> from {
> as-path "^originating AS number$"
> }
> then accept;
> term 20 {
> then reject;
> }
> }
>
> protocols bgp {
> group ebgp-peer1 {
> peer-as 12345;
> import only-allow-routes-originating-in-peer-as;
>                         blah blah etc etc.
> }
> group ebgp-peer2 {
> peer-as 23456;
> import only-allow-routes-originating-in-peer-as;
>                         blah blah etc etc.
> }
> }
>
> For peer1 I only want as-path ^12345$ and similarly for peer2 I only want
^23456$.
>
> Would I achieve this with configuration groups?
>
> All the best,
>
> John.
> --
> John Senior <js at irishbroadband.ie>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>