Solaris 10 Quagga Packages.
---------------------------

These are beta packages of Quagga for Solaris, with SMF support. 

 These packages were compiled for Solaris 10 and will attempt to install SMF
specific files, however the binaries themselves may (or may not) work on
Solaris 8 and 9. 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-gcc-rdynamic --enable-opaque-lsa --enable-ospf-te
--enable-multipath=64 --enable-user=quagga --enable-ospf-te
--enable-ospfclient=yes --enable-ospfapi=yes  --enable-group=quagga
--enable-nssa --enable-opaque-lsa

This means that by default:

- 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, **before** installing the
  packages OR otherwise change Quagga/user and Quagga/group properties for
  each service after installing the packages and verify the ownership and
  permission on /var/run/quagga.

- The daemons will try create their UNIX sockets in /var/run/quagga. This
  directory does not exist per default on Solaris, but will be created by
  the package.

  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 packages will
  take care of this provided the appropriate user/group existed on the
  system.

- 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). See the
  'Quagga/config_file' SMF property for each service instance on how to
  configure this.

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.