Hi!
I've just upgraded to OPNsense 18.1.r1-amd64. Every thing is working OK except the FRR Service that does not appear in the widget (image attached). However, it's working ok, doing what is supposed to do.
Could you please take a look?
Thanks in advance,
Hi odites999,
A copy+paste fail indeed, thanks for your report!
Fixed via: https://github.com/opnsense/plugins/commit/7bc1c2088
You can try this by patching your system:
# opnsense-patch -c plugins 7bc1c2088
Cheers,
Franco
I am sorry it was my fault. It seems like I forgot about that when I did the migration from quagga. I am sorry for this inconvenience. The patch Franco created will be installed automatically with the next release if you don't patch it by yourself.
Thanks for the quick fix. Patch installed and working OK. Great work guys!!
Cheers,
Hello!
After the 18.1 update, the widget problem has appeared again. FRR is not started at boot.
Cheers,
Er... we fixed the service probing, not the startup (if that was indeed an issue it was not handled as such).
"However, it's working ok, doing what is supposed to do." seemed to reinforce that assumption.
Cheers,
Franco
Yes it does its job, once you have manually started the service, not before. Probably I did not explain it very well. Sorry. In my case, RIP routing is used by TV Service so I must start the service to be able to watch TV.
Cheers,
Okay, hopefully Fabian can take a look and fix it in the next iteration. Thanks for explaining. :)
Cheers,
Franco
@fichtner - the plugin seems to create the correct config because "service frr start" starts it without issues. This means there is probably some trouble with booting the device since it should be started by rc.d.
If I can help you to identify the problem, just tell me.
We have a workaround in place... it should hit 18.1.3.
https://github.com/opnsense/plugins/commit/f26a704f9
Cheers,
Franco
I have applied the patch (opnsense-patch -c plugins f26a704f9) but the problem is still there... no automatic start of FRR after rebooting the system.
Cheers,
I don't know if it patches ok. Locally it worked. If not it would probably be beneficial if somebody started looking into why the service fails who has a proper setup. I don't believe there is no clever person around to find and fix this over the course of a month.
Cheers,
Franco
The patch is just missing a chmod 755, then it's working ;)
chmod 755 /usr/local/etc/rc.syshook.d/50-frr.start
chmod in opnsense-patch worked for core, but not for plugins...
https://github.com/opnsense/update/commit/f5f37da5
The problem has been solved. Thanks to everyone. :)
Cheers!