| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |\ \ \ \
| | |/ / /
| |/| / /
| | |/ / |
Be fixes
|
| | | | |
|
| |/ / |
|
| |\ \
| | | |
| | | |
| | | | |
ipcpd: normal: Add Flow State Objects to RIB
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
This makes the routing component create a Flow State Database
(FSDB). An FSDB contains Flow State Objects (FSOs). An FSO is created
when a neighbor is added, it is deleted when a neighbor is removed and
its QoS is updated when a neighbor's QoS changes.
|
| |\ \
| | | |
| | | |
| | | | |
lib: Fix typo in cdap
|
| |/ / |
|
| |\ \
| | | |
| | | |
| | | | |
lib: Manage multiple flows with a single CDAP instance
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
You can now add multiple flows to a CDAP instance. This will simplify
sending messages to different peers (e.g. for syncing the RIB). A
request will now return an array of keys terminated by
CDAP_KEY_INVALID. Removes the enum from the CDAP proto file to just
take the opcode as an integer.
|
| |\ \
| | | |
| | | |
| | | | |
Be cdap flow
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Our mailserver was migrated from intec.ugent.be to the central
ugent.be emailserver. This PR updates the header files to reflect this
change as well. Some header files were also homogenized if the
parameters within the functions were badly aligned.
|
| | | |
| | | |
| | | |
| | | | |
The CMakeLists files are now properly indented.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
cacep.h was not installed on install, but other applications may want
to use it as well.
|
| |/ /
| | |
| | |
| | | |
This removes the CDAP flow class, which is no longer needed.
|
| |\ \
| | | |
| | | |
| | | | |
ipcpd: normal: Refactor application entities and add neighbors struct
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This refactors the different Application Entities of the normal
IPCP. They all listen to and use the connection manager to establish
new application connections.
This commit also adds a neighbors struct to the normal IPCP. It
contains neighbor structs that contain application
connection. Notifiers can be registered in case a neighbor changes
(added, removed, QoS changed).
The flow manager has an instance of this neighbors struct and listens
to these events to update its flow set. The routing component also
listens to these events so that it can update the FSDB if needed. The
flow manager now also creates the PFF instances and the routing
instances per QoS cube.
The RIB manager also uses this an instance of the neighbors struct and
listens to neighbor events as well.
|
| |\ \
| | | |
| | | |
| | | | |
ipcpd: normal: Add connection manager
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
This adds the connection manager which allows the different AEs of the
normal IPCP to register with it. An AE can then use the connection
manager to allocate a flow to a neighbor, or to wait for a new
connection from a neighbor.
|
| |\ \
| | | |
| | | |
| | | | |
lib: Split CACEP into request/response protocol
|
| | | | |
|
| |\| |
| | | |
| | | |
| | | | |
lib: Split authentication from CACEP
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
By removing authentication as part of CACEP, all policies
disappear. CACEP becomes a policy-free connection establishment
protocol between Application Entities. Authentication can later be
added cleanly as a pure policy function when needed.
|
| |\ \
| | | |
| | | |
| | | | |
lib: Remove application entity name
|
| |/ /
| | |
| | |
| | |
| | | |
The AE name should not be passed over the layer boundaries. If an
application has more than one AE it should exchange this in CACEP.
|
| |\ \
| | | |
| | | |
| | | | |
lib: Revise CACEP API
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The information passed to CACEP is split between the information about
the connection and the information to be used during the
authentication exchange.
|
|\ \ \ \
| |/ / /
|/| | /
| | |/
| |/| |
|
| |\ \
| | | |
| | | |
| | | | |
irmd: Fix timeouts in reg_entry
|
| |/ /
| | |
| | |
| | |
| | | |
This fixes bad timedwaits for the state of the reg_entry. Also
slightly revised timedwaits throughout the prototype.
|
|\| |
| |/
|/| |
|
| |\
| | |
| | |
| | | |
irmd: Fix bug in name comparison of IPCPs
|
| |/ |
|
|\| |
|
| |\
| | |
| | |
| | | |
irmd: Check IPCP type before bootstrap
|
| | | |
|
| |/
| |
| |
| |
| | |
This prevents assertion failures in the IPCP in some cases. IPCPs can
now safely assert the type.
|
|\| |
|
| |\
| | |
| | |
| | | |
tools: Continue oping server after failed write
|
| | |
| | |
| | |
| | |
| | |
| | | |
When hammering the oping thread, it will have write fails when the
buffer gets full as its flow is non-blocking. It would stop and
deallocate the flow, but should just continue.
|
|\| | |
|
| |\|
| | |
| | |
| | | |
tools: Fix overflow bug in oping
|
| |/
| |
| |
| |
| |
| | |
Sometimes the receiver thread got the SDU before the writer thread has
set the sent time when testing over the local. The sent time is now
written before actually sending to avoid this.
|
|\ \
| | |
| | |
| | | |
irmd: Fix detection of IRMd
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When starting two IRMds, the second one exits, but applications can't
contact the first because the second instance took the UNIX socket.
Now the lockfile is checked for running IRMd instances before opening
the UNIX socket.
|
|\| |
| | |
| | |
| | | |
lib: Clean up memory management in cacep policies
|
|/ / |
|
|\ \
| | |
| | |
| | | |
ipcpd: normal: Change address authority policy
|
|/ /
| |
| |
| |
| |
| | |
This changes the address authority to follow a similar approach to
that of the other policies. No function pointers are passed to its
user anymore.
|
|\ \
| | |
| | |
| | | |
lib: Exchange protocol info during CACEP
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This exchanges a protocol name, a protocol version and concrete syntax
for the protocol upon CACEP. For CDAP, only version 1 and GPB are
supported. No lists for other supported versions or syntaxes are
exchanged (but the proto file supports it). CACEP fails if there is a
mismatch between the protocol names, version and syntax specified by
the communicating parties.
|