* What is frr?
=================
-http://www.freerangerouting.net/
-> Frr is a routing software suite, providing implementations of OSPFv2,
-> OSPFv3, RIP v1 and v2, RIPv3 and BGPv4 for Unix platforms, particularly
-> FreeBSD and Linux and also NetBSD, to mention a few. Frr is a fork of GNU
-> Zebra which was developed by Kunihiro Ishiguro. Development of GNU Zebra
-> slowed dramatically to the point where eventually GNU Zebra was forked into
-> Frr.
-
-> The Frr tree is an attempt to provide a zebra tree with at least the
-> bug-fixes, which have accumulated, applied, while tracking any significant
-> changes made to the zebra.org tree. Ultimately, this tree hopes to revitalise
-> development of this code base.
-
-I packaged zebra-pj which was then renamed to frr to get people used to it
-and offer Debian users the choice which versions they like to use. I hope this
-brings frr some feedback and helps it evolving to a good successor of the
-orphaned zebra.
-
- -- Christian Hammers <ch@debian.org>, Jul/Aug 2003
+http://www.frrouting.org/
+FRR is a routing software suite, providing implementations of OSPFv2,
+OSPFv3, RIP v1 and v2, RIPng, ISIS, PIM, BGP and LDP for Unix platforms, particularly
+FreeBSD and Linux and also NetBSD, to mention a few. FRR is a fork of Quagga
+which itself is a fork of Zebra.
+Zebra was developed by Kunihiro Ishiguro.
* Why has SNMP support been disabled?
=====================================
-Frr used to link against the NetSNMP libraries to provide SNMP
+FRR used to link against the NetSNMP libraries to provide SNMP
support. Those libraries sadly link against the OpenSSL libraries
to provide crypto support for SNMPv3 among others.
OpenSSL now is not compatible with the GNU GENERAL PUBLIC LICENSE (GPL)
-licence that Frr is distributed under. For more explanation read:
+licence that FRR is distributed under. For more explanation read:
http://www.gnome.org/~markmc/openssl-and-the-gpl.html
http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs
Updating the licence to explecitly allow linking against OpenSSL
would requite the affirmation of all people that ever contributed
-a significant part to Zebra or Frr and thus are the collective
+a significant part to Zebra / Quagga or FRR and thus are the collective
"copyright holder". That's too much work. Using a shrinked down
version of NetSNMP without OpenSSL or convincing the NetSNMP people
to change to GnuTLS are maybe good solutions but not reachable
*BUT*
It is allowed by the used licence mix that you fetch the sources and
-build Frr yourself with SNMP with
+build FRR yourself with SNMP with
<remove the "grep ^smux" block at the end of debian/frr.preinst>
# export WANT_SNMP=1
# apt-get -b source frr
system's routing table if not set up properly.
Priorities were suggested by Dancer <dancer@zeor.simegen.com>.
-They're used to start the Frr daemons in more than one step
+They're used to start the FRR daemons in more than one step
(for example start one or two at network initialization and the
-rest later). The number of Frr daemons being small, priorities
+rest later). The number of FRR daemons being small, priorities
must be between 1 and 9, inclusive (or the initscript has to be
changed). /etc/init.d/frr then can be started as
=====================================================================
If this message occurs the receive buffer should be increased by adding the
-following to /etc/sysctl.conf and "--nl-bufsize" to /etc/frr/debian.conf.
+following to /etc/sysctl.conf and "--nl-bufsize" to /etc/frr/daemons.conf.
> net.core.rmem_default = 262144
> net.core.rmem_max = 262144
-See message #4525 from 2005-05-09 in the frr-users mailing list.
+See message #4525 from 2005-05-09 in the quagga-users mailing list.
* vtysh immediately exists:
===========================
Check /etc/pam.d/frr, it probably denies access to your user. The passwords
-configured in /etc/frr/Frr.conf are only for telnet access.
+configured in /etc/frr/frr.conf are only for telnet access.
projects / mirror_frr.git / blobdiff