Skip to main content
All CollectionsWicket Installations
How To: Install a Dispel RHEL9+ Wicket — Full-Auto Install Guide
How To: Install a Dispel RHEL9+ Wicket — Full-Auto Install Guide

Welcome! The goal of this document is to walk through installing a Dispel Virtual RHEL Wicket.

Maya Shah avatar
Written by Maya Shah
Updated over 2 weeks ago

This guide is broken down into three sections:

  1. Building the RHEL 9+ VM

  2. Installing and running the script

  3. Verifying success

Building the VM

💡 To start this process, you will need:

  1. A RHEL dvd ISO file from RedHat.

  2. A RedHat account and registered license in order to create and register the VM.

  1. Create a RHEL 9+ virtual machine with:

    • Type/Architecture based on your device OS

    • (Min) 4 GB RAM

    • (Min) 30 GB storage

    • 2 vCPU

    • Two network interfaces, one with access to external internet and the other with access to the target internal network.

  2. Boot up the RHEL 9+ virtual machine.

Install and Run the Script

  1. Download the preconfigured configure_wicket.sh file provided by Dispel.

    1. Confirm the file was not corrupted during download using the Wicket Checksum Guide.

    2. Copy this script onto the RHEL VM.

    3. Ensure the interface names and gateway IPs are correct.

  2. Modify the script’s permissions to be executable.

    1. Open a terminal and elevate to root user by running sudo su.

    2. Change directory (cd) to where the configure_wicket.sh file exists in the VM.

    3. Run chmod +x configure_wicket.sh to allow the file to be executable.

  3. Run the Installation

    1. Run sudo ./configure_wicket.sh to run the script.

      1. If the RHEL VM is unregistered, the script will prompt for Red Hat account credentials to register the VM. Otherwise, the script is fully automated!

    2. Allow the script to run

Final Validations

  1. After the script runs, check for tun100 is up! and tun101 is up! messages.

  2. If both messages popped up, you can confirm the tunnels are up by running ifconfig.

    1. You should see both tun100 and tun101 interfaces up.

  3. Confirm tunnel stability by running:

    1. ping -t 10.100.1.1 (production tunnel), and

    2. ping -t 10.101.1.1 (support tunnel).

Did this answer your question?