Skip to main content

FLUX Test

Before installing Medulla, it is essential to verify the communication between:

  • Your Medulla server,
  • Your relay (if applicable),
  • Your client machines.

To do this, we provide a testing procedure that includes dedicated scripts. All data flows must be successfully validated to ensure a smooth deployment and optimal operation of Medulla.

Please feel free to contact us for any assistance or clarification regarding these tests.

The scripts are available for download here:

-----------------------------------------------------------

Test Prerequisites

Before you begin, make sure you have downloaded the test scripts provided above and prepared the machines:

  1. On the Linux servers (Medulla & Relai):

    • Install the necessary tools: sudo apt update && sudo apt install netcat-openbsd mariadb-client ldap-utils

    • Make the scripts executable:

      chmod +x listen_ports_debian.sh medulla_connection_check.sh medulla_relay_connection_check.sh
dos2unix *.sh  # If necessary

  2. On the Windows client machine with the Medulla agent:

    • Right-click on the script, click Properties, check the box to allow the script to run, and confirm.

    image.png

     

    • Allow PowerShell scripts to run:

    Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

    # Answer "Yes for all" (Y or T) if prompted

    For PowerShell v7.5.4: 

    There is no need to unblock the script. You must run the command shown above.

    It will ask if you want to allow the publisher of the script; simply confirm by clicking R or A.

    image.png

1. Test Medulla Server <-> Medulla Relay

Verify communication between the main server and the relay.

Direction: Server to Relay

  • A. On the Relay Server (Destination): Start listening on the ports. (Do not perform this step if Medulla is already installed or if you are using SaaS)

    ./listen_ports_debian.sh -r

  • B. On the Medulla Server (Source): Run the connection test.

    ./medulla_connection_check.sh -r <RELAY_IP>

Direction: Relay to Server

  • C. On the Medulla Server (Destination): Start listening on the ports. (Do not perform this step if Medulla is already installed or if you are using SaaS)

    ./listen_ports_debian.sh -m

  • D. On the Relay Server (Source): Run the connection test.

    ./medulla_relay_connection_check.sh -m <MEDULLA_IP>

2. Medulla Server <-> Windows Client Test

Verify direct communication between the server and client workstations.

Direction: Server to Client Workstation 

  • A. On the Client Workstation (Destination): Start listening. 

    .\listen_ports_windows.ps1

  • B. On the Medulla Server (Source): Run the test to the client’s IP address.

    ./medulla_connection_check.sh -c client.example.com

Direction: Client Workstation to Server

  • C. On the Medulla Server (Destination): Start listening. (Do not perform this step if Medulla is already installed or if you are using SaaS)

    ./listen_ports_debian.sh -m

  • D. On the Client Workstation (Source): Run the test to the server's IP address.

    .\windows_connection_check_signed.ps1 -Target <SERVER_IP> -Mode pulse

A log file has been created (in the location where you are running the script) that summarizes several tests, named: LOG_Test_Flux.txt

If you encounter permission errors when creating the log file, try placing the scripts in the user’s Downloads folder, or grant the windows_connection_check.ps1 script permission to create a file in the same location.

3. Medulla Relay <-> Windows Client Workstation Test

Only if the workstations need to communicate via a relay.

Direction: Relay to Client Workstation

  • A. On the Client Workstation (Destination): Start listening.


    .\listen_ports_windows.ps1

  • B. On the Relay Server (Source): Run the test to the workstation’s IP address.

    ./medulla_relay_connection_check.sh -c client.example.com

Direction: Client Workstation to Relay 

  • C. On the Relay Server (Destination): Start listening. (Do not perform this step if Medulla is already installed or if you are using SaaS)

    ./listen_ports_debian.sh -r

  • D. On the Client Workstation (Source): Run the test to the relay's IP address.

    .\windows_connection_check_signed.ps1 -Target <RELAY_IP> -Mode relay

A log file has been created (in the location where you are running the script) that summarizes several tests, named:LOG_Test_Flux.txt

If you encounter permission errors after creating the log file, try placing the scripts in the user’s Downloads folder, or grant the windows_connection_check.ps1 script permission to create a file in the same location.

4. Medulla Relay DMZ <-> Windows Mobile Client Test

Verification of direct communication between the server and client workstations.

(Mobile clients can only be reached on ports 5222 and 22)

Direction: Client Workstation to Server

  • A. On the Medulla DMZ Server (Destination): Start listening. (Do not perform this step if Medulla is already installed or if you are using SaaS)

    ./listen_ports_debian.sh -r

  • B. On the Mobile Client (Source): Run the test to the server’s IP address.

    .\windows_connection_check_signed.ps1 -Target <SERVER_IP> -Mode relay

5. Test server destined for Medulla -> Your GLPI server

Verify direct communication between the server and your GLPI server.

(Requires the mariadb-client package: apt install mariadb-client)

  • A. On the Medulla server: Run the test against the external GLPI database.

    ./check_connection_glpi.sh DB_FQDN DB_USERNAME DB_PASSWORD DB_NAME_GLPI

6. Server Test for Medulla -> Your LDAP Server

Verify direct communication between the server and your LDAP server.

(Requires the ldap-utils package: apt install ldap-utils)

  • A. On the Medulla server: Run the test against the external LDAP server.

    ./check_connection_ldap.sh HOST PORT 'BIND_DN' 'PASSWORD' 'BASE_DN'

Back to top