Next: CRC-32 Up: Protocol Specifications Previous: CHAN

CONFOUNDER

CONFOUNDER

DISTRIBUTION NOTE
This protocol will not be distributed via anonymous ftp. If interested, contact xkernel-bugs@cs.arizona.edu about obtaining this protocol. SPECIFICATION
The CONFOUNDER protocol prepends a 4 byte pseudo-random number to the front of each outgoing packet. It pops (and discards) 4 bytes from the front of each incoming packet.

REALM
CONFOUNDER is in the ASYNC realm.

PARTICIPANTS
CONFOUNDER passes participants to the lower protocols without manipulating them.

CONTROL OPERATIONS
CONFOUNDER recognizes the following control operations; all others are passed unchanged to the lower protocol or session.

GETMAXPACKET and GETOPTPACKET: The packet size returned by the lower protocol/session is diminished by 4, and passed upward.

IP_PSEUDOHDR: This control operation turns on the IP pseudoheader length-fixup flag, either for a session or the entire protocol. The control operation is also passed to the lower session or protocol. See IP (page ) for an explanation of this kludge.

CONFIGURATION
CONFOUNDER expects to be configured on top of a transport protocol. The transport protocol must preserve packet boundaries (i.e. CONFOUNDER will not work on top of TCP).

Example of a graph.comp file:


---------------------------------
@;
name=simeth/0;
name=eth protocols=simeth/0;
name=arp protocols=eth;
name=vnet protocols=eth,arp;
name=ip protocols=vnet;
name=confounder protocols=ip;
name=udp protocols=confounder;
@;
prottbl = ../../../etc/prottbl.nonstd;
---------------------------------

RESTRICTIONS
CONFOUNDER always generates the same sequence of pseudo-random numbers.

AUTHORS
Hilarie Orman and Richard Schroeppel


Tue Nov 29 16:28:56 MST 1994