The indoor master router is all important to the way our system works. It “phones home” to our datacentre where our monitoring/management systems are located. From here the unit will be provided with an IP address from our network, a private IP address unless the end user has chosen to receive a public one. This network connection allows us to manage, monitor and configure the device and subsequent access points and outdoor units remotely.
One of the primary features of the system is the way that we can load balance the client’s data traffic across multiple outdoor units and/or and auxiliary WAN connection automatically. This programming has been done by default and accounts for HTTPS (SSL) sites to be locked by connection to whichever outgoing path the traffic originates on. This is essential for banking websites to as the connection through a browser to an encrypted website will fail should the site sense the data is coming via more than one originating path.
Our system uses a sophisticated routing table with automatic failover to sense which WAN connections are live and balances traffic evenly across all available routes. Further bespoke configuration changes can be made to force traffic through a particular interface should the client desire.
All traffic for a VoIP phone system may need to use a particular gateway service provided by the carrier.
Telemetry data traffic that’s recognised by a monitoring centre to always originate from a particular IP address.
Inbound Public IP address services for remote monitoring or CCTV traffic can be forced to always use the same public IP.
One of the unique characteristics of our Public IP address service is that it is network independent. It will re-establish the connection to our datacentre using whatever WAN connection is working on the master router. In this way the network will self-heal maintaining the same inbound public IP address for the client’s system regardless of the connection method used, 1- 5 sims or AUX WAN.
All devices are locked down to prevent local access to configuration. The only way to make changes to the system is via our portal management system. This in turn is only available if the device is either using one of our InterWiz supplied EE data SIMs or if the client has purchased an operating license for the facility. Any public IP addresses are only maintained to the device if the user pays for this add on service in addition to the license or InterWiz EE SIM service.
Currently the services that the portal will allow configuration of are:
LAN IP Address range
DHCP server settings
Wireless WPA2 security key
With future development of the Management system we are going to introduce:
Inbound firewall rules
DHCP lease reservations
Central Wireless controller for multiple AP’s
Additional Bespoke services that we can offer are:
Guest network configurations
Multiple Networks including Vlan configurations
Self-service guest WiFi portal with optional PayPal integration.