Re: KRT: Received route with strange next-hop

2015-11-25 Thread Ondrej Zajicek
On Thu, Nov 19, 2015 at 08:25:01AM -0500, Brian Rak wrote: > >Generally, BIRD expects that the next hop address is reachable by > >interface address prefix. In your case you just add device route for > >45.63.4.188/32 instead of adding peer address of 45.63.4.188 to veth0. It > >is true that for th

Re: pattern matching for bgp communities

2015-11-25 Thread Ondrej Zajicek
On Tue, Nov 24, 2015 at 12:19:29PM +0100, Job Snijders wrote: > Hi all, > > Is there a way to do pattern matching or regex matching on the BGP > communities associated with a prefix? Hi I don't think so. Generally, we could add something like member/filter operation on communities and similar l