Westermo MR Series - Manual (Page 188)

188 6622-3201
Web Interface and Command Line Reference Guide www.westermo.com
RIP destination IP address list:
RIP packets are normally sent out on a broadcast basis or to a multi-cast address. This parame-
ter may be used to force RIP packets to be sent to a specified IP address. It is particularly useful
if you need to route the packets via a VPN tunnel.
RIP authentication method:
This parameter selects the authentication method for RIP packets.
When set to “Off”, the interface will send and receive packets without any authentication.
When set to “Access List”, the interface will send RIP packets without any authentication. When
receiving packets, the interface will check the sender’s IP address against the list entered on the
Configure > IP Routes > RIP > RIP access list, and if the IP address is present in the list, the
packet will be allowed through. When set to “Plain password (V1+V2)”, the interface will use the
first valid key it finds (set on the
Configure > IP Routes > RIP > Authentication Keys pages), and use the plaintext RIP
authenti cation method before sending the packet out. If no valid key can be found, the interface
will not send any RIP packets. When receiving a RIP packet, a valid plaintext key must be present
in the packet before it will be accepted. This method can be used with both RIP v1 and RIP v2.
When set to “MD5 (V2 only)”, the interface will use the first valid key it finds (set on the
Configure > IP Routes > RIP > Authentication Keys pages), and use the MD5 authentication
algorithm before sending the packet out. If no valid key can be found, the interface will not send
any RIP packets. Received RIP packets must be authenticated using the MD5 authentication algo-
rithm before they will be accepted. This method can be used with RIP v2.
Only send RIP when interface is in service:
When set to ON, RIP packets will only be sent out of this interface if the interface is in service.
DEFLATE compression:
When this parameter is set to “Off”, DEFLATE compression is disabled on this PPP instance.
When set to “On”, DEFLATE compression is enabled and data compression is applied to the
data being carried. The effectiveness of data compression will vary with the type of data but a
typical ratio achieved for a mix of data, for instance Web pages, spread sheets, databases, text
files, GIFs, etc. would be between 2 and 3:1. This has the effect of increasing the connection
through put. If the data is traversing a network where charges are based on the amount of data
passed (such as many GPRS networks), it may also offer significant cost savings. Note however
that if the data is already compressed, such as .zip or .jpg files, then the system will detect that
the data can not be compressed further and send it un-compressed.
MPPE encryption:
When this parameter is set to “On”, the PPP instance will attempt to negotiate MPPE
(Microsoft Point to Point Encryption) with the remote peer. It the remote is unable or unpre-
pared to negotiate MPPE, negotiations will fail. When negotiated, the PPP will encrypt the PPP
frames as per the MPPE standard.
MPPE key size:
This parameter indicates the desired encryption key length to use with MPPE. Valid values for
the mppebits parameter are “Auto”, “40”, “56” and “128”. “Auto” indicates that the unit will
accept whatever the remote suggests. For the other values, the remote must accept and request
the key size specified, else the PPP negotiations will fail.
Note:
With MPPE is that there is no pre-shared keys to set up or keys to set up at all. The encryption
keys are determined by the PPP links themselves on start-up. Therefore, MPPE does not pro-
vide authentication, and only encrypts the data sent on the PPP link.
Time band:
This parameter specifies the Time Band number to use for this PPP instance (see Configure >
Time Bands > Time Band n).