ouroboros/src/ipcpd/normal/ribmgr.h, branch 0.3Ouroboros main repositoryhttp://www.ouroboros.rocks/cgit/ouroboros/atom?h=0.32016-10-22T11:27:02Zbuild: Compile with strict conversion2016-10-22T11:27:02Zdimitri staessensdimitri.staessens@intec.ugent.be2016-10-21T18:13:41Zurn:sha1:3cafbf3cfe5c58a6988dbfc4c29148ebb804f5c2
This has the code checked with -Wcast-qual and -Wconversion flags.
These flags were removed because SWIG generated code fails.
ipcpd: normal: Improve upon the internal design2016-10-12T12:54:18ZSander Vrijderssander.vrijders@intec.ugent.be2016-10-12T12:54:18Zurn:sha1:43e2f332770007a3fcea011ffb35e8fbb24a6205
This commit will remove the RMT component from the normal IPCP, as
some of its functionality would else be duplicated in the FMGR. Now
all reading from flows, either N-1 or N+1 is done in the FMGR, then
either passed to the FRCT or a lookup is performed in the PFF (not
there yet) and the PDU is forwarded.
ipcpd: normal: First version of the fast path bootstrap2016-10-11T14:15:33ZSander Vrijderssander.vrijders@intec.ugent.be2016-10-08T17:42:51Zurn:sha1:69ef99bb2dc05337e8189acc42dc9122f4182ead
This is the first version of the fast path bootstrap in the normal
IPCP. It sets up a connection with the other end, and creates the
appropriate data structures. N+1 and N-1 SDUs are read and written and
passed through the right components.
ipcpd: normal: Allow initiating enrollment2016-08-01T09:12:14ZSander Vrijderssander.vrijders@intec.ugent.be2016-07-28T15:23:42Zurn:sha1:cf719963be2e42026012e152ae49f4c764dd9b4f
This will add more functionality for enrolling two normal IPCPs with
each other. Some bugs were fixed in CDAP. Now on enrolling, an IPCP
will send a START message to the other IPCP. Next step is syncing the
RIBs.
ipcpd: normal: Establish N-1 management flows2016-07-14T14:52:54ZSander Vrijderssander.vrijders@intec.ugent.be2016-07-14T14:52:54Zurn:sha1:8d1951e463193c1aa213c4680f645ec7b9247e15
This adds the intial implementation of establishing management N-1
flows between normal IPCPs. On calling fmgr_mgmt_flow, a management
flow will be setup to a certain destination IPCP. After flow
allocation, the fd is handed to the RIB manager. The flow manager also
listens for incoming flow requests. In case they are management flows,
they are handed to the RIB manager, otherwise to the FRCT.
ipcpd: Add initial headers for the normal IPCP2016-07-12T15:51:45ZSander Vrijderssander.vrijders@intec.ugent.be2016-07-12T13:45:47Zurn:sha1:d96bac100c5fe181383e947c1e62241cbabce6ac
This adds the initial headers for the normal IPCP. The normal IPCP
consists of 3 main components:
* The flow manager, in charge of managing N and N-1 flows.
* The RIB manager, in charge of managing the RIB
* FRCT: The flow and retransmission control task