M2M Cellular Gateway
Scenario Application Timing
When the administrator of the gateway wants to set up some service daemons in a host
that is in the Intranet to allow remote users request for services from the host actively,
even the host is behind a NAT gateway. But remote users think the gateway provides
those services, so users use the global IP of the gateway to request their services. Apply
the DMZ feature in the NAT gateway to meet the application scenario. In addition,
please also be noted that the client host is still protected by the gateway firewall.
Scenario Description
The DMZ host is behind a NAT gateway and receives all normal and active packets from
the Internet.
Remote user can access the DMZ host by using the IP address of the gateway, and the
gateway will skip the NAT checking on the DMZ host.
DMZ host is still protected by the gateway firewall.
Parameter Setup Example
Following table lists the parameter configuration as an example for the gateway in
above diagram with DMZ enabling.
Use default value for those parameters that are not mentioned in the table.
Configuration Path
DMZ
Scenario Operation Procedure
In above diagram, the NAT Gateway is the gateway of Network‐A and the subnet of its
Intranet is 10.0.75.0/24. The gateway has the IP address of 10.0.75.2 for LAN interface
and 118.18.81.33 for WAN interface. It serves as a NAT router.
Index skipping is used to reserve slots for new function insertion, when required.
[DMZ]-[Configuration]
IP Address of DMZ Host: 10.0.75.100 ■ Enable
107