Transit with OpenBGPd... How to allow only on or two as neighbor only ?
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 (all|none|self|default-route)
Problem is that I need to announce for example a pair of AS number..
How can I do that with openbgpd ?
Thanks !
/Xavier
--
Quand on essaye continuellement, on finit par y arriver. Donc, plus ca
rate, plus on a de chance que ca marche...
(Proverbe Shadok)
Re: Transit with OpenBGPd... How to allow only on or two as neighbor only ?
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
announce foo
}
With foo :
announce (all|none|self|default-route)
Problem is that I need to announce for example a pair of AS number..
How can I do that with openbgpd ?
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 table
is reexported).
--
:wq Claudio
Re: Transit with OpenBGPd... How to allow only on or two as neighbor only ?
[...] 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 table is reexported). Thanks Claudio, But can you provide me a more detailed example. Because I have some difficulies to make a filter for such setup... /Xavier -- Quand on essaye continuellement, on finit par y arriver. Donc, plus ca rate, plus on a de chance que ca marche... (Proverbe Shadok)
Re: Transit with OpenBGPd... How to allow only on or two as neighbor only ?
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 work in a save manner (defaulting to self and so not the full table is reexported). Thanks Claudio, But can you provide me a more detailed example. Because I have some difficulies to make a filter for such setup... The best way to make a scalable setup is by using bgp communities. That way your transit/peering routers advertise based on information you can set on origin or ingress into your network, not depending on the prefix/as itself. I have not checked how bgpd and community support looks in -current, but when experimenting a few months back I had some problems with setting multiple communities and I was also forced to use an external route-server to see what was happening in my test network. I intend to give this a new try when I have finished the project I'm currently working on. /Tony -- Tony Sarendal - [EMAIL PROTECTED] IP/Unix -= The scorpion replied, I couldn't help it, it's my nature =-
