Skip to the content
support@suri-oculus.com
Monday - Friday 9:00 - 21:00
Suri-Oculus Project

Suri-Oculus Project

Suri-Oculus Project

Intelligent Security, Evolving Protection

Learn More
  • Homepage
  • About Suri-Oculus
  • Documentation
  • Downloads
  • Blog
  • News
  • FAQ
  • Contacts
  • Features
    • Suricata Dashboard
    • Suricata Management Console
    • Suricata AI Analysis
    • Suricata Flow Analytics
    • Suricata TLS Analysis
    • Suricata Log Viewer
    • Suricata on Low-Power Hardware
    • Suricata Rules Management
  • Donate

Introduction

  • Introduction

Log parser

  • Log Parser – daemonmove service (Version 3.0)
  • Log parser – daemonmove service

Installation and setup

  • Changes in config.js (Version 3.5)
  • Installation
  • Important Notice About Configuration

Backend

  • Suri Oculus Backend version 3.0
  • Backend
  • Config
    • Config file
  • Routes
    • Suri Oculus 3.0 – Routes
    • Backend Routes ver 2

Event Viewer

  • Changes in config.js (Version 3.5)
  • Events Viewer Tab

Rules Management

  • Rules management Tab

Threats Management

  • Oculus Tools
  • Threats Management Tab

Controls

  • Web Controls Tab

Statistic and Analytics

  • Web Statistic Tab

Chinese Project Overview

  • ? Suri Oculus 项目简介

Licensing

  • Suri Oculus Commercial License Agreement (EULA)
  • Licensing Overview
View Categories
  • Home
  • Documentation
  • Event Viewer
  • Changes in config.js (Version 3.5)

Changes in config.js (Version 3.5)

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 by ip a, nmcli, or ifconfig)
  • type — the logical network role of the interface

Recommended Types #

  • LAN — internal network
  • WAN — external interface
  • DMZ — demilitarized zone
  • VPN — 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.js must be updated.

  • Interfaces not defined in ifaceTypes will be processed without zone assignment.


This update simplifies adapting Suri Oculus to different network architectures and improves traffic analysis accuracy and visualization clarity.

 
 
 
Updated on February 17, 2026
Important Notice About Configuration
Table of Contents
  • backendUrl Parameter
  • ifaceTypes Parameter
    • Format
    • Recommended Types
  • Why It Is Needed
  • Important Notes

Intelligent Security, Evolving Protection

  • Contacts
  • Documentation
  • Downloads
  • Donate
  • News
  • Licensing Overviw
  • Blog
  • About
  • Suricata
  • FAQ

Chinese Technical Overview - ch.suri-oculus.com

Proudly powered by WordPress | Theme: Popularis Business