AS Path Filter list
Anibe Onuche
a.onuche at nixp.net
Mon Jul 1 12:23:25 CEST 2013
Hello
This is a snippet of my configurations
/
function match_as () {
if (bgp_path ~ [= * 1111 =]) then return true;
if (bgp_path ~ [= 2222 =]) then return true;
return false;
}
filter bgp_in_AS111
{
..
..
if ! (match_as_AS()) then reject;
accept;
}
template bgp Peer {
..
..
..
import filter bgp_in_AS111;
}/
from the above i want Bird to allow AS 1111 and other subsequent AS
paths to be allowed access.
But for AS 2222, no subsequent AS Paths to be allowed.
Am i on the right track?
In-case you are wondering why the need AS1111 represent Networks with
good network administrators while AS 2222 are those who don't
On 6/28/2013 11:04 AM, Ondrej Filip wrote:
> On 28.6.2013 11:57, Anibe Onuche wrote:
>> Hello All.
> Hi Anibe,
> I am not sure what do you really want. But I suggest you, to look at
> our WIKI - https://redmine.labs.nic.cz/projects/bird/wiki/Examples
>
> There is a lot of god examples, how to configure BIRD as route server
> including filtering.
>
> Ondrej
>
>
>> I work with an IX and considering implementing bird as my route server.
>> Was successful in my lab implementation
>> need a few config to be through.
>>
>>
>> I want to configure a function on my bird that will only allow
>> certain network containing some as-path to be used.(i.e as-path filters)
>> While at that, other network have valid bgp paths attached to their
>> as-path should also be imported.
>>
>> How do i go about this ?
>>
>> Regards
>> Anibe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20130701/23056553/attachment.html>
More information about the Bird-users
mailing list