Home » ZyXEL Manuals » Networking » ZyXEL MAX318M » Manual Viewer

ZyXEL MAX318M User Guide - Page 148

VPN, NAT, and NAT Traversal, 8.12.7 ID Type and Content, Table 62, SECURITY PROTOCOL

Get ZyXEL MAX318M PDF manuals and user guides

Add to My Manuals
Save this manual to your list of manuals

Page 148 highlights

Chapter 8 Security 8.12.6 VPN, NAT, and NAT Traversal NAT is incompatible with the AH protocol in both transport and tunnel mode. An IPSec VPN using the AH protocol digitally signs the outbound packet, both data payload and headers, with a hash value appended to the packet, but a NAT device between the IPSec endpoints rewrites the source or destination address. As a result, the VPN device at the receiving end finds a mismatch between the hash value and the data and assumes that the data has been maliciously altered. NAT is not normally compatible with ESP in transport mode either, but the WiMAX Device's NAT Traversal feature provides a way to handle this. NAT traversal allows you to set up an IKE SA when there are NAT routers between the two IPSec routers. Figure 83 NAT Router Between IPSec Routers A B Normally you cannot set up an IKE SA with a NAT router between the two IPSec routers because the NAT router changes the header of the IPSec packet. NAT traversal solves the problem by adding a UDP port 500 header to the IPSec packet. The NAT router forwards the IPSec packet with the UDP port 500 header unchanged. In the above figure, when IPSec router A tries to establish an IKE SA, IPSec router B checks the UDP port 500 header, and IPSec routers A and B build the IKE SA. For NAT traversal to work, you must: • Use ESP security protocol (in either transport or tunnel mode). • Use IKE keying mode. • Enable NAT traversal on both IPSec endpoints. • Set the NAT router to forward UDP port 500 to IPSec router A. Finally, NAT is compatible with ESP in tunnel mode because integrity checks are performed over the combination of the "original header plus original payload," which is unchanged by a NAT device. The compatibility of AH and ESP with NAT in tunnel and transport modes is summarized in the following table. Table 62 VPN and NAT SECURITY PROTOCOL AH AH ESP ESP MODE Transport Tunnel Transport Tunnel NAT N N Y* Y Y* - This is supported in the WiMAX Device if you enable NAT traversal. 8.12.7 ID Type and Content With aggressive negotiation mode (see Section 8.12.4 on page 147), the WiMAX Device identifies incoming SAs by ID type and content since this identifying information is not encrypted. This 148 WiMAX Device Configuration User's Guide

