HowTo

From Wiki@Commgate

Jump to: navigation, search

Contents

Upgrading From 3.x

Overview

This howto provides information on how to migrate mailboxes to CommGate Enterprise Server 2009 or later.

Upgrading from CommGate Professional 3.x

  • Before starting the upgrade from CommGate Professional 3.x, disable the SMTP Mail Server. This step will prevent inbound mail from disrupting the upgrade process.
  • Upgrade the CommGate system
  • On first boot, login to the system either from an attached keyboard/monitor or via a secure shell (SSH).
  • To start the mailbox conversion run the following command: imap2cyrus --dovecot
  • If you have large number of IMAP folders, the process can take a few hours.
  • Restart the SMTP Mail Server.

Migrating from a Remote IMAP Server

Here are the required steps for migrating mail to CommGate Enterprise Server 2009.

  • Create the User Accounts on the CommGate system. During this process, create a corresponding username/password text file on the CommGate system. This file is only used for migrating mail and can be deleted once migration is complete. The username/password file has the following format: 
username1|password1 \\
username2|password2 \\
username3|password3 \\
  • Make sure the IMAP mail server is up and running!
  • Run the imap2cyrus command with the following flags: 
   * --host: the hostname or IP of the old mail server
   * --port: the port for the mail server (defaults to 143)
   * --file: the name of the username/password file created earlier


Back to top

Resetting root Password

Overview

If your CommGate Server is no longer accessible since the root password has been lost, you can follow the following steps to reset the root password and regain access to the operating system. This may be necessary if:

  • your server has been compromised or hacked
  • your client has changed the password and forgotten it
  • your IT personnell have changed and did not leave you the password
  • the password has been mislaid

For security reasons this procedure cannot be carried out remotely. It must be done from the console while physically at the server.

Booting into single-user mode

In single-user mode, your computer boots to runlevel 1. Your local file systems are mounted, but your network is not activated. You have a usable system maintenance shell.

Warning! Do not use single-user mode if your file system cannot be mounted successfully. You cannot use single-user mode if the runlevel 1 configuration on your system is corrupted.

Use the following steps to boot into single-user mode:

  • At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu.
  • Select CommGate Professional Edition with the version of the kernel that you wish to boot and type a to modify the kernel arguments before booting.
  • Make sure that the cursor is at the end of the line and press the [Spacebar] and then type single. Press [Enter] to exit edit mode and begin booting up your system.
  • Once the operating system has loaded you will be at a prompt similar to the following:

>sh-3.00#


  • Type the command passwd and press [Enter]. You will see the following:

Changing password for user root New UNIX password:

Make sure that you set a strong password - i.e. it should not be based solely on a dictionary word and should contain numbers or other valid non-alpha characters.
  • You will then be asked to re-enter the password to confirm it and will subsequently receive a confirmation that the root password has been reset.
  • Now type in the command reboot and press [Enter] to restart your CommGate system.

Links

Original Redhat Documentation
Back to top

Creating Static Routes

Overview

This document describes how to configure a static route on a CommGate system.

Configuration

Static routes on a CommGate system are associated with a particular network interface. The route is then enabled/disabled when the particular network interface is enabled/disabled. Here is a simple scenario:

  • A CommGate LAN interface - eth1 - is configured with a 192.168.1.x network.
  • A private building-to-building wireless connection is setup via a wireless router. One side of the wireless router is connected to the CommGate LAN at 192.168.1.100. The other side of the wireless router is connected to a 192.168.99.x LAN.

In order for the CommGate gateway to be aware of the remote 192.168.99.x LAN, a static route must be configured. In this example, /etc/sysconfig/network-scripts/route-eth1 is created with the following:

192.168.99.0/24 via 192.168.1.100

After adding this static route, the route can be activated by re-enabling the CommGate LAN interface: /sbin/ifup eth1. If you are using Multi-WAN, then you also need to restart the firewall: /sbin/service firewall restart.

Additional LAN Networks

If you have other LAN networks connected behind your CommGate gateway, you need to configure these on the CommGate system. In version 4.1, you can add extra networks in /etc/system/network file (create the file if it does not exist). The format is similar to:

EXTRALANS="LAN1 LAN2 ... LANx"

For example:

EXTRALANS="192.168.4.0/24 192.168.5.0/24"

You may need to restart services (for example, the web proxy) after making this change.
Back to top

Retrieved from "http://wiki.commgate.net/index.php/HowTo"