D-Link DIR-330 Product Manual - Page 38

XAUTH, Server Mode, Client Mode, Local/Remote ID, Local ID, Remote ID, Main Mode, Aggressive Mode - vpn client

Page 38 highlights

Section 3 - Configuration • Additional Authentication Methods (Optional) XAUTH - Check this box to include additional username and password authentication requirements for the VPN. Select Server Mode or Client Mode. • Server Mode - Select a group from the Authentication database drop-down menu containing the list of user credentials permitted. • Client Mode - Enter the user name and password if required by the remote VPN server endpoint configured in xAuth Server Mode. Local/Remote ID - Check this box to include additional ID authentication requirements for the VPN using a specific IP Address, FQDN, ASN1, or a Custom String. • Local ID - Select one of the options from the drop-down menu. Enter an ID to identify and authenticate the local VPN endpoint. • Remote ID - Select one of the options from the drop-down menu. Enter an ID to identify and authenticate the remote VPN endpoint. Main / Aggressive Mode: Select Main Mode or Aggressive Mode for IKE Phase 1 negotiation. • Main Mode - Select this option to configure the standard negotiation parameters for IKE Phase 1 of the VPN Tunnel. (Recommended Setting) • Aggressive Mode - Select this option to configure IKE Phase 1 of the VPN Tunnel to carry out negotiation in a shorter amount of time. (Not Recommended - Less Secure) NAT-T Enable: Check this box to enable NAT Traversal. Enabling this option will allow IPSec traffic from this endpoint to traverse through the translation process during NAT. The remote VPN endpoint must also support this feature and it must be enabled to function properly over the VPN. D-Link DIR-330 User Manual 33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112

33
D-L±nk DIR-330 User Manual
Sect±on 3 - Configurat±on
Main / Aggressive Mode:
NAT-T Enable:
• Additional Authentication Methods (Optional)
XAUTH
- Check this box to include additional username and password authentication requirements for the VPN.
Select
Server Mode
or
Client Mode
.
Server Mode
- Select a group from the Authentication database drop-down menu containing the list
of user credentials permitted.
Client Mode
- Enter the user name and password if required by the remote VPN server endpoint
configured in xAuth Server Mode.
Local/Remote ID
- Check this box to include additional ID authentication requirements for the VPN using a specific
IP Address, FQDN, ASN1, or a Custom String.
Local ID
- Select one of the options from the drop-down menu. Enter an ID to identify and authenticate
the local VPN endpoint.
Remote ID
- Select one of the options from the drop-down menu. Enter an ID to identify and authenticate
the remote VPN endpoint.
Select Main Mode or Aggressive Mode for IKE Phase 1 negotiation.
Main Mode
- Select this option to configure the standard negotiation parameters for IKE Phase 1 of
the VPN Tunnel. (Recommended Setting)
Aggressive Mode
- Select this option to configure IKE Phase 1 of the VPN Tunnel to carry out
negotiation in a shorter amount of time. (Not Recommended - Less Secure)
Check this box to enable NAT Traversal. Enabling this option will allow IPSec traffic from this endpoint to traverse
through the translation process during NAT. The remote VPN endpoint must also support this feature and it must
be enabled to function properly over the VPN.