264 MDS Orbit MCR/ECR Technical Manual MDS 05-6632A01, Rev. F
in-packets 0
in-last-use 1615520
out-bytes 0
out-packets 0
out-last-use 0
rekey-time 1195
life-time 2202
install-time 1399
local-ts 192.168.1.0/24
remote-ts 192.168.2.0/24
Ping the back-office PC from the local device to make sure the traffic is passing between device and PC.
> ping 192.168.2.1
PING 192.168.1.2 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=63 time=389 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=63 time=161 ms
--- 192.168.2.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 550ms
rtt min/avg/max/mdev = 161/275/389/114 ms
Troubleshooting
The following are common reasons for VPN connection failure:
Invalid certificate or keys loaded on the device 1.
Time not synchronized on the device. Note that after cell connection is established, device can take 2.
few minutes to sync time from NTP server. VPN connection will not succeed until time is
synchronized.
Mismatch in cipher suites configured for IKE policy on device and peer VPN gateway.
3.
Mismatch in cipher suites configured for IPsec policy on device and peer VPN gateway. 4.
Mismatch in remote and local IP subnets configured for IPsec connection on device and peer VPN 5.
gateway. Note the following:
For device
- remote ip subnet = back-office subnet
- local ip subnet = local LAN or WIFI subnet on device
For VPN gateway
- remote ip subnet = device’s local LAN or WIFI subnet
- local ip subnet = back-office subnet on device
DHCP Service 3.8.13
Understanding
The unit can be configured to act as a DHCP server. When enabled, this service will respond to DHCP
requests from any interface.
As a DHCP server, the unit can assign either IPv4 or IPv6 addresses to clients
NOTE At least one of the unit’s interfaces (ETH1, ETH2, WiFi or Bridge if the interface is bridged)
must be configured with an IP address from the subnet of the configured DHCP.
To Next Page
Loading...
