On Wed, Sep 19, 2007 at 11:51:10AM +0200, Claer wrote: > On Tue, Sep 18 2007 at 06:20, Claudio Jeker wrote: > > On Tue, Sep 18, 2007 at 12:25:02PM -0500, [EMAIL PROTECTED] wrote: > > > I saw from a thread a while back that putting as-path regular > > > expression support into OpenBGPd was being considered. I'm testing > > > out a 4.2 snapshot, and so far it doesn't seem to be there just yet. > > > > > > For various reasons, I'd like to be able to tweak prefixes based on > > > some specific as-path values a la Juniper. This kind of stuff: > > > > > > Criteria: Path whose second AS number must be 56 or 78. > > > Regular Expression: (. 56) | (. 78) or . (56|78) > > > Example Matches: 1234 56 and/or 34 78 > > > > > > http://www.juniper.net/techpubs/software/junos/junos74/swconfig74-policy/html/policy-extend-match-config3.html > > > > > > Anyone know if this is in the works? > > > > > > > Adding a better AS filter list is on my todo list since a long time. We > > will not implement a full regex -- cisco demonstrated once again why regex > > is a bad idea. > > > > Just a few thoughts. I do not like the | (or) operator. This can be > > written with two rules without any issues. I guess we will support +, ., - > > , ^ and $. > > About OpenBGPd todo list, is there any plan to implement bpg > confederations ? >
Honestly, no. I have not the free time to do that but my company does consulting which can include developing such features if you are in desperate need. I also accept diffs if somebody likes to implement it. -- :wq Claudio
