•
Interface Type - Specifies if it is a PPTP or L2TP client.
•
Remote Endpoint - The IP address of the remote endpoint. Where this is specified as a URL,
the prefix dns: must be precede it.
Names of Assigned Addresses
Both PPTP and L2TP utilizes dynamic IP configuration using the PPP LCP protocol. When
NetDefendOS receives this information, it is stored in symbolic host/network names. The settings
for this are:
•
Inner IP Address - The host name that is used for storing the assigned IP address. If this
network object exists and has a value which is not 0.0.0.0 then the PPTP/L2TP client will try to
get that one from the PPTP/L2TP server as the preferred IP.
•
Automatically pick name - If this option is enabled then NetDefendOS will create a host name
based on the name of the PPTP/L2TP interface, for example ip_PPTPTunnel1.
•
Primary/Secondary DNS Name - This defines the DNS servers from a list of predefined
network objects.
Note: The default PPTP/L2TP route
A PPTP/L2TP server will not provide information such as gateway or broadcast
addresses, as this is not used with PPTP/L2TP tunnels. When using PPTP/L2TP, the
default route is normally routed directly across the PPTP/L2TP tunnel without a
specified gateway.
Authentication
•
Username - Specifies the username to use for this PPTP/L2TP interface.
•
Password - Specifies the password for the interface.
•
Authentication - Specifies which authentication protocol to use.
•
MPPE - Specifies if Microsoft Point-to-Point Encryption is used and which level to use.
If Dial On Demand is enabled then the PPTP/L2TP tunnel will not be set up until traffic is sent on
the interface. The parameters for this option are:
•
Activity Sense - Specifies if dial-on-demand should trigger on Send or Recv or both.
•
Idle Timeout - The time of inactivity in seconds to wait before disconnection.
Using the PPTP Client Feature
One usage of the PPTP client feature is shown in the scenario depicted below.
Here a number of clients are being NATed through NetDefendOS before being connected to a PPTP
server on the other side of the NetDefend Firewall. If more that one of the clients is acting as a
PPTP client which is trying to connect to the PPTP server then this will not work because of the
NATing.
The only way of achieving multiple PPTP clients being NATed like this, is for the NetDefend
Firewall to act as a PPTP client when it connects to the PPTP server. To summarize the setup:
9.5.4. PPTP/L2TP Clients
Chapter 9. VPN
470
Summary of Contents for NetDefend DFL-1660
Page 28: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 28 ...
Page 88: ...2 6 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 88 ...
Page 166: ...3 10 DNS Chapter 3 Fundamentals 166 ...
Page 254: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 254 ...
Page 268: ...5 4 IP Pools Chapter 5 DHCP Services 268 ...
Page 368: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 368 ...
Page 390: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 390 ...
Page 414: ...8 3 Customizing Authentication HTML Pages Chapter 8 User Authentication 414 ...
Page 490: ...9 8 6 Specific Symptoms Chapter 9 VPN 490 ...
Page 528: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 528 ...
Page 544: ...11 7 HA Advanced Settings Chapter 11 High Availability 544 ...
Page 551: ...12 3 5 Limitations Chapter 12 ZoneDefense 551 ...
Page 574: ...Default 512 13 9 Miscellaneous Settings Chapter 13 Advanced Settings 574 ...
Page 575: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 575 ...