Claudio Jeker wrote:
On Fri, Sep 02, 2005 at 01:53:03PM +0100, Karl Austin wrote:
Hi,
I'm just testing out OpenBGPD here, and am trying to set multiple
communities for a BGP peer, however it appears that no matter what I
try, only the very last community specified gets set, overwriting those
previous. I've scoured Google and the lists and can't seem to see this
addressed anywhere. Is it just that the setting of multiple communities
is not supported, or am I missing something obvious?
I've tried:
neighbor 192.168.1.1 {
set community 65400:100
set community 65400:200
set community 65400:300
}
and also tried match statements e.g.
match from 192.168.1.1 set { community 65400:100, community 65400:200,
community 65400:300 }
along with separate match lines for each community.
Which version of OpenBGPD are you useing?
This problem should be fixed in -current.
I've just updated to the latest Snapshot available from FTP and it still
seems to only set a single community (the last one specified). I've
checked on two different peers running two different BGPDs and both of
them only show the final community in the list as being sent.
Thanks,
Karl Austin