Section	Page
WiMAX CPE Series	1
About This User's Guide	3
Document Conventions	4
Safety Warnings	6
Contents Overview	7
Table of Contents	9
User’s Guide	15
Introduction to the Series	17
1.1 About Your WiMAX Device	17
1.1.1 WiMAX Internet Access	18
1.1.2 Models with Phone Ports	18
1.1.3 Models with WiFi	19
1.2 Good Habits for Managing the WiMAX Device	19
Introduction to the Web Configurator	20
2.1 Overview	20
2.1.1 Accessing the Web Configurator	20
2.1.2 Saving and Canceling Changes	21
2.1.3 Working with Tables	21
2.2 The Main Screen	22
Setup Wizard	25
3.1 Overview	25
3.1.1 Welcome to the Setup Wizard	25
3.1.2 LAN Settings	26
3.1.3 WiMAX Frequency Settings	27
3.1.4 WiMAX Authentication Settings	28
3.1.5 VoIP Settings	30
3.1.6 WLAN Settings	32
3.1.7 Setup Complete	34
Tutorials	35
4.1 Overview	35
4.2 WiMAX Connection Settings	35
4.3 Setting Up a Small Network for the LAN	36
4.4 Making a Telephone Call Over the Internet	38
4.4.1 Configure Your SIP Account	38
4.5 Blocking Web Access from the WiMAX Device	40
4.6 Restricting Wireless Access to the WiMAX Device	40
4.7 Allowing Internet Users to use Internal Servers	42
4.8 Access the WiMAX Device with a Domain Name	44
4.8.1 Registering a DDNS Account on www.dyndns.org	45
4.8.2 Configuring DDNS on Your WiMAX Device	46
4.8.3 Testing the DDNS Setting	46
4.9 Configuring Static Route for Routing to Another Network	46
4.10 Remotely Managing Your WiMAX Device	48
4.11 Changing Certificate to Communicate with Other Networks	49
4.12 Using Virtual Networks	50
4.12.1 Scenario 1	51
4.12.2 Scenario 2	52
4.12.3 Scenario 3	54
4.12.4 Scenario 4	56
4.12.5 Scenario 5	58
Technical Reference	61
System Status	63
5.1 Overview	63
5.2 System Status	63
WiMAX	67
6.1 Overview	67
6.1.1 What You Need to Know	67
6.2 Connection Settings	70
6.3 Frequency Settings	72
6.4 Authentication Settings	74
6.5 Channel Plan Settings	77
6.6 CAPL Settings	79
6.6.1 CAPL Settings: Add	80
6.7 RAPL Settings	81
6.8 Home NSP Settings	82
6.9 Connect	83
6.10 Wide Scan	85
6.11 Link Status	87
6.12 Link Statistics	88
6.13 Connection Info	89
6.14 Service Flow	89
Network Setting	91
7.1 Overview	91
7.1.1 What You Need to Know	91
7.2 WAN	94
7.3 PPPoE	96
7.4 GRE	97
7.5 EtherIP	98
7.6 IP	98
7.7 DHCP	99
7.8 WLAN	100
7.9 WPS	102
7.10 MAC Address Filter	103
7.11 Static Route	104
7.12 Static Route Add	104
7.13 RIP	105
7.14 Port Forwarding	107
7.14.1 Port Forwarding Wizard	108
7.15 Port Trigger	108
7.15.1 Port Trigger Wizard	110
7.15.2 Trigger Port Forwarding Example	111
7.16 DMZ	111
7.17 ALG	112
7.18 QoS	113
7.19 UPnP	113
7.19.1 Installing UPnP in Windows XP	114
7.19.2 Web Configurator Easy Access	118
7.20 VLAN	119
7.21 DDNS	121
7.22 IGMP Proxy	123
7.23 Content Filter	123
Security	125
8.1 Overview	125
8.1.1 What You Need to Know	125
8.2 IP Filter	125
8.3 MAC Filter	126
8.4 DDOS	127
8.5 PPTP VPN Server	129
8.6 PPTP VPN Client	130
8.7 PPTP VPN Client: Add	131
8.8 L2TP VPN Server	133
8.9 L2TP VPN Client	135
8.10 L2TP VPN Client: Add	135
8.11 IPSec VPN	137
8.11.1 IPSec VPN: Add	139
8.12 Technical Reference	144
8.12.1 IPSec Architecture	144
8.12.2 Encapsulation	145
8.12.3 IKE Phases	146
8.12.4 Negotiation Mode	147
8.12.5 IPSec and NAT	147
8.12.6 VPN, NAT, and NAT Traversal	148
8.12.7 ID Type and Content	148
8.12.8 Pre-Shared Key	150
8.12.9 Diffie-Hellman (DH) Key Groups	150
The VoIP General Screens	151
9.1 VoIP Overview	151
9.1.1 What You Need to Know	151
9.1.2 Before you Begin	152
9.2 Media	153
9.3 QoS	154
9.4 SIP Settings	155
9.5 Speed Dial	155
9.6 Technical Reference	156
9.6.1 DSCP and Per-Hop Behavior	156
The VoIP Account Screens	157
10.1 Overview	157
10.1.1 What You Need to Know	157
10.2 Status	160
10.3 Server	161
10.4 SIP	163
10.5 Feature	165
10.6 Dialing	166
10.7 FAX	167
10.8 Technical Reference	167
10.8.1 SIP Call Progression with Session Timer	167
10.8.2 SIP Client Server	170
The VoIP Line Screens	171
11.1 Overview	171
11.1.1 What You Need to Know	171
11.2 Phone	172
11.3 Voice	172
11.4 Region	173
Maintenance	175
12.1 Overview	175
12.1.1 What You Need to Know	175
12.2 Password	180
12.3 HTTP	181
12.4 Telnet	181
12.5 SSH	182
12.6 SNMP	183
12.7 CWMP	183
12.8 OMA-DM	185
12.9 Date/Time	187
12.10 Time Zone	187
12.11 Upgrade File	188
12.11.1 The Firmware Upload Process	189
12.12 Upgrade Link	189
12.13 CWMP Upgrade	189
12.14 Backup/Restore	190
12.15 Restore	190
12.15.1 The Restore Configuration Process	191
12.16 Factory Defaults	191
12.17 Log Setting	192
12.18 Log Display	192
12.19 Network Test	193
12.20 Traceroute	194
12.21 About	194
12.22 Reboot	195
Troubleshooting	197
13.1 Power, Hardware Connections, and LEDs	197
13.2 WiMAX Device Access and Login	198
13.3 Internet Access	199
13.4 Wireless Internet Access (for Models with WiFi)	201
13.5 Phone Calls and VoIP (for Models with Phone Ports)	201
13.6 Reset the WiMAX Device to Its Factory Defaults	202
13.6.1 Pop-up Windows, JavaScript and Java Permissions	202
Product Specifications	203
WiMAX Security	207
Importing Certificates	211
Common Services	237
Open Software Announcements	241
Legal Information	277

