Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
Quagga
Edit
PageHistory
Diff
Info
LikePages
Quagga is a fork of the [Zebra] routing daemon. Quagga originally consisted of the -pj patchset to Zebra, and was created because of a difference in beliefs between the Quagga developers (Faster development == more features, and faster bug finding and fixing) and the Zebra developers (Stable development). A lot of people tend to use Quagga these days when they need a Linux machine to participate in a routing network. Quagga's growth in the last year or so has been huge, seeing development of many new features as well as a lot of code cleanups. A Quagga is a now extinct creature that is closely related to a Zebra. ---- !!Configuration These notes are for observations on Debian Sarge. Quagga uses the files in <tt>/etc/quagga/</tt>. By default, there is only a <tt>daemons</tt> file and a <tt>debian.conf</tt> file. You MUST enable ''zebra=yes'' in the <tt>daemons</tt> file if you want any routes to be actually used! I wanted to use [BGP], so I copied my old <tt>bgpd.conf</tt> from zebra, changed the log file entry in it from <tt>/var/log/zebra/bgpd.log</tt> to <tt>/var/log/quagga/bgpd.log</tt> and made the file readable by the quagga group (since quagga has its own user and group in Debian). I also had to enable ''bgpd=yes'' in the <tt>daemons</tt> file. Read the notes in the <tt>daemons</tt> file for the necessary file permissions on the *.conf files. In practice, it will work with just __quagga__ group read permissions, but the __quagga__ user needs to be able to write to the file if you want to be able to save configs. When you use the <tt>vtysh</tt> program, it wants your user's normal login password, not a configured quagga password or anything. You can create (and configure) an <tt>/etc/quagga/vtysh.conf</tt> file, and give a <pre> <tt>log file /var/log/quagga/vtysh.log</tt> </pre> entry. Note that the <tt>username ''user password''</tt> given in the example config file doesn't seem to do anything. I think you need to have have "<tt>line vty</tt>" entries in each daemon's config file. There are example files in <tt>/usr/share/doc/quagga/examples</tt>. ---- !!Notes ! interface tewh:192.168.70.114: ospf_read authentication type mismatch. You have an md5 vs no auth on your link. check your configuration for typos ! How vtysh works <pre> 18:27 <@mattb> telnet localhost 2601 will take you to zebra 18:28 <@mattb> telnet 2605 18:28 <@mattb> will take you to bgpd 18:28 <@mattb> vtysh will take you to Quagga's integrated shell 18:28 <@mattb> which combines the interface of zebra and whatever other quagga daemons you have running 18:29 < Remosi> I think you've gotta admit 18:29 < Remosi> that part of quagga is rather uh quirky 18:29 <@mattb> I quite like vtysh 18:29 <@mattb> the telneting into a particular port for a particular daemon bit 18:29 <@mattb> is a bit quirky 18:29 < Remosi> yeah 18:29 < Remosi> vtysh isn't too bad </pre>
2 pages link to
Quagga
:
LinuxNetlinkSockets
ZebraConfig
