[Bug 235969] net/frr6: integrated-vtysh-config not honored by rc file
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Feb 23 20:25:23 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235969
Bug ID: 235969
Summary: net/frr6: integrated-vtysh-config not honored by rc
file
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: olivier at freebsd.org
Reporter: yman at protonmail.ch
Flags: maintainer-feedback?(olivier at freebsd.org)
Assignee: olivier at freebsd.org
Created attachment 202299
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=202299&action=edit
frr.in.patch
Problem
When using 'integrated-vtysh-config' mode with frr.conf (frr_vtysh_boot rc
flag), but without any daemon specific config files (e.g. ospfd.conf) all
daemons failed to start. Then 'vtysh -b' failed to apply config to daemons.
Steps to reproduce on 12.0:
* install frr6
* create /usr/local/etc/frr/vtysh.conf with
- service integrated-vtysh-config
- hostname router
- username root nopassword
* create empty /usr/local/etc/frr/frr.conf
* put any daemons in /etc/rc.conf options with frr_vtysh_boot, like
- frr_enable="YES"
- frr_daemons="zebra ospfd bgpd"
- frr_vtysh_boot="YES"
* start frr service
Result
No daemons running, service didn't start.
Expected result
All chosen daemons running, service started.
Some explanation
In 'integrated-vtysh-config' mode vtysh utility controls that all daemons has
config they need, while serving it from single config file (frr.conf), not
daemon specific configs. vtysh also controls config writing. Daemons on startup
locate frr.conf file and don't tries to load they own config. 'vtysh -b' runs
last and apply configuration to daemons.
While there's a 'frr_vtysh_boot' flag in rc file for that exact reason, startup
procedures still require all daemons have they own configs. If there are no
daemon specific configs, that daemon will not be executed at all.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list