Follow

Static IPs and OmniNet Services

Definitions

A) ISP Static IP:

Static IP that is assigned by customers' internet service provider

 

B) OmniNET Static IP/OmniNET Port Forward IP

IP assigned to OmniNET "plus" subscriptions that ingress traffic through OmniNET services.  This is an optional add-on so be careful to include this if it is necessary as defined within this article.

 

Summary

OmniNet offers several solutions to provide filtering services.  Depending on which method you choose to integrate with OmniNET, the use of static IPs can vary slightly.  However, some things remains constant with any subscription: 

TRUTH#1

If you want to forwarding inbound traffic to a subscription connected to OmniNET, you must purchase an OmniNET Static IP/Port Forwarding IP.

 

TRUTH#2

You cannot leverage a customers ISP Static IP for inbound traffic (port forwarding) once you are online with OmniNET services.  This is due to the security design. All outbound traffic is forced to our datacenter and therefore per routing needs, inbound services need to ingress at our DC to be let in and back out again.

 

Now lets go into how these are applicable based on which solution you choose to integrate with OmniNET.

 

OmniWAN' OmniBridge

(A) ISP Static IP required? NO

No.  OmniBridges can function both behind an existing router assigning a private IP to the OmniBridge, or with the modem in bridge/passthrough mode with a static IP.  As long proper protocols are allowed through the OmniBridge, it will come online in either scenario.  See OmniBride installation instructions for further details.

(B) OmniNET Static IP/Port Forward IP required: NO.  Only if port forwarding is required for your customer.  One additional benefit to have OmniNET Static IP/Port Forward IP, egress traffic will use the same IP so traffic will both ingress and egress with the same IP.

 

OmniBridge Recommended scenario:  Modem in router mode with DHCP and OmniBridge plugged into LAN. Buy a (B) OmniNET Static IP if port forwarding is needed.

 

Cloud-Links (Classic)

(A) ISP Static IP required? NO

No.  Cloud-links can function both behind an existing router assigning a private IP to the Cloud-link, or with the modem in bridge/passthrough mode with a static IP assigned to the Cloud-link using the partner tool.  As long proper protocols are allowed through the modem, it will come online in either scenario.  See Cloud-link installation instructions for further details.

(B) OmniNET Static IP/Port Forward IP required? NO

NO.  Only necessary if port forwarding is required for your customer.

 

Cloud-link recommended scenario:  Modem in router mode with DHCP and Cloud-link plugged into LAN. Buy a (B) OmniNET Static IP if port forwarding is needed.

 

 

BYOG

(A) ISP Static IP required? YES*...

YES* for most subscriptions.

* DynamicDNS as a BETA is available for partner to test but is officially unsupported due to 3 parties needing to sync up perfectly to avoid customer disruptions. Since this is a site-to-site tunnel, when public IP changes are initiated by the ISP, the tunnel is disrupted. While DynamicDNS updates apply and all peers must sync up successfully to restore connectivity.  This is not recommended, but is an option for some BYOG hardware such as Araknis models.  See BYOG page for additional details.

 

(B) OmniNET Static IP/Port Forward IP required? NO

NO.  Only necessary if port forwarding is required for your customer.

 

BYOG Recommended scenario:  Modem in bridge mode with (A) ISP Static IP on BYOG.  Buy a (B) OmniNET Static IP if port forwarding is needed.

 

Having trouble deciding on a which subscription you need? 

Contact your OmniNET sales rep.  With a few questions, they can help you scope out your opportunities and right size them for the proper fit!

Have more questions? Submit a request
Powered by Zendesk