Aug 05, 2020 
Support Center » Knowledgebase » Kerio Control » How do I backup the configuration
 How do I backup the configuration
Solution WinRoute Firewall

Backup and Import of Configuration

All WinRoute configuration data is stored in the following files under the same directory where WinRoute is installed:

winroute.cfg
Chief configuration file

users.cfg
Information about groups and user accounts.

logs.cfg
Log configurations

host.cfg
Preferences for backs-up of configuration, user accounts data, DHCP server database, etc.

ids.cfg
Stored for future use.

The data in these files are saved in XML format so that it can be easily modified by an advanced user or generated automatically using another application. Configuration back-up can be done by copying the files (for details see below).

Warning
Stop WinRoute Firewall Engine before handling configuration files as the files are retrieved during the WinRoute Firewall Engine startup only. Configuration files are saved after any modification is done and after the Engine is stopped. All modifications done during Engine performance will be overwritten by the configuration in the system memory when the Engine is stopped.

Configuration Recovery Performed Through Back-Up
To recover configuration through backed-up data (typically this need may arise when WinRoute is installed to a new workstation or when the operating system is being reinstalled), follow these steps:

Perform WinRoute installation on a required machine (refer to chapter Installation).

Stop WinRoute Firewall Engine.

Copy backed-up configuration files host.cfg, logs.cfg, users.cfg and winroute.cfg into the WinRoute installation directory

(typically C:\Program Files\Kerio\WinRoute Firewall).


Run WinRoute Firewall Engine.

At this stage, WinRoute detects the required configuration file. Within this process, unknown network interfaces (ones which are not defined in the winroute.cfg configuration file) will be detected in the system. Each network interface includes a unique (randomly generated) identifier in the operating system. It is almost not possible that two identifiers were identical.

To avoid setting up new interfaces and changing traffic rules, you can assign new identifiers to original interfaces in the winroute.cfg configuration file.

Stop WinRoute Firewall Engine.

Use a plaintext editor (e.g. Notepad) to open the winroute.cfg configuration file. Go to the following section:



Scan this section for the original adapter. Find an identifier for a new interface in the new adapter\'s log and copy it to the original adapter. Remove the new interface\'s log.

Example: Name of the local network interface is LAN. This network connection is labeled as Local area connection in the new operating system. Now, the following data can be found in the Interfaces section (only the essential parts are listed):


\DEVICE\
{7AC918EE-3B85-5A0E-8819-CBA57D4E11C7}

LAN
...


\DEVICE\
{6BF377FB-3B85-4180-95E1-EAD57D5A60A1}

Local Area Connection
...


Copy the Local Area Connection interface\'s identifier into the LAN interface. Remove the data for Local Area Connection (a relevant listitem section).

When all these changes are performed, the data in the configuration file relating to interface connected to the local network will be as follows:


\DEVICE\
{6BF377FB-3B85-4180-95E1-EAD57D5A60A1}

LAN
...

Save the winroute.cfg file and run WinRoute Firewall Engine.

Now, the WinRoute configuration is identical with the original WinRoute configuration on the prior operating system.


Article Details
Article ID: 41
Created On: Aug 11, 2004 10:03 AM

 This answer was helpful  This answer was not helpful

 Back
 Login [Lost Password] 
Email:
Password:
Remember Me:
 
 Search
 Article Options
Home | Register | Submit a Ticket | Knowledgebase | News | Downloads
Language: