Filtering on Export-Protocol

[Michael Rack]

Can you explain what you mean?

How should I change my scripts?

I think it will be a good workaround when I simply use functions instead of
filters, so I can bypass some parameters.

*protocol bgp *'peer-neo' {
>       ipv4 { export where *filter_common_ipv4_out(* "peer-neo" *)*; };
> }
> *function  *filter_common_ipv4_out( string remote_peer_name ) {
>       if  remote_peer_name  = 'peer-neo' then .....;
> }


It is stupid because i define the peer-name twice.
But for now it will do the job relatively easily.

I have over 40 peers, so I have to write the function / filter for common
use.

Am Mi., 8. Apr. 2020 um 19:39 Uhr schrieb Maria Matějka <
maria.matejka at nic.cz>:

> Hello!
>
> Currently not supported. Is simple exact match enough for your purposes?
> This may be simply added to the filter language.
>
> Maria
>
> On April 8, 2020 6:47:49 PM GMT+02:00, Michael Rack <mail at michaelrack.de>
> wrote:
>>
>> Hi Guys,
>>
>> if i am in the EXPORT-Routine, how can i access the "protocol-name" of
>> that instance that is currently using my function?
>>
>> If I rely on "proto" I get the protocol-name where the route comes from.
>> That is not what I want.
>>
>> *protocol bgp *'peer-neo' {
>>>       ipv4 { export filter *filter_common_ipv4_out*; };
>>> }
>>> *filter  * filter_common_ipv4_out() {
>>>       if  proto  = 'peer-neo' then .....;
>>> }
>>
>>
>> How can I match for 'peer-neo' ?
>>
>> Thank you.
>> Michael.
>>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20200408/e831a5fd/attachment.htm>