Ouroboros main repository http://www.ouroboros.rocks/cgit/ouroboros/atom?h=0.4 2017-02-08T17:04:13Z 2017-02-08T17:04:13Z dimitri staessens dimitri.staessens@intec.ugent.be 2017-02-08T16:09:55Z urn:sha1:742d01a4f9a32f17561104ee7da8971c1bcdd703 This removes the logfile and outputs log messages to the logging system. The creation of the logfiles (as well as the ap_init() call) were moved into ipcp_init() to simplify the IPCP creation and shutdown. Fixes #25 Fixes #27 2017-02-07T20:00:45Z dimitri staessens dimitri.staessens@intec.ugent.be 2017-02-07T19:45:14Z urn:sha1:bfb86b66c8e7d9d8dc45d9075a4db6d10931dccf The ipcp-ops header was removed and merged into ipcp.h. The common components dif_name and ipcp_type have been moved to the main ipcp struct. After this move, ipcp_data only contained shim information, so it was renamed to shim_data. The ipcp_init() function checks the type and will only include the shim_data if the type is not an IPCP_NORMAL. All ipcps have been adapted to this change in API. 2017-02-06T19:04:34Z dimitri staessens dimitri.staessens@intec.ugent.be 2017-02-06T15:05:44Z urn:sha1:373efaf24d3600fe4dadf6bfaaee8d19e2ec32d7 This PR updates the normal IPCP to use the new RIB. The old ribmgr is removed and replaced by a stub that needs to be implemented. All components (dir, fmgr, frct) were adapted to the new RIB API. A lot of functionality was moved outside of the ribmgr, such as the addr_auth, which is now a component of the IPCP. The address is also stored to the ipcpi struct. The irm tool has an option to set the gam policy of the rib manager. 2017-01-09T10:23:48Z Sander Vrijders sander.vrijders@intec.ugent.be 2017-01-08T10:14:43Z urn:sha1:0a071a42d4e80f54e92f34911cafda3d666d35d5 This allows IPCPs to bind a name, so that they can announce their name to neighbors which can then allocate a flow to them. Registering of the name happens by an administrator. It also moves the irmd_api to common ground, since it is used by all IPCPs. 2017-01-04T14:59:41Z dimitri staessens dimitri.staessens@intec.ugent.be 2017-01-04T14:25:15Z urn:sha1:4384cd203a958373cf0ab959afb688f9eeba05fc These operations separe the starting and joining of the main ipcp threads into ipcp_boot() and ipcp_shutdown() operations. This allows the proper cleanup of user data and user threads after the IPCP is requested to shut down. 2017-01-04T10:18:24Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-12-30T08:15:39Z urn:sha1:f3fbf2c6093b293f995c4d784509577695e052b1 Reorganizes the normal IPCP a bit to make sure internal components do not need to access the state of the IPCP. The IPCP has now a thread calling accept and delegating it to the correct component based on the AE name (this used to be in the fmgr). Internal components are initialized upon enrollment or bootstrap of the IPCP. If a step fails, the IPCP goes back to the INIT state, if all components boot correctly, it goes to the operational state. RIB synchronization is still done by sending a CDAP start/stop and syncing with a ribmgr state, but needs revision later on. 2016-12-27T20:51:58Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-12-27T20:36:52Z urn:sha1:dbd901e65371ae390c36e7f6ed4a8bf59db6a5f6 Since the mainloop threadpool is created on ipcp_init and all threads waited for on ipcp_fini, there is no need for it to be accessible from elsewhere. 2016-12-24T12:50:00Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-12-24T00:59:42Z urn:sha1:2fe765020769c8eb06ca410b7e289f37508d5efc This corrects the license statements on all files. Installed headers are LGPLv2.1, the rest of the code is GPLv2. 2016-12-06T13:01:32Z Sander Vrijders sander.vrijders@intec.ugent.be 2016-12-06T13:01:32Z urn:sha1:38de1fd9af5a46c18ce5523b0c48e5f1c8679099 Changes a state of the IPCP to a more correct terminology. 2016-11-30T14:34:04Z Sander Vrijders sander.vrijders@intec.ugent.be 2016-11-30T14:34:04Z urn:sha1:8e0165c2ee9659ee57934947369659c093db621e This will split the IPCP state PENDING_ENROL into IPCP_CONFIG and IPCP_BOOTING. IPCP_CONFIG is concerned only with configuring the IPCP with the bare essence. When in IPCP_BOOTING, the IPCP will complete its configuration by starting its policies, and thus making the IPCP completely functioning.