| Age | Commit message (Collapse) | Author |
|---|
|
OK norby@
|
|
ok claudio@
|
|
packets comming from the net are looped through the RDE and may get
delayed because of this. The result is that the neighbor FSM ends in
state FULL instead of LOADING and so the LSDB is not correctly
synchronized. Issue found by norby@ OK norby@
|
|
one of the worst documented parts of the RFC.
The initial packet sent by the slave may have no flags set. Don't
enforce that the M bit is set but instead check that the I bit and
MS bit are unset.
The master should only issue NBR_EVT_XCHNG_DONE if it has sent at
least one packet with M bit cleared else the slave may get stuck
in state Exchange.
In NBR_STA_LOAD the db_tx_timer() still needs to send db descriptions
out. This will be the last packet sent with the cleared M bit.
|
|
|
|
do with this software, just happend to be my only valid email address at
the time.
|
|
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@
|
