There are a number of ways to slice this one.
First of all, you need a routable IP address - one reachable from the outside. If your connections are behind a (carrier) NAT then you need to set up a connection to (and by way of) some outside router, e.g., a fusionhub.
Secondly, assume that you have routable IP address(es) to the WAN interface(s) of the device (be they dynamic or static) then Peplink is offering a DNS name for each interface of the device though its Incontrol2 registration. And in particular it defines a hostname for the IP address employed by the device to connect to IC2. That may vay over time (as connections are enabled or disabled).
E.g., assume your router is a Balance One, with two WAN interfaces. Assume further that you have named it “MyBalanceOne” in IC2, and have activated the “Find My Peplink Address” feature.
Your internet hostname will then be “MyBalanceOne.mypep.link”
Your WAN-1 interface will be “wan-1.MyBalanceOne.mypep.link” and whatever IP address the device connects to IC2 will be “ic2-detected.MyBalanceOne.mypep.link”. As the WANs go up or down, the “ic2-detected.MyBalanceOne.mypep.link” will change (though I don’t know how frequently that is being updated).
That might do the trick for you.
A couple of things to keep in mind:
- The IP address of ic2-detected.MyBalanceOne.mypep.link will be wherever the breakout is for communications to IC2 from the device. If the device is behind a carrier NAT then the IP address will be that of the gateway to the internet, and not (by itself) usable.
- If the device is connected to a fusionhub (or other gateway device) and traffic is routed through that gateway then the IP address of ic2-detected.MyBalanceOne.mypep.link will be one that you control, and would allow you to set up the proper port or address forwarding from the gateway to the device.
Just the usual $0.02.