Solaris binaries.
-----------------

These are binaries of Quagga for Solaris, presented as a very rough package.
Solaris 10 is the primary supported version, however Solaris 9 and 8 should
work too. Please read all of the notes below before attempting to use these
binaries.

These binaries were built with gcc with the following configure options:

./configure --prefix=/usr/local/quagga/ --localstatedir=/var/run/quagga
--enable-ipv6 --enable-multipath=64 --enable-nssa --enable-opaque-lsa
--enable-ospf-te  --enable-ospfclient=yes --enable-ospfapi=yes
--with-libpam --enable-user=quagga --enable-group=quagga

This means that by default:

- If you untar the package in /, the files will unpack to /usr/local/quagga

- The daemons require /usr/local/quagga/lib/ to be in the library path, you
  may need to set LD_LIBRARY_PATH.

- The daemons will try switch credentials to the 'quagga' user and group.
  These user and group IDs do not exist per default on Solaris, you will
  have to either create this user and group, or start the daemons with the
  -u root -g root arguments.

  (NB: the daemons must always be started as root, regardless.)

- The daemons will try create their UNIX sockets in /var/run/quagga. This
  directory does not exist per default on Solaris, you will have to create
  it and it must be writable to the user the daemons will effectively run
  as, eg if you created a quagga user and run the daemons as such, then
  /var/run/quagga should be owned by quagga and mode 0611.

- The daemons look to /usr/local/quagga/etc/<name>.conf for their config
  file (which must be readable to the user the daemon is run as).

Further notes:

- zebra does not yet support alias address interfaces on Solaris. Do not
  expect zebra to correctly function if you have alias interfaces
  configured. As a work around, one can plumb 'vni' interfaces and use these
  for alias addresses, one vniX interface per address. As vni interfaces are
  specific to S10, this workaround is specific to S10 too - alias interfaces
  hence are not supported by zebra on Solaris 9 or earlier. This will
  hopefully be remedied in a future release of Quagga.

- These binaries are not supported by Sun Microsystems in any way. Please
  use the normal Quagga channels for support and/or bug reports. However
  Sun Microsystems would be interested to receive feedback from customers on
  their experiences with Quagga.

- These binaries were not compiled with vtysh, to avoid having it depend on
  readline. If you have a readline development environment, you can compile
  vtysh from the Quagga sources, using the above configure options, and it
  should work. You can of course use the telnet accessible interfaces.

- It is recommended you use the -A argument to daemons to restrict which
  addresses the daemons have their telnet CLI listen to.

- It is recommended you take the required actions to allow the daemons to
  switch to a non-root user, rather than simply pass the -u root -g root
  argument to daemons to avoid permissions problems. 

- Further integration of Quagga with Solaris 10 remains to be done, and
  future binaries may not integrate in the same way - eg, they may be launched
  from SMF, they may not require a Quagga user, etc.. caveat emptor. This 
  integration remains to be done.