In Client Mode, the Lock is not acting as a router / firewall on the network, it’s acting as a client. This means the Lock will provide a secure remote access to the network but can not protect the devices connected to the same LAN, as the default gateway to Internet is another device on the network.
Deploying Node in Client Mode
- IMPORTANT Remove WAN cable if connected
- Connect your computer to the Lock using the service port.
- Log into the Lock’s browser interface as admin.
- Go to the page Network > LAN
- Set “Protocol” as “DHCP client”, then click “Switch protocol” and after the page has reloaded click “Save”. Wait until the changes have been saved.
- Connect the Lock from any LAN port to the network
If you need to configure Client Mode with static addresses
- Connect your computer to the Lock using the service port.
- Log into the Lock’s browser interface as admin.
- Go to the page Network > LAN.
- Set “Protocol” as “Static”, then click “Switch protocol” and wait until the page has reloaded
- Set LAN IP (free static IP from the target network, e.g. 192.168.100.10 in the example) and set the netmask (255.255.255.0 in the example)
- Set Gateway IP to point to the firewall/router on the target network (192.168.100.1 in the example)
- Finally click “Save”. Wait until the changes have been saved.
- Connect the Lock from any LAN port to the network
Note: With earlier SW versions than v3.3.3 on Lock 100 and Lock 200, the Lock will automatically change to default configuration if the USB modem or WAN cable is connected to the Lock after it has been set to Client Mode. For this reason, neither USB modem nor WAN cable should be connected to Lock when changing the Lock to Client mode. This does not apply from v3.3.3 onwards (Lock 100 & Lock 200) and on all Lock 150 and Lock 500 versions.