Lines Matching +full:control +full:- +full:field

1 .\" Copyright (c) 2001-2002 Packet Design, LLC.
22 .\" OR NON-INFRINGEMENT.  PACKET DESIGN DOES NOT WARRANT, GUARANTEE,
55 control session packet acknowledgment and retransmission.
60 .Bl -tag -width ".Va session_hhhh"
64 Control packets.
69 L2TP control and data packets are transmitted to, and received from,
82 L2TP control messages (without any L2TP headers) are transmitted
102 .Sh CONTROL MESSAGES
103 This node type supports the generic control messages, plus the following:
104 .Bl -tag -width foo
110 .Bd -literal
125 field enables packet processing.
126 Each time this field is changed back to zero the sequence
132 field configures the local tunnel ID for the control connection.
135 field determines how incoming L2TP packets with a tunnel ID
136 field different from
141 is non-zero, they will be dropped; otherwise, they will be dropped
142 only if the tunnel ID is non-zero.
147 is set to non-zero after receipt of the SCCRP or SCCCN control message.
152 control message.
157 field should be set from the
160 The default value for this field is one; zero is an invalid value.
163 is non-zero, this value may not be decreased.
183 control message back to the node that sent the last
185 Appropriate action should then be taken to shutdown the control connection.
190 This control message configures a single data session.
194 .Bd -literal
199     u_char      control_dseq;   /* whether we control data sequencing */
201     u_char      include_length; /* whether to include length field */
225 is non-zero, then the setting of
229 control message.
243 control message (see below).
249 control of data packet sequencing to the LNS.
253 field determines whether the L2TP header length field is included
255 For incoming packets, the L2TP length field is always checked when present.
304 control message, or when all hooks have been disconnected.