Administrator's Guide - Kerio Software Archive
Administrator's Guide - Kerio Software Archive Administrator's Guide - Kerio Software Archive
Network interfaces connection will not be recovered. • In mode of on-demand dial (i.e. outside the intervals defined), connection will be recovered in response to the first request (i.e. packet sent from the local network to the Internet). Automatic hangup when idle Dial-ups are usually charged by connection time. When no data are transferred via the connection, there is no reason to keep the link up. Therefore, it is possible to set also idleness time after which the link will be hung-up automatically. For optimal idleness timeout length, it is necessary to know how the Internet connection is charged in the particular case. If the idleness timeout is too short, it may result in too frequent hanging up and dialing of the link which might be very uncomfortable and in certain cases even increase connection costs. Note: In the time interval where persistent connection of the link is set (see above), the idleness timeout is ignored. 5.6 Supportive scripts for link control (Windows) In some cases there is a special need of running a program or a script (execute a batch command) along with dialing or hanging up a link. This can be helpful for example if a special type of modem is used that must be controlled by a special program provided by its developers. Kerio Control allows launching any program or a command in the following situations: Before dial, After dial, Before hang-up or/and After hang-up. In case of the Before dial and Before hang-up options, the system does not wait for its completion after startup of the program. Figure 5.4 Dial-up — external commands Scripts for control of dial-ups must be located in the scripts subdirectory of the firewall’s installation directory, typically C:\Program Files\Kerio\WinRoute Firewall\scripts (Attention! This directory does not exist in the default installation — it is therefore necessary to create it!). 58
5.6 Supportive scripts for link control (Windows) The script names must have the following names: • BeforeDial.cmd — before dial, • AfterDial.cmd — after dial, • BeforeHangup.cmd — before hangup, • AfterHangup.cmd — after hangup. Each script first accepts the parameter of full name of the connection currently being dialed or hung up (name in the Kerio Control interface). Possible errors (e.g. if you allow an action but the particular script does not exist) are recorded in the Error log (see chapter 22.8). Note: If the name of the dial-up includes blanks, it will be automatically put in quotes upon the script call, which guarantees correct transmission of the full name in an only parameter of the script. However, it is more suitable to use names without blanks and diacritics for dial-ups. Interfaces in Kerio Control can be renamed any time needed. Warning: On Windows, Kerio Control is running as a service. Therefore, external applications and operating system’s commands will run in the background only (in the SYSTEM account). The same rules are applied for all external commands and external programs called by scripts. Therefore, it is not highly unrecommended to use interactive applications (i.e. applications with user interaction) for the actions described above. Interactive application would be running “in background” until the system restart or killing of the particular process. Under specific circumstances, such application might also block other dials or hang-ups. In the Software Appliance / VMware Virtual Appliance edition, supportive scripts for dial-ups are not supported. 59
- Page 7 and 8: 26 Technical support . . . . . . .
- Page 9 and 10: 8. Enable the intrusion prevention
- Page 11 and 12: 2.2 Conflicting software Warning: S
- Page 13 and 14: 2.3 System requirements met). 2.3 S
- Page 15 and 16: 2.4 Installation - Windows • TCP/
- Page 17 and 18: 2.4 Installation - Windows Warning:
- Page 19 and 20: 2.5 Initial configuration wizard (W
- Page 21 and 22: 2.6 Upgrade and Uninstallation - Wi
- Page 23 and 24: 2.7 Installation - Software Applian
- Page 25 and 26: 2.7 Installation - Software Applian
- Page 27 and 28: 2.10 Kerio Control Engine Monitor (
- Page 29 and 30: 2.11 The firewall’s console (Soft
- Page 31 and 32: 3.1 Kerio Control Administration we
- Page 33 and 34: 3.2 Administration Console - the ma
- Page 35 and 36: 3.3 Administration Console - view p
- Page 37 and 38: Chapter 4 License and Registration
- Page 39 and 40: 4.3 License information User is def
- Page 41 and 42: 4.4 Registration of the product in
- Page 43 and 44: 4.4 Registration of the product in
- Page 45 and 46: 4.4 Registration of the product in
- Page 47 and 48: 4.4 Registration of the product in
- Page 49 and 50: 4.6 Subscription / Update Expiratio
- Page 51 and 52: Chapter 5 Network interfaces Kerio
- Page 53 and 54: 5.3 Viewing and editing interfaces
- Page 55 and 56: 5.3 Viewing and editing interfaces
- Page 57: 5.5 Advanced dial-up settings Figur
- Page 61 and 62: 6.1 Persistent connection with a si
- Page 63 and 64: 6.1 Persistent connection with a si
- Page 65 and 66: 6.2 Connection with a single leased
- Page 67 and 68: 6.3 Connection Failover Advanced di
- Page 69 and 70: 6.3 Connection Failover Figure 6.8
- Page 71 and 72: 6.4 Network Load Balancing Note: 1.
- Page 73 and 74: 6.4 Network Load Balancing On the t
- Page 75 and 76: 6.4 Network Load Balancing Hint: Sp
- Page 77 and 78: Chapter 7 Traffic Policy Traffic Ru
- Page 79 and 80: 7.1 Network Rules Wizard Step 4 —
- Page 81 and 82: 7.1 Network Rules Wizard Figure 7.5
- Page 83 and 84: 7.1 Network Rules Wizard Note: In t
- Page 85 and 86: 7.3 Definition of Custom Traffic Ru
- Page 87 and 88: 7.3 Definition of Custom Traffic Ru
- Page 89 and 90: 7.3 Definition of Custom Traffic Ru
- Page 91 and 92: 7.3 Definition of Custom Traffic Ru
- Page 93 and 94: 7.3 Definition of Custom Traffic Ru
- Page 95 and 96: 7.3 Definition of Custom Traffic Ru
- Page 97 and 98: 7.4 Basic Traffic Rule Types Do not
- Page 99 and 100: 7.4 Basic Traffic Rule Types Figure
- Page 101 and 102: 7.4 Basic Traffic Rule Types Transl
- Page 103 and 104: 7.5 Policy routing 7.5 Policy routi
- Page 105 and 106: 7.6 User accounts and groups in tra
- Page 107 and 108: 7.7 Partial Retirement of Protocol
5.6 Supportive scripts for link control (Windows)<br />
The script names must have the following names:<br />
• BeforeDial.cmd — before dial,<br />
• AfterDial.cmd — after dial,<br />
• BeforeHangup.cmd — before hangup,<br />
• AfterHangup.cmd — after hangup.<br />
Each script first accepts the parameter of full name of the connection currently being dialed<br />
or hung up (name in the <strong>Kerio</strong> Control interface).<br />
Possible errors (e.g. if you allow an action but the particular script does not exist) are recorded<br />
in the Error log (see chapter 22.8).<br />
Note: If the name of the dial-up includes blanks, it will be automatically put in quotes upon the<br />
script call, which guarantees correct transmission of the full name in an only parameter of the<br />
script. However, it is more suitable to use names without blanks and diacritics for dial-ups.<br />
Interfaces in <strong>Kerio</strong> Control can be renamed any time needed.<br />
Warning:<br />
On Windows, <strong>Kerio</strong> Control is running as a service. Therefore, external applications and<br />
operating system’s commands will run in the background only (in the SYSTEM account). The<br />
same rules are applied for all external commands and external programs called by scripts.<br />
Therefore, it is not highly unrecommended to use interactive applications (i.e. applications<br />
with user interaction) for the actions described above. Interactive application would be<br />
running “in background” until the system restart or killing of the particular process. Under<br />
specific circumstances, such application might also block other dials or hang-ups.<br />
In the <strong>Software</strong> Appliance / VMware Virtual Appliance edition, supportive scripts for dial-ups<br />
are not supported.<br />
59
Change language