As mentioned previously, Diffie-Hellman is used to establish the shared secret keys for IKE, IPsec
and PFS in NetDefendOS. The administrator configured
Diffie-Hellman group number
indicates to
NetDefendOS the level of security that is to be used for DH exchanges. The higher the group
number, the greater the security, but this will also increase the hardware processing resources
required.
The DH groups supported by NetDefendOS are as follows:
•
DH group 1 (768-bit).
•
DH group 2 (1024-bit - the default setting).
•
DH group 5 (1536-bit).
•
DH group 14 (2048-bit).
•
DH group 15 (3072-bit).
•
DH group 16 (4096-bit).
•
DH group 17 (6144-bit).
•
DH group 18 (8192-bit).
Caution: Higher DH group numbers will consume more resources
Most hardware platforms will be able to provide sufficient processing resources for the
default
DH group 2
. Higher group numbers will consume progressively more resources
and this can mean that tunnel setup for the highest groups can be unacceptably long
(tens of seconds) on a slower hardware platform. It could also result in 100% processor
utilization from the tunnel setup process and a possible temporary halt of all traffic
throughput.
9.3.3. IKE Authentication
Manual Keying
The "simplest" way of configuring a VPN is by using a method called
manual keying
. This is a
method where IKE is not used at all; the encryption and authentication keys as well as some
other parameters are directly configured on both sides of the VPN tunnel.
Note
NetDefendOS does not support manual keying.
Manual Keying Advantages
Since it is very straightforward it will be quite interoperable. Most interoperability problems
encountered today are in IKE. Manual keying completely bypasses IKE and sets up its own set of
IPsec SAs.
Manual Keying Disadvantages
It is an old method, which was used before IKE came into use, and is thus lacking all the
functionality of IKE. This method therefore has a number of limitations, such as having to use the
same encryption/authentication key always, no anti-replay services, and it is not very flexible.
There is also no way of assuring that the remote host/firewall really is the one it says it is.
Chapter 9: VPN
690
Содержание NetDefendOS
Страница 30: ...Figure 1 3 Packet Flow Schematic Part III Chapter 1 NetDefendOS Overview 30 ...
Страница 32: ...Chapter 1 NetDefendOS Overview 32 ...
Страница 144: ...Chapter 2 Management and Maintenance 144 ...
Страница 220: ... Enable DHCP passthrough Enable L2 passthrough for non IP protocols 4 Click OK Chapter 3 Fundamentals 220 ...
Страница 267: ... SourceNetwork lannet DestinationInterface any DestinationNetwork all nets 4 Click OK Chapter 3 Fundamentals 267 ...
Страница 284: ...Chapter 3 Fundamentals 284 ...
Страница 360: ...The ospf command options are fully described in the separate NetDefendOS CLI Reference Guide Chapter 4 Routing 360 ...
Страница 392: ...Chapter 4 Routing 392 ...
Страница 396: ...Web Interface 1 Go to Network Ethernet If1 2 Select Enable DHCP 3 Click OK Chapter 5 DHCP Services 396 ...
Страница 419: ... Host 2001 DB8 1 MAC 00 90 12 13 14 15 5 Click OK Chapter 5 DHCP Services 419 ...
Страница 420: ...Chapter 5 DHCP Services 420 ...
Страница 424: ...2 Now enter Name lan_Access Action Expect Interface lan Network lannet 3 Click OK Chapter 6 Security Mechanisms 424 ...
Страница 573: ...Chapter 6 Security Mechanisms 573 ...
Страница 575: ...This section describes and provides examples of configuring NAT and SAT rules Chapter 7 Address Translation 575 ...
Страница 607: ...Chapter 7 Address Translation 607 ...
Страница 666: ...Chapter 8 User Authentication 666 ...
Страница 775: ...Chapter 9 VPN 775 ...
Страница 819: ...Chapter 10 Traffic Management 819 ...
Страница 842: ...Chapter 11 High Availability 842 ...
Страница 866: ...Default Enabled Chapter 13 Advanced Settings 866 ...
Страница 879: ...Chapter 13 Advanced Settings 879 ...