This section has three downwards commands and three upwards ones.
This indicates that a promiscuous ethernet packet has arrived. The EDL packet data follows the manage_msg structure. The fields are:
This indicates that a packet has been received on an association which is not currently valid. The manager should perform whatever signalling is required to quench the source. The manager should regard this as an expedited operation. The fields are:
This indicates that a meta signalling FDL cell has arrived. The FDL cell follows the manage_msg structure. The fields are:
This is used to create the association data path for a socket. It gives all the information necessary to prepare tables in the drivers etc. No assoc destroy is provided because the destruction call-backs are called automatically when the socket is disconnected, detached or aborted. The valid fields are:
The possible errors generated by the kernel association code are:
This is used to send a meta-signalling packet on the specified pod. The code for this isn't 100% finished yet. The data to be sent follows the struct manage_msg. The valid fields are:
The possible errors generated by the kernel association code are:
This is used to allow the manager to inquire if an association has had any traffic on it, and is for the purposes of automatic tearing down of unused circuits. This call will mark the association as idle and return the current value of its idle flag. Assocations are created in the idle state. This call should clearly only be used in the ioctl form. Fields used are:
