M2M
Cellular
Gateway
Index
skipping
is
used
to
reserve
slots
for
new
function
insertion,
when
required.
241
Configuration
Path
[IPSec]
‐
[Tunnel
Configuration]
Tunnel
■
Enable
Tunnel
Name
s2s
‐
201
Interface
WAN
1
Tunnel
Scenario
Site
to
Site
Operation
Mode
Always
on
Configuration
Path
[IPSec]
‐
[Local
&
Remote
Configuration]
Local
Subnet
10.0.75.0
Local
Netmask
255.255.255.0
Full
Tunnel
■
Enable
Remote
Subnet
10.0.76.0
Remote
Netmask
255.255.255.0
Remote
Gateway
203.95.80.22
Configuration
Path
[IPSec]
‐
[Authentication]
Key
Management
IKE+Pre
‐
shared
Key
12345678
Local
ID
User
Name
Network
‐
B
Remote
ID
User
Name
Network
‐
A
Configuration
Path
[IPSec]
‐
[IKE
Phase]
Negotiation
Mode
Main
Mode
X
‐
Auth
None
Scenario
Operation
Procedure
In
above
diagram,
Network
‐
A
is
in
the
headquarters,
and
the
subnet
of
its
Intranet
is
10.0.76.0/24.
The
security
gateway
for
Network
‐
A
has
the
IP
address
of
10.0.76.2
for
LAN
interface
and
203.95.80.22
for
WAN
interface.
However,
Network
‐
B
is
in
the
branch
office
and
the
subnet
of
its
Intranet
is
10.0.75.0/24.
The
security
gateway
for
Network
‐
B
has
the
IP
address
of
10.0.75.2
for
LAN
interface
and
118.18.81.33
for
WAN
interface.
Establish
an
IPSec
VPN
tunnel
with
"Site
to
Site"
scenario
by
starting
from
either
site.
So
both
Intranets
of
10.0.75.0/24
and
10.0.76.0/24
can
securely
communicate
each
other.
Finally,
all
packet
flows
from
the
client
hosts
in
the
Intranet
of
Network
‐
B
at
branch
office
will
go
through
the
established
VPN
tunnel.
That
means,
the
security
gateway
in
branch
office
supports
"Full
Tunnel"
feature
and
the
client
hosts
behind
it
can
access
not
only
the
server
or
database
resources
in
the
Intranet
of
Network
‐
A
at
HQ,
but
also
the
Internet
in
a
secured
connection.
The
HQ
gateway
controls
and
secures
the
IP
networking
request
flows
from
the
branch
office.
