| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
| |
This adds support for adding the application name to a BIND DNS server
through the nsupdate utility.
|
| |
|
|
|
| |
flow allocation now propagates on the client side up to the IPCP.
added UNKNOWN_AP and UNKNOWN_AE definitions to dev.h
|
| |
|
|
|
| |
This abstracts away the IRMd messages by calling the functions from
ipcp.h in the ouroboros library. It also fixes some formatting issues.
|
| |
|
|
|
|
| |
This commits adds the gethostbyname call to resolve the dst_name for a
flow allocation using DNS. The DNS server should be specified using
the method mandated by the system (e.g. added to /etc/resolv.conf).
|
| |
|
|
|
|
|
|
| |
All instance-id's in ouroboros will be set by the system to the pid of
the process associated with this application process instance. This
means that the user has no way to choose the instance id's. Function
calls that assumed manually defined instance id's have been replaced
throughout the system.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Unregistering ap's now works. An AP now registers/unregisters its AP-I
by sending its AP name and its pid to the IRMd. The IPCPs register
whatevercast names. An AP name is currently mapped on a whatevercast
name represented by the same string literal. The IRMd allows
registration of only one AP-I per AP. A Name Space Management system
is needed in the processing system so we can resolve this completely.
Changing the stack to register whatevercast names required some changes
all over the ipcpd implemented and in the library.
|
| | |
|
| |
|
|
|
|
| |
Initial code for application registration. Specifying "*" will (for
now) register with the first IPCP available in the system. Modified
the echo server not to barf messages on failed accept()
|
| |
|
|
|
|
| |
The shim UDP will listen to incoming SDU's for a flow. If the flow is
FLOW_PENDING, it will set it to FLOW_ALLOCATED on the reception of the
first SDU, and connect() to set the destination server_host:sp.
|
| |
|
|
| |
fixes comments on 38c4169 (memleaks)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This implements the API for flow allocation. The shims currently does
the following.
The shim IPCP binds to an interface (IP address) and listens for flow
allocation requests on UDP port 0x0D1F (3359), referenced as the
listen port (lp). It will treat any datagram received on lp as a flow
allocation request.
Upon receiving an allocation request IRM_MSG_CODE__IPCP_FLOW_ALLOC
from the IRMd, the shim IPCP will bind a UDP socket to a port (cp)
allocated by the host OS. From that port it will send a UDP packet
containing the destination ap_name to server_host:lp and wait for a
response.
Upon reception of a packet on server_host:lp, the shim_IPCP creates a
UDP socket for the flow with a port set by the host os (sp), binds to
it and echoes the received datagram back from server_host:sp to
client_host:cp. It will also notify the IRMd of an incoming flow
allocation request IRM_MSG_CODE__IPCP_FLOW_REQ_ARR, with as
src_ap_name ("John Day"). It will get the port_id as a return value
of that message and create a flow with status FLOW_PENDING with that
port_id. If the server responds negatively to the flow allocation
request (i.e. the shim IPCP on the server side receives a
IRM_MSG_CODE__IPCP_FLOW_ALLOC_RESPONSE with a response != 0, it will
delete the pending flow. If response == 0, it will set the status to
FLOW_ALLOCATED.
On the client machine the IPCP will learn sp upon reception of the
echoed datagram. It will then create a flow with the port_id it
received with the message from the IRMd and set it to ALLOCATED.
Pending implementation:
DNS support, this PR only supports local flows on the loopback adapter
127.0.0.1.
A thread to listen for the echoed message, to avoid the
entire IPCP to block when the echoed message is lost.
This PR compiles but is untested pending necessary implementations
elsewhere in the stack.
|
| | |
|
| |
|
|
|
| |
added missing NULL checks
common argument check function for ipcps
|
|
|
Basic functions for implementation of IPC processes, and
implementation of core functions of the shim IPCP over UDP. Updates
to the build system to compile these IPC processes, as well as some
fixes in the irmd (rudimentary capturing exit signals) and some fixes
in the library, mainly relating to the messaging.
Basic implementation of creation / bootstrapping / deletion of the
shim UDP. Placeholders for other functions.
|
