Follow

OmniNet Cloud-Link Installation Scenarios

There are typically only a couple of ISP scenarios, but some configurations can be unique and not all variations can be accounted for below.

OmniNet recommends using a laptop to determine what your modem is doing. This is quite helpful to determine which scenario below you might have.

As a requirement, port 5246 UDP outbound needs to be allowed through your modem.
(Note: You can always check with ISP ahead of time to make sure that port is not being blocked)


#1 "My modem has DHCP running and is handing out Public IPs on its WAN/ethernet port"

As long as your cable modem has DHCP turned on and it is handing out public IPs, the cloud link will lease a Public IP and public DNS server from your modem, with that setup, the Cloud Link should get online. As long as port 5246 UDP outbound is good, then all you need to do is plug in correctly and reboot your modem. You may need to reboot the Cloud-Link unit after you modem comes back online.

You can test this by connecting your laptop to your modems WAN port and rebooting the modem. If your laptop leases a public IP once your modem comes online, that means it should do the same for the cloud link.


#2 "No DHCP running but I know my public static IP"

If your modem is not running a DHCP server on the WAN port, then you could use the partner config tool with the cloud link connected to a laptop with ethernet port. Using the downloaded tool, you can manually set the static IP on your cloud link. Once that is configured, plug your cloud link into the WAN port on your modem. Reboot modem followed by Cloud-Link Unit.

Here is a link for manually configuring your Cloud Link's static IP
http://support.omninet.io/hc/en-us/articles/203663580-Setting-a-static-public-IP-address-on-your-Cloud-Link-s-WAN-interface


#3 "DHCP is running but it is handing out an internal IP"

Your modem is in router mode. We have many customers that run in this double-NAT configuration and typically is okay for small locations. If the Cloud Link leases and internal IP, as long as it can talk outbound on UDP port 5246 through the modem, it should be able to connect to the OmniNet Cloud.


#4 Changing from Router to Bridge Mode: "My modem is in router mode but I have a static IP and want to configure Cloud-Link to use the static IP"

Your modem is in router mode. If you are running VOIP thru OmniNet Cloud, some customer have found changing configuration for your modem to bridge/passthrough mode and NOT "router mode", results in a better VOIP experience.

In bridge mode, your cloud link will be able to use your ISP assigned static public IP (Only the Cloud-Link can leverage this IP for Cloud-Link connectivity and cannot be leveraged for port forwarding. Use plus subscriptions to give you port forwarding).

Note to DSL customers: OmniNet Cloud Link cannot negotiate DSL PPPoE authentication, so please research if the ISP and modem can allow for bridging in that scenario. Contacting the ISP before hand would be highly suggested.

 

--Changing the modem operation mode--

OmniNet Recommends consulting with your ISP or reading the modem' manufacturer specific setup documentation unless you are experienced with changing modems between these modes.

Log into your modem and configure it to run in bridge mode

You will likely have to set the static IP on your cloud link - see below

Here is the link for manually setting your cloud link's static IP:

 http://support.omninet.io/hc/en-us/articles/203663580-Setting-a-static-public-IP-address-on-your-Cloud-Link-s-WAN-interface

 

- Troubleshooting -


Please refer to our updated troubleshooting page at the following link:

http://support.omninet.io/hc/en-us/articles/203905430-Cloud-Link-doesn-t-connect-no-connection-to-MDS-Cloud

 

Note to DSL customers:

DSL encapsulation when using OmniNet may very likely require that the MTU Value on the modem is turned down to 1452.

Have more questions? Submit a request
Powered by Zendesk