Thanks Quentin. Currently on vacation. I'll run some variations through strace and report any issues. On Mon, 19 Aug 2019, 16:05 Quentin Young, <qlyoung@cumulusnetworks.com> wrote:
~/frr> ./configure --help | grep sysconf --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
Setting this to /usr/local/etc should do it. In case you want to do this at runtime we also have the --pathspace option, docs for that are in the manpages:
https://github.com/FRRouting/frr/blob/master/doc/manpages/common-options.rst...
Quentin
On Aug 19, 2019, at 9:28 AM, Phil Wiggins <phil.wiggins@gmail.com> wrote:
Is it possible to relocate /etc/frr to use another location such as /usr/local/etc/frr? It's important to us for virtualization where the virtual routers (virtual_file_system:/usr/local/etc/frr) can't conflict with the host (/etc/frr); otherwise, we get multiple virtual routers trying to use host_file_system:/etc/frr concurrently which doesn't end well.
Is there something that I can add/change to the build script? https://gist.github.com/apwiggins/44f3592a61965783372aea5881ed9f7a [snip] ./bootstrap.sh ./configure \ --prefix=/usr/local \ --enable-exampledir=/usr/share/doc/frr/examples/ \ --localstatedir=/var/run/frr \ --sbindir=/usr/lib/frr \ --sysconfdir=/usr/local/etc/frr \ --enable-pimd \ --enable-watchfrr \ --enable-ospfclient=yes \ --enable-ospfapi=yes \ --disable-ospf6d \ --enable-multipath=64 \ --enable-user=root \ --enable-group=root \ --enable-vty-group=frrvty \ --enable-configfile-mask=0640 \ --enable-logfile-mask=0640 \ --enable-rtadv \ --enable-fpm \ --enable-systemd=yes \ --with-pkg-git-version \ --with-pkg-extra-version=-ITNFRR [/snip]
Cheers,
Phil
On Thu, 21 Jun 2018 at 08:44, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Phil -
This is cool, thanks for taking the time for figuring this out and for posting the results to this alias for future people to find! Let us know if you need anything.
thanks!
donald
On Fri, Jun 15, 2018 at 1:37 PM, Phil Wiggins <phil.wiggins@gmail.com> wrote:
If anyone is interested in running FRR in the NRL CORE emulation environment, I have some build scripts for FRR on CORE that I posted at the first link below. Normally CORE runs Quagga, so this script was a hack to shoehorn FRR as a Quagga replacement. These scripts are not part of CORE yet, so are unsupported. People on this list may want to use CORE for FRR experimentation and testing, so you can customize these scripts to suit your own needs.
It's best to run this stuff in a VM with no internet connection (after installation) since CORE runs lots of processes as root - a well-known security issue.
https://github.com/coreemu/core/issues/170
( install_frr_for_core.sh) FRR on NRL CORE build script - assumes Ubuntu 16.04.4 clean installation in a VM or physical host: https://gist.github.com/apwiggins/44f3592a61965783372aea5881ed9f7a
(core_misc_frr.py ) used by the install script above to install at ./core/misc/frr.py https://gist.github.com/apwiggins/d610c2794c8c0a12a45bfc093fd2e949
(core_services_frr.py) used by the install script above to install at ./core/services/frr.py https://gist.github.com/apwiggins/747a9a14feff2ce3a3b8760406b825a7
https://www.nrl.navy.mil/itd/ncs/products/core The Common Open Research Emulator (CORE) is a tool for emulating networks on one or more machines. You can connect these emulated networks to live networks. CORE consists of a GUI for drawing topologies of lightweight virtual machines, and Python modules for scripting network emulation.
Cheers,
Phil
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev