Return to RELEASE.NOTES CVS log

Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / pimdd

Annotation of embedaddon/pimdd/RELEASE.NOTES, revision 1.1.1.1

1.1       misho       1: Second Pre-release December 31, 1998 (Happy New Year)
                      2: 
                      3: * Fixed a variety of bugs and updated the implementation to comply
                      4:   with some sublte points and revisions of the PIM-DM specification.
                      5: 
                      6: * Also synch'ed with the latest pimd from Pavlin and added patches
                      7:   for Linux, which were contributed by Jonathan Day <j.c.day@larc.nasa.gov>.
                      8:   Thanks Jonathan.
                      9: 
                     10: 
                     11: First Pre-release June 5, 1997
                     12: 
                     13: * Pimd-dense requires kernel patches to the current ip_mroute kernel 
                     14:   in order to operate correctly.  This is due to bugs in the ipmroute
                     15:   kernel code currently being distributed (at least for FreeBSD).
                     16:   I've tested pimdd with both Rusty's GateD patches (to be depricated)
                     17:   and Pavlin's combined patches, which are available at:
                     18:     ftp://catarina.usc.edu/pub/pim/pimd/experimental/one-pimd-gated-kernel
                     19:   It should also work with any of the other recent patch kits that Pavlin
                     20:   has produced for use with Sparse-mode pimd.
                     21: 
                     22: * Since pimd cannot reliably get preference and metric info from the kernel
                     23:   a configuration option is provided to specify a preference with which to
                     24:   advertise sources when sending PIM-Assert messages.  The phyint command
                     25:   in pimd.conf allows you to specify a default perference for each
                     26:   interface.  If no preference is specified, prefs will default to 101, 
                     27:   which is high enough that default preferences advertised by either
                     28:   Cisco or Gated routers (both having better information on unicast routes)
                     29:   will will over pimd preferences.  Directly connected sources will always
                     30:   be asserted with a preference of 0.
                     31: 
                     32: * Because unicast routes are obtained from the kernel, only the prefered
                     33:   route is available.  Pimd cannot determine the existence of 
                     34:   equal-cost-multipaths, and thus does not implement the addressing of
                     35:   joins and prunes to 0.0.0.0.
                     36: 
                     37: * RSRR support is currently rough and completely untested.
                     38: 
                     39: 
                     40: 
                     41: