| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
IPCPs will report their pid on shutdown for faster debugging.
|
| |
|
|
|
| |
Flows are deallocated first, then the socket is closed to prevent
IPCPs hanging on the connect.
|
| |
|
|
| |
Destruction of the object in the reply stage was unsafe.
|
| | |
|
| | |
|
| |
|
|
| |
This removes the ret value which was not being set correctly.
|
| |\
| |
| |
| | |
Fix locks
|
| | | |
|
| | | |
|
| |\|
| |
| |
| | |
ipcpd: Revised locking
|
| | |
| |
| |
| |
| |
| | |
The state lock was reverted to an rwlock to avoid interference of
management functions with the fast path. IPCPs now close without
calling unsafe functions in the signal handler.
|
| |\ \
| |/
|/|
| | |
ipcpd: normal: Add initial steps for N+1 flow allocation
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds the initial framework for flow allocation between two N+1
endpoints. The FMGR will receive flow allocation requests and will
create a connection as a result, addressed to the right address, it
will also pass a flow allocation message to this address. Upon receipt
on the other side, the FMGR will be receive a flow allocation message
and a pointer to a new connection. The FMGR can then accept or destroy
the connection. This commit also introduces the RMT function, which is
needed by the FRCT to forward its SDUs on the right file descriptor.
|
| | | |
|
| | |
| |
| |
| | |
ap_table had no function to look for entries by apn.
|
| | | |
|
| | |
| |
| |
| |
| | |
The reg_entry_del_api must be called to correctly set the flow
handling state instead of just clearing the entry from the list.
|
| | |
| |
| |
| | |
Location-dependent names should be managed by a higher-level NMS.
|
| | |
| |
| |
| |
| | |
The apis parameter is not set if the IRMd is not running when running
the tool.
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The complete data model inside the IRMd has been restructured. The
bind operation was revised to allow binding of AP and AP instances and
register those names with different DIFs (see "irm bind" for details).
Server applications require to call ap_init with a server name
argument, client application that do not the be reachable over any DIF
can call ap_init(NULL). Calling ap_init for a client with a specified
name will not have adverse consequences for the application, but will
consume unnecessary resources in the IRMd.
Application servers can now be started at any point after the IRMd has
been started. Starting servers, binding AP names and registering names in
DIFs can be performed in any order that does not defy temporal logic.
Supports naming instances by their pid. In case of IPCP Instances
created with the IRM tool, the name assigned during "irm ipcp create"
can be used.
All the changes required updates in the tools.
|
| |
|
|
|
|
|
|
| |
This adds a condition variable with a timeout to the CDAP request so
that we can respond correctly to the answer from the remote. It also
adds a timeout to the condition variable waiting on completion of
enrollment. Furthermore, for every CDAP callback a new thread is now
spawned, to avoid deadlocking in case a callback is stuck.
|
| |
|
|
|
|
|
| |
Previously it was up to the admin to choose whether or not to enable
DDNS. Now the build just checks if the executables can be found, and
if they are available DDNS functionality is enabled, else it is
disabled.
|
| |
|
|
|
| |
Calling api_bind during bootstrap caused the IRMd to lock up.
api_bind is now called after the normal completes bootstrapping.
|
| |
|
|
|
|
|
| |
This adds a condition variable to the IPCP state, so that upon state
changes any listeners to state changes can be notified. It also
replaces the read/write lock with a mutex in order to be able to do
so.
|
| |\
| |
| |
| | |
ipcpd: normal: Fix log message
|
| | |
| |
| |
| |
| | |
conf->dif_name was not copied from the dif_config gpb message.
Fixes some logs.
|
| | | |
|
| |/
|
|
|
| |
This will create a new IPCP if enroll is called on a non existing
IPCP. It also fixes two memleaks.
|
| |
|
|
|
| |
Now the correct max length of an SDU is checked upon writing a frame,
as well as on receiving it.
|
| |\
| |
| |
| | |
lib, irmd: Bind AP instances to AP_subsets
|
| | |
| |
| |
| |
| |
| |
| | |
This call will allow grouping AP instances of a certain AP together
which are configured identically. Adds the bind operation to dev and
updates the applications to make use of this call. Flow_alloc is now
only called with the pid and doesn't send the apn anymore.
|
| | |
| |
| |
| |
| |
| | |
This adds the MSG_DONTWAIT flag to the send function of the
shim-eth-llc, when using PF_PACKET. Previously the send would return
only after the frame was sent, resulting in poor performance.
|
| |/
|
|
|
|
| |
This will add a timeout to the socket so that a process won't be
blocked by the actions of the process with which it is communicating
over the socket.
|
| |\ |
|
| | |\
| | |
| | |
| | | |
ipcp, irmd, lib: Notify IRMd upon IPCP initialization
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This will notify the IRMd when the IPCP is initialized and ready to
receive messages. Previously a bootstrap could fail since the IPCP was
not listening to the socket yet.
|
| | |\ \
| | | |
| | | |
| | | | |
Several small fixes and enhancements
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the admin tries to bootstrap an IPCP that does not yet exist, it
will first create the IPCP, then bootstrap it since it has all
required information.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If an IPCP crashes (due to a segfault for instance), it is removed
from the spawned apis list. However, if it was an IPCP it should also
be removed from the IPCPs list, since else on shutdown, the irmd will
try to destroy the IPCP that crashed.
|
| | | |/
| | |
| | |
| | |
| | | |
A lock was not being taken to check the state, but then it was
released if the state was not IPCP_NULL, resulting in a segfault.
|
| |/ /
| |
| |
| |
| |
| | |
Threads from the threadpool will now check the state of the IRMd and
exit gracefully without a need to cancel them. This avoids the unsafe
call of pthread_cancel in the signal handler.
|
| |/
|
|
| |
registry_sanitize_apis should be called under write locked reg_lock.
|
| | |
|
| |
|
|
| |
Cleanup handlers were not always popped.
|
| | |
|
| | |
|
