Contributed by grey on from the keeping the routing daemons coming dept.
Router manufacturers and buggy software writers of the world beware, yet another BSD-licensed piece of the puzzle to the OpenBSD master plan has been committed to the src tree.
Below is the commit message with a detailed introduction:
CVSROOT: /cvs Module name: src Changes by: firstname.lastname@example.org 2005/01/28 07:05:41 Added files: usr.sbin/ospfd : Makefile area.c auth.c buffer.c config.c control.c control.h database.c hello.c imsg.c in_cksum.c interface.c iso_cksum.c kroute.c log.c log.h lsack.c lsreq.c lsupdate.c neighbor.c ospf.h ospfd.8 ospfd.c ospfd.h ospfe.c ospfe.h packet.c parse.y rde.c rde.h rde_lsdb.c Log message: Welcome ospfd started by Esben Norby some time ago by using the imsg/three process framework of bgpd. He implemented the basic concept plus the ospf finite state machines. Later I joined and helped him cleanup, debug and extend his work. Right now it is not particularly useful, major parts are still missing but is imported to allow more people to work on it. status: The basic protocol works for broadcast networks and the LS database is synchronized and updated. It is not possible to be DR or BDR on a network and other interface types like point-to-point are not yet supported. The shortest path tree is not calculated and so no routing information is exchanged with the kernel FIB. Not yet connected to the builds. OK henning@
Additionally, Claudio Jeker has let us know about some ideas still in the works:
Here is a small list of planned stuff that will make ospfd cool:
- support for aliased networks (cisco only supports the main interface network whereas on zebra/quagga it is possible to use all defined networks)
- carp(4) support (originating networks dependant on the carp if status)
- interface groups for tamplating dynamic interfaces like tun(4) or pppoe(4)
(Comments are closed)