* falz <[email protected]> [2011-04-28 16:57]: > #################################### > PREFIX_ORIGINATE = "{ 10.171.0.0/19, 101.192.144.0/24, 91.199.248.0/24 > }" > COMMUNITY_TEST = "65000:666" > > network 10.171.0.0/19 > network 101.192.144.0/24 > network 91.199.248.0/22 > > # <default allow/deny stuff from sample conf is here> > > match from any prefix $PREFIX_ORIGINATE set localpref 140
so this is matching inbound, aka routes you learn form any peer > # bgpctl show ip bgp > flags destination gateway lpref med aspath origin > AI*> 10.171.0.0/19 0.0.0.0 100 0 i and here you are looking at outgoing announcements, prefixes that originate on your box. aka everything works as intended :) > The 'match' statements I'm using above do work if I'm receiving routes > from another peer so the syntax does appear to be valid. I've also > tried them in the 'neighbor' statement with no luck. Doing so there > also seems odd since I would have to have multiple neighbor statements > for each originating prefix. match out to any prefix $foo set $bar (note that this doesn't make sense for localpref, that is, as the name sez, local to your router) -- Henning Brauer, [email protected], [email protected] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
