ouroboros - Ouroboros main repository

	Commit message (Collapse)	Author	Age	Files	Lines
*	ipcpd: normal: Add RIB objects	Sander Vrijders	2016-11-15	1	-4/+0
\| \| \| \| \|	This adds the ability to create/update/destroy RIB objects. Syncing with other DIF members is not yet supported.
*	ipcpd: normal: Add policy for obtaining a flat address	Sander Vrijders	2016-11-01	1	-1/+2
\| \| \| \| \| \|	This adds a policy for obtaining a flat address, and thus also the infrastructure for policies in the IPCP. The IPCP should check if the address is available; this is currently not there yet.
*	build: Compile with strict conversion	dimitri staessens	2016-10-22	1	-4/+7
\| \| \| \| \|	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 design	Sander Vrijders	2016-10-12	1	-0/+5
\| \| \| \| \| \| \| \|	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 bootstrap	Sander Vrijders	2016-10-11	1	-5/+9
\| \| \| \| \| \| \|	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 enrollment	Sander Vrijders	2016-08-01	1	-4/+3
\| \| \| \| \| \| \|	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 flows	Sander Vrijders	2016-07-14	1	-5/+7
\| \| \| \| \| \| \| \| \|	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 IPCP	Sander Vrijders	2016-07-12	1	-0/+35
	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