How to split access to WMS and Legacy Collaboration
This guide provides instructions how to split access to WMS and Legacy Collaboration interfaces based on IP addresses.
Created: June 2026
Permalink: https://wildix.atlassian.net/wiki/x/AYDSi
Introduction
This feature allows administrators to restrict access to the WMS and the Legacy Collaboration interface to specific IP addresses. By configuring these restrictions, you can ensure that the management interface is only accessible from an administrative network while keeping the Legacy Collaboration interface available for users on a separate network or interface.
Step 1. Get IP Addresses
Open your terminal and log in as a root admin
Open the terminal and run the following command to see available interfaces:
ifconfigNote down the IP addresses for WMS and Legacy Collaboration.
Step 2. Create the Restriction Environment File
You need to create a configuration file that defines which IP address maps to which service.
Create and open the restriction file:
nano /rw2/etc/nginx/interface-restriction.envAdd the IP addresses in the following order:
Line 1: WMS IP address
Line 2: Collaboration IP address
Example:
MGMT_IP=192.168.1.10
COLLAB_IP=192.168.1.20Once configured, access to WMS will be available for users with 192.168.1.10 IP address. At the same time, these users will not be able to access Legacy Collaboration. And users with 192.168.1.20 IP address will be able to access Legacy Collaboration only and will get the access denied notification when trying to reach WMS interface:
Note: Only one IP address can be entered per line.
Save the changes
Step 3. Create the Configuration File
The feature is implemented via a custom configuration script:
Dowload the file
Create the directory:
mkdir -p /rw2/etc/nginx/app/Create the configuration file
nano /rw2/etc/nginx/app/interface-restriction.confCopy the data provided in the file you’ve downloaded and paste it in the configuration file
Save the changes
Reload the service
nginx -s reload