In the “Providers and networks” module you can find the list of all external, internal and virtual networks connected to ICS CUBE. First, let’s see what is a routing object. This is:
When the network object is in the “closed” state, you can see only name, ip-address, status and network gateway reachability (for providers). When the object is highlighted by clicking on it, all the general parameters are shown. Every object can be edited or deleted using the buttons on the top panel, or the appropriate buttons near the name of the object. Besides, it can be turned off, if necessary, and then turned on again - it will remove the settings of the interface without the necessity to create an object. Also, the top panel contains the “Network settings wizard” button.
To add a new network, use the “Add” button, and choose the appropriate type of network.
Provider - in ICS CUBE it’s a WAN interface, which is responsible for NAT for the users of ICS CUBE.
When creating / editing a provider, if the “Keep UDP port” flag is set, the port of outgoing UDP traffic will not be replaced by ICS CUBE.
When being created, every provider is set one of the three possible priorities:
|main||All users traffic goes through this provider. If you have two or more internet channels, you can prioritize them all as “main”. Traffic that doesn’t go through proxy-server, will be divided between those channels using dynamic balancing, which allows to combine their bandwidth for better usage. The traffic that goes through proxy, will be routed via the “default” channel.|
|backup||Will not be used while the a main provider is working. If the main provider is down, the backup channel will come into its place.|
|additional||Will not be used except the cases, specified in the static routes in ICS CUBE.|
This scheme represents how three providers can be set in ICS CUBE. Main Provider 1 is the default gateway for all users and services. Provider 2 is not active while Provider 1 is up. Provider 3 is set up as the additional one. For certain user the static route is specified to use this provider.
The “External devices” tab is for adding Cisco routers.
The “Providers monitor” tab opens the module of the relevant service which monitor the providers state and switching between them. This service can be disabled, if necessary.
To open a provider settings window, you can use the “More…” button, or just click on its name in the list of the networks. A page with all this provider settings will be opened. On the first tab there will be the general status and information about its DynDNS-server.
What is the way ICS CUBE uses to check that the first provide became unavailable and it’s time to switch to the backup provider? You can set a criteria in the provider settings. To check it, you need to press the “More…” button on the provider. ICS CUBE can use the following criteria:
Also, availability via DynDNS can be an additional criteria.
In the “Settings” tab you can set the monitoring criteria and DynDNS parameters.
The “Rules” tab allows to set firewall rules for all the traffic that comes through this provider. You can create a deny or allow rule, route, and a speed limit. All rules that you set here, will be also in the list of the firewall itself.
In the “Log” tab you can find all system messages from the provider interface. Log is divided into pages, you can use buttons “Next” and “Back” to navigate, or you can enter the page number in the appropriate field.
This tab is most valued for the ppp-providers (PPPoE, PPTP), far less messages usually comes from static providers.
In the top right corner you can see the search line. You can use it to search through the log.
Log is always showing events of the current date. If you would like to check the log for the other day, you can pick a date from the calendar on the top left corner of the module.
Finally, the “Events” tab contains all the changes made for the provider. The functions are identical with the “Log” tab, but the interface is more user-friendly.
In the right part of the top panel there is a drop-down menu “Messages”, which allowed to filter the list of events using some specific criteria: system messages, service messages, errors, other messages.