Fwd: Re: Changing Filters and "reload out" will not work // Version 2.0.2
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 "'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 <INFO> Reloading protocol edge-at-sbg-v4-2221 2020-04-08 15:05:24.163 <DBG> Assertion 'c->channel_state == CS_UP' failed at nest/proto.c:405
Is there anyone out there that can help, what is going wrong here?
Thank you. Michael.
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-community when the proto-name matches ~ "*2221". *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)); } if p = "edge-at-sbg-v4-2221" then { *bgp_community.add*((65000,11050)); } return false; }
When i run *birdcl s r export "'edge-de-fre-v4-2220'" all *i can not see the community added to the exported route. Also on the remote machine, there are no communities at all on received routes. Do I miss anything? *PS: *i added a debug-print and this will be logged
*2020-04-08 15:18:57.742 <INFO> matched ~ in is_filtered_proto_out(): edge-de-fre-v6-2220*
so i reach the IF-Statement and it is matching the conditions. Am Mi., 8. Apr. 2020 um 17:20 Uhr schrieb Vasil Bakalov <me@keksbg.dev>:
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 "'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 <INFO> Reloading protocol edge-at-sbg-v4-2221
2020-04-08 15:05:24.163 <DBG> Assertion 'c->channel_state == CS_UP' failed at nest/proto.c:405
Is there anyone out there that can help, what is going wrong here?
Thank you. Michael.
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 affected by the changes?
Note that version 2.0.2 is pretty old and we have several bugs in reconfiguration code. I would suggest to upgrade to latest version. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
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 < santiago@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 "'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?
Note that version 2.0.2 is pretty old and we have several bugs in reconfiguration code. I would suggest to upgrade to latest version.
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (3)
-
Michael Rack -
Ondrej Zajicek -
Vasil Bakalov