Reloading static/direct/device/kernel protocols via birdc fails
Hi, When I am attempting to reload kernel, static, direct or device protocol via birdc, I always get message like this "krt_main: reload failed", while in the log file I see just reloading message: <INFO> Reloading protocol krt_main For pipe, bgp and ospf instances there is only "reloading" message. Is this a bug, feature or something else? PS: I need reload to force bird to rescan specific kernel table. Thank you! -- With best regards, Alexander.
On Wed, Aug 20, 2014 at 01:03:12PM +0200, Alexander Demenshin wrote:
Hi,
When I am attempting to reload kernel, static, direct or device protocol via birdc, I always get message like this "krt_main: reload failed", while in the log file I see just reloading message:
<INFO> Reloading protocol krt_main
For pipe, bgp and ospf instances there is only "reloading" message.
Is this a bug, feature or something else?
Hi Reload operation is not implemented in kernel protocol, you have to restart it. -- 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."
Hi, On 2014-08-22 12:01, Ondrej Zajicek wrote:
Reload operation is not implemented in kernel protocol, you have to restart it.
OK, thank you. But this has implications - when restarting, it will remove all existing routes from anywhere else (BGP, OSPF etc) for a short time, but it might be sufficient to disrupt communication (or even reset some of them). It would be nice to implement "reload" in a way that it will force rescan of routes/devices, this should be very easy to do. Thank you!
participants (2)
-
Alexander Demenshin -
Ondrej Zajicek