perhaps you should add two new constants:
1) target_proto
2) source_proto (same as proto + proto for compatibility)
We do filtering on VLANs so perhaps it is also possible to expose the
target_interface where the socket is bound to?
So we can simply match on *if target_interface = "eth1.2220"*
Aaahh now i see...
Currently I do pattern matching... Sorry.
function is_filtered_proto_in ( string p )
> {
> return false;
> }
> function is_filtered_proto_out ( string p )
> {
> if p ~ "*2220" then
> {
> bgp_community.add((65000,11120));
>
I say that there is no support for such a thing yet but I may be able to
provide you with a patch (we want to add it to the filter language).
Maria
On April 8, 2020 7:58:41 PM GMT+02:00, Michael Rack wrote:
>Can you explain what you mean?
>
>How should I change my scripts?
>
>I think it will be
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" *)*; };
> }
> *functio
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 wrote:
>Hi Guys,
>
>if i am in the EXPORT-Routine, how can i access the "protocol-name" of
>that
>instance
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_co
Okay, I will update all my hosts to the current version.
Thank you.
Am Mi., 8. Apr. 2020 um 18:28 Uhr schrieb Ondrej Zajicek <
santi...@crfreenet.org>:
> On Wed, Apr 08, 2020 at 05:36:28PM +0200, Michael Rack wrote:
> > Yeah i am doing so
> >
> > 1) birdcl configure
> > 2) birdcl reload out "
On Wed, Apr 08, 2020 at 05:36:28PM +0200, Michael Rack wrote:
> Yeah i am doing so
>
> 1) birdcl configure
> 2) birdcl reload out "'edge-at-sbg-v4-2221'"
>
> because i do not know if the "configure" knows what was changed.
> Or will configure always sync all routes also when they are not affe
Yeah i am doing so
1) birdcl configure
2) birdcl reload out "'edge-at-sbg-v4-2221'"
because i do not know if the "configure" knows what was changed.
Or will configure always sync all routes also when they are not affected by
the changes?
In my current Setup, I am not able to add a bgp-commun
I'm pretty sure you should be using just birdc configure to re-read the
config and apply it without dropping connections.
On 4/8/20 6:10 PM, Michael Rack wrote:
Hi Guys,
I run v2.0.2 of BIRD-Daemon. If i change something on the filters i
try to reload my changes with /birdcl reload out
"'edg
Hi Guys,
I run v2.0.2 of BIRD-Daemon. If i change something on the filters i try to
reload my changes with *birdcl reload out "'edge-at-sbg-v4-2221'**"* but
the changes do not go into effect.
*All what i see in debug-mode:*
2020-04-08 15:05:24.163 Reloading protocol edge-at-sbg-v4-2221
> 2020-0
Good evening,
I have this kind of bird.conf:
https://pastebin.com/6pMkJFix
I understand that in the Pipe protocol I need the 'import' clause to import
in master table routes learn by BGP. But I don't understand why in the Pipe
protocol in combination with BGP is useful to have the 'export' clause
12 matches
Mail list logo
