If non-zero, instruct pppd to set the serial port to the specified
baudrate. This value should normally be left as 0 to automatically
choose the speed.
If TRUE, specify that pppd should set the serial port to use hardware
flow control with RTS and CTS signals. This value should normally be set
-to FALSE.
If non-zero, instruct pppd to presume the connection to the peer has
failed if the specified number of LCP echo-requests go unanswered by the
peer. The "lcp-echo-interval" property must also be set to a non-zero
@@ -1100,7 +1100,7 @@ value if this property is used.
If non-zero, instruct pppd to send an LCP echo-request frame to the peer
every n seconds (where n is the specified value). Note that some PPP
peers will respond to echo requests and some will not, and it is not
@@ -1111,8 +1111,8 @@ possible to autodetect this.
If non-zero, instruct pppd to request that the peer send packets no
larger than the specified size. If non-zero, the MRU should be between
128 and 16384.
@@ -1131,7 +1131,7 @@ larger than the specified size. If non-zero, the MRU should be between
If TRUE, do not require the other side (usually the PPP server) to
-authenticate itself to the client. If FALSE, require authentication
-from the remote side. In almost all cases, this should be TRUE.
If TRUE, do not require the other side (usually the PPP server) to
+authenticate itself to the client. If FALSE, require authentication
+from the remote side. In almost all cases, this should be TRUE.
If TRUE, MPPE (Microsoft Point-to-Point Encrpytion) will be required for
the PPP session. If either 64-bit or 128-bit MPPE is not available the
session will fail. Note that MPPE is not used on mobile broadband
connections.
If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encrpytion) will be
required for the PPP session, and the "require-mppe" property must also
-be set to TRUE. If 128-bit MPPE is not available the session will fail.
+be set to TRUE. If 128-bit MPPE is not available the session will fail.