Match case Limit results 1 per page

Chapter 8 Security

WiMAX Device Configuration User’s Guide

148

8.12.6

VPN, NAT, and NAT Traversal

NAT is incompatible with the AH protocol in both transport

and tunnel

mode. An IPSec VPN using

the AH protocol digitally signs the outbound packet, both data payload and headers, with a hash

value appended to the packet, but a NAT device between the IPSec endpoints rewrites the source or

destination address. As a result, the VPN device at the receiving end finds a mismatch between the

hash value and the data and assumes that the data has been maliciously altered.

NAT is not normally compatible with ESP in transport mode either, but the WiMAX Device’s

NAT

Traversal

feature provides a way to handle this. NAT traversal allows you to set up an IKE SA when

there are NAT routers between the two IPSec routers.

Figure 83

NAT Router Between IPSec Routers

Normally you cannot set up an IKE SA with a NAT router between the two IPSec routers because

the NAT router changes the header of the IPSec packet. NAT traversal solves the problem by adding

a UDP port 500 header to the IPSec packet. The NAT router forwards the IPSec packet with the UDP

port 500 header unchanged. In the above figure, when IPSec router

tries to establish an IKE SA,

IPSec router

checks the UDP port 500 header, and IPSec routers

and

build the IKE SA.

For NAT traversal to work, you must:

•

Use ESP security protocol (in either transport or tunnel mode).

•

Use IKE keying mode.

•

Enable NAT traversal on both IPSec endpoints.

•

Set the NAT router to forward UDP port 500 to IPSec router

Finally, NAT is compatible with ESP in tunnel mode because integrity checks are performed over the

combination of the "original header plus original payload," which is unchanged by a NAT device. The

compatibility of AH and ESP with NAT in tunnel and transport modes is summarized in the following

table.

Y* - This is supported in the WiMAX Device if you enable NAT traversal.

8.12.7

ID Type and Content

With aggressive negotiation mode (see

Section 8.12.4 on page 147

), the WiMAX Device identifies

incoming SAs by ID type and content since this identifying information is not encrypted. This

Table 62

VPN and NAT

SECURITY PROTOCOL

MODE

NAT

Transport

Tunnel

ESP

Transport

ESP

Tunnel