Hi Ondrej, Thanks for prompt reply. A couple of question: 1. How to configure based on match AS for example in cisco, they have regular expression like _7898$, what is the equivalent of this command in BIRD config file (do you use the same regular expression syntax)? 2. I managed to set the community to let say 1000:1234, how to put it in the filter to match this community (let say, we want to advertise to certain peer only the routes that match community 1000:1234) I'm sorry for such a basic question, I'm not used to config command and thanks a lot in advance. Regards, Affandi Indraji -----Original Message----- From: Ondrej Zajicek [mailto:santiago@crfreenet.org] Sent: Monday, January 25, 2010 5:16 PM To: Affandi INDRAJI Cc: bird-users@network.cz Subject: Re: Command Syntax for BIRD configuration On Mon, Jan 25, 2010 at 03:51:42PM +0800, Affandi INDRAJI wrote:
Hi,
I tried to find out the documentation of the Command Syntax for BIRD configuration, for example in cisco if we want to set the community for certain peer we can configure it like this:
route-map test-in permit 10 set community 17819:64901 additive ! neighbor 10.1.1.1 route-map test-in in !
I try to figure out base on the documentation available in http://bird.network.cz/ but I can't find any (or maybe I miss it out).
Here is the documentation of BIRD commands: http://bird.network.cz/?get_doc&f=bird-4.html But these commands are not used for configuration, but mostly for examination of the state of protocol sessions and routing tables. BIRD is configured by editing a config file, not by a command line. The syntax of the config file is here: http://bird.network.cz/?get_doc&f=bird-3.html http://bird.network.cz/?get_doc&f=bird-5.html http://bird.network.cz/?get_doc&f=bird-6.html For example, adding the community for certain peer can be done using filters, as it is shown in the last link. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."