EasyManua.ls Logo

Pepwave Surf SOHO - Page 51

Pepwave Surf SOHO
151 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Remote IP
Address / Host
Names (Optional)
If
NAT Mode
is not enabled, you can enter a remote peers WAN IP
address or hostname(s) here. If the remote uses more than one address,
enter only one of them here. Multiple hostnames are allowed and can be
separated by a space character or carriage return. Dynamic-DNS host
names are also accepted.
This field is optional. With this field filled, the Pepwave Surf SOHO will
initiate connection to each of the remote IP addresses until it succeeds
in making a connection. If the field is empty, the Pepwave Surf SOHO
will wait for connection from the remote peer. Therefore, at least one of
the two VPN peers must specify this value. Otherwise, VPN connections
cannot be established.
Click the icon to configure data stream using TCP protocol
[EXPERIMENTAL].In the case TCP protocol is used, the exposed TCP
session option can be authorised to work with TCP accelerated WAN
link.
Cost
Define path cost for this profile.
OSPF will determine the best route through the network using the
assigned cost.
Default: 10
Data Port
This field is used to specify a UDP or TCP port number for transporting
outgoing VPN data. If
Default
is selected, UDP port 4500 will be used.
Port 32015 will be used if port 4500 is unavailable. If
Custom
is
selected, enter an outgoing port number from 1 to 65535.
Bandwidth Limit
Define maximum download and upload speed to each individual peer.
This functionality requires the peer to use PepVPN version 4.0.0 or
above.
Receive Buffer
Receive Buffer can help to reduce out-of-order packets and jitter, but will
introduce extra latency to the tunnel. Default is 0 ms, which disable the
buffer, and maximum buffer size is 2000 ms.
Packet
Fragmentation
If the packet size is larger than the tunnels MTU, it will be fragmented
inside the tunnel in order to pass through.
Select Always to fragment any packets that are too large to send, or Use
DF Flag to only fragment packets with Dont Fragment bit cleared. This
can be useful if your application does Path MTU Discovery, usually
sending large packets with DF bit set, if allowing them to go through by
fragmentation, the MTU will not be detected correctly.

Related product manuals