IP Overrides - Manage Consecutive Static IP bank - IP-Overrides-Manage-Consecutive-Static-IP-bank/IP-Overrides-Manage-Consecutive-Static-IP-bank

IP Overrides - Manage Consecutive Static IP bank
NetCloud Feature
Routing
ft:locale
en-US
ft:sourceName
Salesforce
allViewCount
3679
Document Type
Article
  • Provide an override in the config to prevent devices in large scale environments from using each other as the internet gateway.
  • This document will demonstrate overriding the cellular WAN interface's subnet/gateway information. E.g.
    • 166.10.20.x with a gateway of 166.10.20.x(+-1) and a subnet mask of 255.255.255.240.
    • Override will force the Gateway to 166.10.20.1 and force the subnet mask to 255.255.255.0.
  • Consecutive static WAN IP addresses
  • Devices connect to the same tower
  • Topology example:
consecutive IP cellular
Confirm the topology and what subnet the modems are connecting as on their WAN:
  1. Locate the modem in connection manager
    • User-added image
  2. Select the modem so that the field expands. This will show the device IP address and gateway.
    • User-added image

Override the cellular WAN interface's subnet/gateway information:
  1. Select the target modem and click Edit.
  2. On the IPv4 Configuration page, Enter only the following data:
    1. Subnet mask: 255.255.255.0
    2. Gateway IP 166.10.20.1 (Enter the values that match your subnet. In this example, I have selected x.x.x.1 as my gateway because it is a free IP address on that subnet and will not overlap with a unit in use.)
      •  User-added image
  3. Click Save. 
  • This will reset the modem. 
  • A gateway address is not needed for the cellular network. 
  • A gateway will be used by the router and may be required for routing decisions. 
  • When the Cradlepoint gets a network connection there is an algorithm that runs to determine if the gateway IP address is one value higher or lower than the device's IP address.
  • If a device with that IP is connected to the same tower, undesirable routing can occur. I.e. device routes to device two instead of out to the carrier. 
  • This is a common occurrence with fleet deployments where all vehicles are parked in a central lot or use the same tower to connect to cellular. 
  • VPN tunnels fail to connect with log messages like
  • Fri May 4th 10:08:54 2018    ipsec    INFO    03[NET] error writing to socket: Permission denied
Fri May 4th 10:08:54 2018    ipsec    INFO    14[NET] sending packet: from x.x.x.253[500] to x.x.x.252[500] (180 bytes)
Fri May 4th 10:08:54 2018    ipsec    INFO    14[ENC] generating ID_PROT request 0 [ SA V V V V V ]