In version 3.5, the config.js file has been updated.
It now includes network interface configuration used by the system.
Current structure example:
// new version including net interfaces
export const backendUrl = 'http://192.168.1.1:8080';
// configure - network interfaces
export const ifaceTypes = {
enp4s0: 'LAN',
enp3s0: 'WAN',
enp7s0: 'DMZ',
tun0: 'VPN'
};
backendUrl Parameter #
export const backendUrl = 'http://192.168.1.1:8080';
Defines the address of the Suri Oculus backend server.
It is used for:
- performing REST API requests,
- retrieving events and statistics,
- managing rules and system settings.
If the server IP address or port changes, this value must be updated accordingly.
ifaceTypes Parameter #
export const ifaceTypes = {
enp4s0: 'LAN',
enp3s0: 'WAN',
enp7s0: 'DMZ',
tun0: 'VPN'
};
Defines logical types for network interfaces.
Format #
<interface_name>: <type>
Where:
interface_name— the system interface name (as shown byip a,nmcli, orifconfig)type— the logical network role of the interface
Recommended Types #
LAN— internal networkWAN— external interfaceDMZ— demilitarized zoneVPN— tunnel interfaces (e.g.,tun0)
Why It Is Needed #
Interface classification is used in the frontend for:
- proper network map visualization,
- separating internal and external traffic,
- filtering events by network zones,
- more accurate host behavior analysis,
- correct flow and statistics visualization.
Without explicitly defining interface types, the system cannot reliably determine whether traffic belongs to the internal network or the external perimeter.
Important Notes #
Interface names must exactly match the names configured in the operating system.
If the network configuration changes,
config.jsmust be updated.Interfaces not defined in
ifaceTypeswill be processed without zone assignment.
This update simplifies adapting Suri Oculus to different network architectures and improves traffic analysis accuracy and visualization clarity.