Overview

In some cases, the factory-reset of the box does not help in resolving network misconfiguration caused by broken network access. This happens due to configuration mistakes or hardware issues (mostly when migrating from another box).

This article explains how to modify the Kerio Control configuration via serial console using two methods.

Process

Method 1

1. Connect via serial console to the Kerio Control box.
2. Execute the below command:
   
   

   cd /opt/kerio/winroute

3. Make the system read/write by executing the below commands:
   
   

   mount -o rw,remount /

4. Locate the Interfaces_v2 section. It should appear as shown below:
   
   

   <list name="Interfaces_v2">

5. Find the necessary interface and modify the following variables:
   
   

   <variable name="Mode">Manual</variable>
   <variable name="IPAddress">0.0.0.0</variable>
   <variable name="Mask">0.0.0.0</variable>
   <variable name="AutodetectGateway">0</variable>
   <variable name="Gateway">0.0.0.0</variable>

6. Replace IPAddress, Mask, and Gateway if needed.
7. (Optional) If you need to change a particular traffic rule, edit the following section: 
   
   

   <list name="TrafficRules_v2" identityCounter="112">

8. Save the file and restart Kerio Control by running the following command:
   
   

   /etc/boxinit.d/60winroute restart

Method 2

1. Connect to the Kerio Control Device via console.
2. Make the system read/writable:
   
   

   mount -o rw,remount /

3. Navigate to the /var/winroute folder:
   
   

   cd /var/winroute

4. Create a new file named winroute.cfg.test in /var/winroute:
   
   

   touch winroute.cfg.test

5. Have a backup file saved via MyKerio or locally.
6. Unzip .tar.gz to the .tar folder.
   
   
   
   
7. Unzip the .tar file to the ControlBackup folder.
   
   
   
   
8. Open the ControlBackup folder and copy the content of winroute.cfg and paste it in the new file created (winroute.cfg.test)
   
   For instance:
   
   
   
   
9. Rename the configuration file to winroute.cfg:

   mv winroute.cfg.test winroute.cfg

10. Restart Kerio Control using the /etc/boxinit.d/60winroute restart command.

Confirmation

The box should be accessible now, and Kerio Control Webadmin loads correctly.