How to set up IP Passthrough

Industrial Routers
,
1

Background: IP Passthrough allows the router to act as a bridge, passing the IP address it receives from the carrier to one attached device. Once the router is in IP Passthrough mode, using the IP will only reach the end device and remote access to the router can only be achieved through one of our cloud platforms. This feature is useful for allowing remote connections to a device connected to the router.

Note 1: Before setting up IP Passthrough, the router must be receiving a public IP from the carrier. In order to test this, go to Status>Network Connections. Under Cellular/Dialup>IP address, input that IP address into a new tab/window on the browser and if it reaches the router login page, then that means IP Passthrough can allow remote connection to the end device.

Note 2: Only one device will receive the IP address, if there are two devices attached, the other one will not get internet. You can specify which device to pass the IP to by changing IP Passthrough Mode to DHCP Fixed MAC, and setting the MAC address.

1. Connect PC to router via Ethernet and log in on 192.168.2.1 using default credentials (adm/123456)

2. Go to Network->IP Passthrough.

content.png831×453 64.9 KB

3.     Check the Enable IP Passthrough, choose the DHCP Dynamic for IP Passthrough Mode and
apply. Leave DHCP lease at 2 minutes.

content.png831×293 55.8 KB

4. If PC/device is not getting IP passed, please release and renew the current DHCP lease, restart router or end device, or unplug and re-plug the Ethernet cable to force a new DHCP request.


2
Hello, I'm using this feature on IR302 running latest firmware (3.5.99) and it's working great. I just don't understand how it's possible to still monitor/manage the IR302 from IHN's Device Manager cloud service if the public IP is assigned to the downstream client/device (how is the IR302 able to communicate with no IP assigned to it)?
3
Also, I see that with IP Passthrough enabled on the IR302 (running latest firmware [3.5.99]) it's assigning the public IP to the downstream client/device (as expected) but with a /16 subnet mask for some reason. This is definitely not the default (ISP-assigned) subnet mask for the IP but rather a modification that the IR302 is performing on the IP addressing assigned to the downstream device. Why is this? I feel that some modification to the IP addressing is necessary to allow the IR302 to "share" the single public IP, but /16 creates a very large range of IPs that downstream devices may no longer be able to reach (when trying to access internet services that may be hosted at those public IPs), due to those IPs now being destined for the "virtual subnet" created by the IR302 and (assumedly) dropped?