AIMdefense System Migration Guide

If DynDNS was used, please save the old data from the Config in a suitable location, as it will have to be set up again after the migration.
If the Unifi module is used, please read the Unifi update instructions first.

Step 1: Access the firewall via SSH.

Step 2: Log in.

Step 3: Select option 8.

Step 4: ‘ curl -sko migrate.sh https://pkg.aimdefense.tech/migrate.sh ‘ (do not pipe!).

Step 5: ‘ sh migrate.sh ‘ (do not pipe!).

Step 6: Confirm with y.

Step 7: Confirm with y and reboot.

Step 8: If a DynDNS was set up, please set it up again.

  1. Note: the DNS changes as follows:
    • dyn.tgfw.de becomes dyn.aimdefense.tech
    • icm.tgfw.de becomes aim.aimdefense.tech
    • “tg” becomes “s2f” (this includes user names)
  2. Examples:
    • tg-1-22.dyn.tgfw.de => s2f-1-22.dyn.aimdefense.tech
    • 33321-2.icm.tgfw.de => 33321-2.aim.aimdefense.tech

Step 9: To set up DynDNS with the new ddclient, see the DynDNS instructions (update until it installs itself, it can then be found under the path stored in the DynDNS instructions).

The migration log can be found under /root/migration_Timestamp.log.

Note for customers with the Tools module and an Advance license:

If all aliases (image on the left) – Path: Firewall → AIMdefense → settings – want to be set, the alias limit must be increased – path: Firewall → Settings → Advanced → Firewall Maximum Table Entries (screenshot below) – the default entry is empty (corresponds to 1000000) ← is not sufficient.

Technical note: In rare cases, it can happen that the login shell of existing users on AIMdefense can change to “nologin” during the update and they can no longer log in afterwards. If you are affected by this, please follow the steps below to resolve the problem:

Log in to the firewall with the “root” and change the shell for the affected users again.

Access -> Usermanagement ->Users -> Click on Edit for the affected user.