Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread Martin Hein
On Thu, 28 Apr 2011 08:50:41 -0500 falz m...@falz.net wrote: 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 #

Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread falz
Martin Hein wrote: network 10.171.0.0/19 set { localpref 140 metric 12 community 65000:666 } I did test this before but only with a bgpctl reload. I've retested this above with fully stopping and starting bgpd and it does then work. Is there no graceful way to do this? Seems odd that bgpd has

Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread Henning Brauer
* falz m...@falz.net [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

Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread Henning Brauer
* falz m...@falz.net [2011-04-28 18:48]: Martin Hein wrote: network 10.171.0.0/19 set { localpref 140 metric 12 community 65000:666 } I did test this before but only with a bgpctl reload. I've retested this above with fully stopping and starting bgpd and it does then work. Is there no

Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread falz
On Thu, Apr 28, 2011 at 10:41 AM, falz m...@falz.net wrote: Martin Hein wrote: network 10.171.0.0/19 set { localpref 140 metric 12 community 65000:666 } I did test this before but only with a bgpctl reload. I've retested this above with fully stopping and starting bgpd and it does then

Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread Claudio Jeker
On Thu, Apr 28, 2011 at 11:02:40AM -0500, falz wrote: On Thu, Apr 28, 2011 at 10:41 AM, falz m...@falz.net wrote: Martin Hein wrote: network 10.171.0.0/19 set { localpref 140 metric 12 community 65000:666 } I did test this before but only with a bgpctl reload. I've retested this above

Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread falz
Henning Brauer Wrote: if this doesn't work with reload and clearing the session(s) in question this would be a bug. I'd like to confirm if it is or not This is a fresh install of i386 4.8. My current workaround is to replicate what's in my config: network 10.171.0.0/19 set { localpref 140

Re: OpenBGPD communities, localpref on originating prefixes

2011-04-28 Thread falz
Henning Brauer wrote: so this is matching inbound, aka routes you learn form any peer (note that this doesn't make sense for localpref, that is, as the name sez, local to your router) Thanks, I didn't realize that the match/allow/deny rules apply only to prefixes passing between neighbors,