Situation
The router shall establish its WAN connection only if this is released using a key switch.
Solution
Another WAN chain will be added that is empty, i.e. that cannot establish a WAN connection. The empty WAN chain will be moved before the existing functional WAN chain, i.e. given higher priority. An event will be added that starts the functional WAN chain in case the input signals that the key switch is set to ON. Another event will be added that starts the empty WAN chain in case the input signals that the key switch is set to OFF.
It is prerequisite that you have access to the web interface of the router and the router has Internet access. It is recommended to commission the router as suggested in the Quick Installation Guide for this. It is also prerequisite that a key switch is connected to input IN1 of the router that connects input IN1 to GND if switched to position ON (input IN1 is high-active, i.e. changes to LOW if connected to GND).
-
Open web interface of the router using a browser: 192.168.1.1 [1]
-
In the WAN → WAN chains menu, add another WAN chain (). [2]
-
In the WAN → WAN chains menu, move the just added WAN chain before WAN chain wan1 added by the startup wizard (). [3]
-
In the Events → Events menu, add a new event for starting a WAN chain (). [4]
-
Edit the just added event ():
-
Description: IN1 LOW starts wan1
-
Event: Input state has changed
-
Input: 2.1 Changed to LOW
-
Action: Start WAN chain
-
Start WAN chain: wan1
-
-
Click on Save settings.
-
In the Events → Events menu, add a new event for starting a WAN chain (). [5]
-
Edit the just added event ():
-
Description: IN1 HIGH starts wan2
-
Event: Input state has changed
-
Input: 2.1 Changed to HIGH
-
Action: Start WAN chain
-
Start WAN chain: wan2
-
-
Click on Save settings.
-
Activate profile by clicking the blinking gear in the title bar ().
The settings become effective immediately. However, the router reacts only on the next change of the input condition and ignores the current condition. This also prevents that the router establishes a connection automatically without user intervention upon a power failure with key switch switched to ON. A connection will only be established if the operator turns the key switch OFF first and then ON again.
Troubleshooting
-
If no mail is received when expected, typos in the following settings may be the reason.
-
System time in router correct?
-
Timer setting correct?
-
E-mail address of recipient correct?
-
E-mail account settings correct?
-
-
It facilitates troubleshooting to have a look at the Modem, Netfilter and Events logs in the Status → Log view menu.
-
Message dispatch can also be triggered manually without having to wait for the expiry of the timer for troubleshooting in the Help → Debugging menu.
-
If e-mail dispatch works after disabling the netfilters in the Netfilter → IP filter menu, a faulty net filter setting is the reason.
Resources
The following ASCII configuration can be taken over using copy & paste. It must be observed that the individual parameters need to be adapted to the own application. Correct numbering must be observed for numbered parameters. Moreover, it must be observed that no existing parameters with the same number will be overwritten.
wan.wans.wan_chain.delete=all wan.wans.active=1 wan.wans.wan_chain.add wan.wans.wan_chain[1].name=wan2 wan.wans.wan_chain[1].lifetime_active=0 wan.wans.wan_chain.add wan.wans.wan_chain[2].name=wan1 wan.wans.wan_chain[2].lifetime_active=0 wan.wans.wan_chain[2].lifetime_wan=wan1 wan.wans.wan_chain[2].interface.add wan.wans.wan_chain[2].interface[1].interface=lte2 wan.wans.wan_chain[2].interface[1].check_interval=10 wan.wans.wan_chain[2].interface[1].check_fail_wan=wan1 wan.wans.wan_chain[2].interface[1].check_type=none wan.wans.wan_chain[2].interface[1].link_port=1.1 events.event_config.event.add events.event_config.event[3].active=1 events.event_config.event[3].description=IN1 LOW starts wan1 events.event_config.event[3].event_type=ev_input events.event_config.event[3].event_input_name=2.1 events.event_config.event[3].event_input_change=to_low events.event_config.event[3].event_action_type=act_wan_chain events.event_config.event[3].event_action_wan_chain=wan1 events.event_config.event.add events.event_config.event[4].active=1 events.event_config.event[4].description=IN1 HIGH starts wan2 events.event_config.event[4].event_type=ev_input events.event_config.event[4].event_input_name=2.1 events.event_config.event[4].event_input_change=to_high events.event_config.event[4].event_action_type=act_wan_chain events.event_config.event[4].event_action_wan_chain=wan2
Back to the Configuration Guides for icom OS Smart Devices
Back to overview