Transit with OpenBGPd... How to allow only on or two as neighbor only ?

2005-10-06 Thread Xavier Beaudouin
Hello, I'd like to find the good working solution when sending AS announces to our peering / transit neigbor. In fact on bgpd.conf man page we have : neighbor $peer1 { remote-as 65001 announce foo } With foo : announce

Re: Transit with OpenBGPd... How to allow only on or two as neighbor only ?

2005-10-06 Thread Claudio Jeker
On Thu, Oct 06, 2005 at 03:18:41PM +0200, Xavier Beaudouin wrote: Hello, I'd like to find the good working solution when sending AS announces to our peering / transit neigbor. In fact on bgpd.conf man page we have : neighbor $peer1 { remote-as 65001

Re: Transit with OpenBGPd... How to allow only on or two as neighbor only ?

2005-10-06 Thread Xavier Beaudouin
[...] The announce keyword is mostly for simple setups. For transit providers announce should be set to all and real bgp filtering should be used. The idea of announce is that small multihomed setups with e.g. two uplinks just work in a save manner (defaulting to self and so not the full

Re: Transit with OpenBGPd... How to allow only on or two as neighbor only ?

2005-10-06 Thread tony sarendal
On 06/10/05, Xavier Beaudouin [EMAIL PROTECTED] wrote: [...] The announce keyword is mostly for simple setups. For transit providers announce should be set to all and real bgp filtering should be used. The idea of announce is that small multihomed setups with e.g. two uplinks just