03a Areg SDK Multitarget Router (mtrouter)

Areg SDK Multitarget Router (mtrouter)

The Multitarget Router enables inter-process and networked communication between Service Provider and Consumer nodes in distributed Areg SDK applications.

Tip

For single-process multithreading applications, mtrouter is not required. See Quick Project Setup for creating projects.

Quick Start

Run mtrouter in 10 Seconds

Linux/macOS:

cd areg-sdk
./product/build/gnu-g++/linux-64-x86_64-release-shared/bin/mtrouter.elf --console

Windows:

cd areg-sdk
.\product\build\msvc-v143\windows_nt-x64-release\bin\mtrouter.exe --console

Expected output:

Areg Multi-target Message Router console application ...
---------------------------------------------------------------------------------------------
Send data with the rate:    0.00  Bytes / sec.
Recv data with the rate:    0.00  Bytes / sec.

Type '-q' or '--quit' to quit the application ...:

Test connection: Run executable of any IPC example, for example 15_pubclient.exe, and type -n in mtrouter console to see connected clients like this:

Areg Multi-target Message Router console application ...
---------------------------------------------------------------------------------------------
Send data with the rate:    0.00  Bytes / sec.
Recv data with the rate:    0.00  Bytes / sec.

Type '-q' or '--quit' to quit the application ...:

---------------------------------------------------------------------------------------------
   Nr. |  Instance ID  |  Bitness  |  Name
---------------------------------------------------------------------------------------------
    1. |          256  |    64     |  15_pubclient.exe
    2. |          257  |    64     |  15_pubservice.exe
---------------------------------------------------------------------------------------------

Type -q to quit

↑ Back to top ↑

Overview

What is mtrouter?

The Multitarget Message Router (mtrouter) is a message routing service that:

✅ Routes messages between distributed processes
✅ Enables inter-process communication (IPC)
✅ Supports network communication (TCP/IP)
✅ Manages service discovery
✅ Handles multiple client connections

When Do You Need mtrouter?

Application Type	Requires mtrouter	Communication
Multithreading (single process)	❌ No	In-process
Multiprocessing (same machine)	✅ Yes	Inter-process (IPC)
Distributed (network)	✅ Yes	Network (TCP/IP)

Important

Without mtrouter, multiprocessing applications cannot communicate with each other. They will run as standalone multithreading applications where only internal (local) services work within each process, but external (public) services remain inaccessible to other processes.

Architecture

Without mtrouter (multithreading):

┌────────────────────────────┐
│     Single Process         │
│  ┌──────────┐ ┌──────────┐ │
│  │ Provider │ │ Consumer │ │
│  └──────────┘ └──────────┘ │
└────────────────────────────┘

With mtrouter (multiprocessing/distributed):

┌─────────────┐         ┌──────────┐         ┌─────────────┐
│  Provider   │────────►│ mtrouter │◄────────│  Consumer   │
│  Process    │         │ (Router) │         │  Process    │
└─────────────┘         └──────────┘         └─────────────┘

Deployment Options

Console Application:

Run manually for development/testing
Easy debugging and monitoring
Stop with -q or --quit

System Service:

Automatic startup at boot
Runs in background
Managed by OS (systemd/Windows Services)

↑ Back to top ↑

Installation

Option 1: Use from Build Directory

After building Areg SDK, mtrouter is available in the build output directory.

Default build paths:

Linux:

./product/build/gnu-g++/linux-64-x86_64-release-shared/bin/mtrouter.elf

Windows:

.\product\build\msvc-v143\windows_nt-x64-release\bin\mtrouter.exe

Note

Build output paths follow pattern: product/build/<compiler>/<platform>-<arch>-<config>/bin/

Option 2: Install via CMake

Install Areg SDK system-wide:

# Configure and build
cmake -B ./build
cmake --build ./build

# Install (requires sudo on Linux)
sudo cmake --install ./build

Default installation locations:

Linux:

Executables: /usr/local/tools/areg/mtrouter
Libraries: /usr/local/lib/libareg.so
Headers: /usr/local/include/areg/
Config: /usr/local/share/areg/areg.init
Service files: /usr/local/share/areg/service/

Windows:

Executables: C:\Program Files\areg\tools\areg\mtrouter.exe
Libraries: C:\Program Files\areg\bin\areg.dll
Headers: C:\Program Files\areg\include\areg\
Config: C:\Program Files\areg\share\areg\areg.init
Service files: C:\Program Files\areg\share\areg\service\

Custom installation prefix:

cmake --install ./build --prefix /opt/areg

What gets installed:

Libraries:

areg - Core framework library
aregextend - Extended utilities library
areglogger - Log observer API library

Executables:

mtrouter - Message router
logcollector - Log collector service
logobserver - Log observer application

Tools:

codegen.jar - Service interface code generator
project-setup.sh / project-setup.bat - Project creation scripts

Configuration:

areg.init - Default configuration file
Service installation scripts (Linux/Windows)

Development files:

Headers (.h, .hpp)
CMake configuration files
pkg-config files (.pc)

↑ Back to top ↑

Running as Console Application

Basic Usage

From build directory:

Linux/macOS:

./product/build/gnu-g++/linux-64-x86_64-release-shared/bin/mtrouter.elf --console

Windows:

.\product\build\msvc-v143\windows_nt-x64-release\bin\mtrouter.exe --console

From installed location:

Linux:

/usr/local/tools/areg/mtrouter --console

Windows:

& "C:\Program Files\areg\tools\areg\mtrouter.exe" --console

Expected output:

Areg Multi-target Message Router console application ...
---------------------------------------------------------------------------------------------
Send data with the rate:    0.00  Bytes / sec.
Recv data with the rate:    0.00  Bytes / sec.

Type '-q' or '--quit' to quit the application ...:

Console Commands

While mtrouter is running, type commands starting with - (short) or -- (long):

Command	Alias	Description
`--help`	`-h`	Display command list
`--instances`	`-n`	Show connected clients
`--pause`	`-p`	Pause message routing
`--restart`	`-r`	Restart all connections
`--quit`	`-q`	Stop mtrouter
`--silent`	`-t`	Toggle silent mode (hide data rates)
`--verbose`	`-v`	Toggle verbose mode (show data rates)

Example - Check connected clients:

Type --instances or -n:

Areg Multi-target Message Router console application ...
---------------------------------------------------------------------------------------------
Send data with the rate:    0.00  Bytes / sec.
Recv data with the rate:    0.00  Bytes / sec.

Type '-q' or '--quit' to quit the application ...:

---------------------------------------------------------------------------------------------
   Nr. |  Instance ID  |  Bitness  |  Name
---------------------------------------------------------------------------------------------
    1. |          256  |    64     |  provider.exe
    2. |          257  |    64     |  consumer.exe
---------------------------------------------------------------------------------------------

Verbose Mode

Toggle verbose mode:

Type --verbose or -v:

When verbose ON (default):

Send data with the rate:    1.23  Bytes / sec.
Recv data with the rate:    0.87  Bytes / sec.

When verbose OFF (silent):

Type '-q' or '--quit' to quit the application ...:

Note

Verbose mode shows data transfer rates, not individual messages.

Custom Configuration

Load custom configuration file:

./mtrouter.elf --console --load="./config/custom.init"

↑ Back to top ↑

Running as System Service

Linux Service (systemd)

Step 1: Prepare Files

Option A: Install via CMake (recommended)

# Install Areg SDK system-wide
sudo cmake --install ./build

# Service file location
ls -l /usr/local/share/areg/service/mtrouter.service

Option B: Manual installation

# Copy executable
sudo cp ./product/build/gnu-g++/linux-64-x86_64-release-shared/bin/mtrouter.elf /usr/local/bin/mtrouter

# Copy library (if shared build)
sudo cp ./product/build/gnu-g++/linux-64-x86_64-release-shared/lib/libareg.so /usr/lib/libareg.so

# Make executable
sudo chmod +x /usr/local/bin/mtrouter

# Update library cache
sudo ldconfig

Verify:

/usr/local/bin/mtrouter --help

Step 2: Install Service File

If installed via CMake:

sudo cp /usr/local/share/areg/service/mtrouter.service /etc/systemd/system/

If manual installation:

sudo cp ./framework/mtrouter/resources/mtrouter.service /etc/systemd/system/

Or create manually:

sudo nano /etc/systemd/system/mtrouter.service

Content:

[Unit]
Description=Areg Multitarget Router Service
After=network.target

[Service]
Type=simple
ExecStart=/usr/local/bin/mtrouter --service
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

Important

The --service flag is required for service mode.

Step 3: Enable and Start Service

Reload systemd:

sudo systemctl daemon-reload

Enable (start at boot):

sudo systemctl enable mtrouter.service

Expected output:

Created symlink /etc/systemd/system/multi-user.target.wants/mtrouter.service → /etc/systemd/system/mtrouter.service

Start service:

sudo systemctl start mtrouter.service

Verify status:

sudo systemctl status mtrouter.service

Expected output:

● mtrouter.service - Areg Multitarget Router Service
     Loaded: loaded (/etc/systemd/system/mtrouter.service; enabled)
     Active: active (running) since Mon 2026-01-27 10:30:00 UTC; 5s ago
   Main PID: 12345 (mtrouter)
      Tasks: 3
     Memory: 8.5M
     CGroup: /system.slice/mtrouter.service
             └─12345 /usr/local/bin/mtrouter --service

Step 4: Manage Service

Stop service:

sudo systemctl stop mtrouter.service

Restart service:

sudo systemctl restart mtrouter.service

Disable (don't start at boot):

sudo systemctl disable mtrouter.service

View logs:

sudo journalctl -u mtrouter.service -f

Expected log output:

Jan 27 10:30:00 hostname mtrouter[12345]: Router service started
Jan 27 10:30:01 hostname mtrouter[12345]: Listening on 127.0.0.1:8181

↑ Back to service setup ↑

Windows Service

Step 1: Prepare Binaries

Option A: Install via CMake (recommended)

# Open PowerShell as Administrator
# Install Areg SDK
cmake --install .\build --prefix "C:\Program Files\areg"

# Service installation script location
dir "C:\Program Files\areg\share\areg\service\mtrouter.service.install.bat"

Option B: Manual installation

# Create installation directory
New-Item -Path "C:\Program Files\areg\tools\areg" -ItemType Directory -Force

# Copy binaries
Copy-Item .\product\build\msvc-v143\windows_nt-x64-release\bin\mtrouter.exe "C:\Program Files\areg\tools\areg\"
Copy-Item .\product\build\msvc-v143\windows_nt-x64-release\bin\areg.dll "C:\Program Files\areg\tools\areg\"

Verify:

& "C:\Program Files\areg\tools\areg\mtrouter.exe" --help

Step 2: Install Service

Open PowerShell as Administrator:

Right-click PowerShell → Run as Administrator

Option A: Using installation script (if CMake installed)

cd "C:\Program Files\areg\share\areg\service"
.\mtrouter.service.install.bat

Option B: Using mtrouter executable

cd "C:\Program Files\areg\tools\areg"
.\mtrouter.exe --install

Expected output:

Service 'Areg Multitarget Router Service' installed successfully

Step 3: Start Service

Using Services GUI:

Press Win + R, type services.msc, press Enter
Find Areg Multitarget Router Service
Right-click → Start

Using PowerShell:

Start-Service "mtrouter.service"

Verify status:

Get-Service "mtrouter.service"

Expected output:

Status   Name               DisplayName
------   ----               -----------
Running  mtrouter.service   Areg Multitarget Router Service

Step 4: Configure Startup Type

Automatic startup:

Set-Service "mtrouter.service" -StartupType Automatic

Manual startup:

Set-Service "mtrouter.service" -StartupType Manual

Step 5: Manage Service

Stop service:

Stop-Service "mtrouter.service"

Restart service:

Restart-Service "mtrouter.service"

Uninstall service:

Option A: Using uninstall script

cd "C:\Program Files\areg\share\areg\service"
.\mtrouter.service.uninstall.bat

Option B: Using mtrouter executable

# Stop first
Stop-Service "mtrouter.service"

# Uninstall
cd "C:\Program Files\areg\tools\areg"
.\mtrouter.exe --uninstall

Expected output:

Service 'Areg Multitarget Router Service' uninstalled successfully

View service logs:

Open Event Viewer: Win + R → eventvwr.msc

Navigate: Windows Logs → Application

Filter for Source: mtrouter

↑ Back to service setup ↑

Configuration

Configuration File Location

Default: areg.init in Areg SDK resources directory

Installed location:

Linux: /usr/local/share/areg/areg.init
Windows: C:\Program Files\areg\share\areg\areg.init

Custom location:

mtrouter --load="./path/to/config.init"

Configuration Format

Settings use key-value pairs:

Syntax:

section::(module|*)::property[::(position|*)] = value

section - Configuration section (e.g., router, log)
module - Module name or * for all modules
property - Property name
value - Property value

Router Configuration Section

Complete example:

# Router service configuration
router::*::service          = mtrouter      # Service name
router::*::connect          = tcpip         # Protocol (tcpip only)
router::*::enable::tcpip    = true          # Enable TCP/IP
router::*::address::tcpip   = 127.0.0.1     # Listen address
router::*::port::tcpip      = 8181          # Listen port

Configuration breakdown:

Property	Default	Description
`router::*::service`	`mtrouter`	Router process name
`router::*::connect`	`tcpip`	Communication protocol
`router::*::enable::tcpip`	`true`	Enable/disable TCP/IP
`router::*::address::tcpip`	`127.0.0.1`	IP address to bind
`router::*::port::tcpip`	`8181`	Port number

Common Configurations

1. Local development (default):

router::*::address::tcpip   = 127.0.0.1
router::*::port::tcpip      = 8181

Use case: Single machine development

2. Network access (all interfaces):

router::*::address::tcpip   = 0.0.0.0
router::*::port::tcpip      = 8181

Use case: Accept connections from any network interface

3. Specific network interface:

router::*::address::tcpip   = 192.168.1.100
router::*::port::tcpip      = 8181

Use case: Bind to specific network interface

4. Custom port:

router::*::address::tcpip   = 127.0.0.1
router::*::port::tcpip      = 9090

Use case: Avoid port conflicts

5. Application-specific routing:

# Default for all applications
router::*::address::tcpip   = 127.0.0.1
router::*::port::tcpip      = 8181

# Specific configuration for 'myapp'
router::myapp::address::tcpip = 192.168.1.50
router::myapp::port::tcpip    = 9090

Use case: Different applications connect to different routers

Disable Logging

Add to configuration:

log::mtrouter::scope::*     = NOTSET

Or disable all logs:

log::*::scope::*            = NOTSET

Tip

For detailed configuration syntax, see Persistence Syntax Guide.

↑ Back to top ↑

Command Reference

Command-Line Options

Options used when starting mtrouter:

Option	Alias	Platform	Description
`--console`	`-c`	All	Run as console application
`--help`	`-h`	All	Display help message
`--install`	`-i`	Windows	Install as Windows service
`--load`	`-l`	All	Load custom configuration file
`--service`	`-s`	Linux	Run as Linux service
`--silent`	`-t`	All	Run without showing data rates
`--uninstall`	`-u`	Windows	Uninstall Windows service
`--verbose`	`-v`	All	Show data transfer rates

Examples:

# Console with default config
mtrouter --console

# Console with custom config
mtrouter -c -l="./my-config.init"

# Silent console mode (no data rates)
mtrouter -c -t

# Verbose console mode (show data rates)
mtrouter -c -v

# Linux service
mtrouter --service

# Windows service install
mtrouter.exe --install

Interactive Console Commands

Commands available while mtrouter runs in console mode (must start with - or --):

Command	Alias	Description
`--help`	`-h`	Display command list
`--instances`	`-n`	Show connected clients
`--pause`	`-p`	Pause message routing
`--restart`	`-r`	Restart all connections
`--quit`	`-q`	Stop mtrouter
`--silent`	`-t`	Toggle silent mode (hide data rates)
`--verbose`	`-v`	Toggle verbose mode (show data rates)

Usage: Type the command (e.g., -n or --instances) and press Enter.

↑ Back to top ↑

Application Integration

Connecting to mtrouter

Applications connect to mtrouter by initializing the Application class with router client enabled.

Important

For inter-process communication, mtrouter must be running. Start mtrouter before or after starting provider and consumer processes. There is no required startup order - applications will automatically connect when mtrouter becomes available. For network communication, configure mtrouter address in application configuration file (areg.init). By default, applications communicate via localhost.

Basic Connection

Minimal setup:

#include "areg/appbase/Application.hpp"

int main()
{
    // Initialize with router client enabled
    Application::initApplication(
        true,   // Enable logging
        true,   // Enable service manager
        true,   // Enable router client ← Important
        true,   // Enable timer manager
        true    // Enable watchdog manager
    );
    
    // Load service model
    Application::loadModel("MyModel");
    
    // Wait for application quit signal
    Application::waitAppQuit(NECommon::WAIT_INFINITE);
    
    // Cleanup
    Application::releaseApplication();
    return 0;
}

Note

The third parameter (true) enables router client connection.

Connection with Custom Configuration

Specify configuration file:

#include "areg/appbase/Application.hpp"

int main()
{
    // Initialize with custom configuration
    Application::initApplication(
        true,   // Enable logging
        true,   // Enable service manager
        true,   // Enable router client
        true,   // Enable timer manager
        true,   // Enable watchdog manager
        "./config/myapp.init",  // Configuration file
        nullptr // Logging configuration (null = use config file)
    );
    
    Application::loadModel("MyModel");
    Application::waitAppQuit(NECommon::WAIT_INFINITE);
    Application::releaseApplication();
    return 0;
}

Application Configuration

Create myapp.init configuration:

# Application router connection settings
router::myapp::service          = mtrouter
router::myapp::connect          = tcpip
router::myapp::enable::tcpip    = true
router::myapp::address::tcpip   = 127.0.0.1    # mtrouter address
router::myapp::port::tcpip      = 8181         # mtrouter port

Or use wildcard for all applications:

# Global router settings (all applications)
router::*::service          = mtrouter
router::*::connect          = tcpip
router::*::enable::tcpip    = true
router::*::address::tcpip   = 127.0.0.1
router::*::port::tcpip      = 8181

Connection Verification

Check connection in application code:

#include "areg/appbase/Application.hpp"
#include "areg/base/NEUtilities.hpp"

int main()
{
    Application::initApplication(true, true, true, true, true);
    
    // Wait for router connection
    NEUtilities::waitTimeout(1000); // Wait 1 second
    
    // Check if connected
    if (Application::isRouterConnected())
    {
        std::cout << "Connected to mtrouter" << std::endl;
    }
    else
    {
        std::cout << "Not connected to mtrouter" << std::endl;
    }
    
    Application::loadModel("MyModel");
    Application::waitAppQuit(NECommon::WAIT_INFINITE);
    Application::releaseApplication();
    return 0;
}

Network Example

Distributed system setup:

Machine 1 (192.168.1.100) - mtrouter:

# config/router.init
router::*::address::tcpip = 192.168.1.100
router::*::port::tcpip    = 8181

# Start router
./mtrouter --console --load="config/router.init"

Machine 2 (192.168.1.101) - Provider:

# provider.init
router::provider::address::tcpip = 192.168.1.100
router::provider::port::tcpip    = 8181

Machine 3 (192.168.1.102) - Consumer:

# consumer.init
router::consumer::address::tcpip = 192.168.1.100
router::consumer::port::tcpip    = 8181

↑ Back to top ↑

Troubleshooting

mtrouter Won't Start

Problem: mtrouter exits immediately or fails to start.

Solution:

1. Check if port is already in use:

Linux:

sudo netstat -tlnp | grep 8181

Windows:

netstat -ano | findstr 8181

If port is in use: Kill the process or change port in configuration

2. Check configuration file:

# Verify file exists
ls -l areg.init

# Check syntax
cat areg.init | grep router

3. Check permissions:

# Make executable
chmod +x mtrouter.elf

# Check file permissions
ls -l mtrouter.elf

Port Already in Use

Problem: "Error: Address already in use"

Solution:

Find process using port:

Linux:

sudo lsof -i :8181

Windows:

netstat -ano | findstr :8181

Kill process:

Linux:

sudo kill -9 <PID>

Windows:

taskkill /PID <PID> /F

Or change port:

Edit areg.init:

router::*::port::tcpip = 9090  # Use different port

Application Cannot Connect

Problem: Application fails to connect to mtrouter.

Solution:

1. Verify mtrouter is running:

# Check process
ps aux | grep mtrouter  # Linux
tasklist | findstr mtrouter  # Windows

2. Check mtrouter console for connections:

Type --instances or -n in mtrouter console to see connected applications.

3. Verify application configuration:

Check myapp.init:

router::*::address::tcpip = 127.0.0.1  # Must match mtrouter
router::*::port::tcpip    = 8181       # Must match mtrouter

4. Verify router client is enabled:

Check application code:

Application::initApplication(
    true,   // logging
    true,   // service manager
    true,   // router client ← Must be true
    true,   // timer
    true    // watchdog
);

5. Test network connectivity:

Same machine:

telnet 127.0.0.1 8181

Different machine:

telnet 192.168.1.100 8181

If telnet fails: Network/firewall issue

Firewall Blocking Connection

Problem: mtrouter running but remote applications can't connect.

Solution:

Linux (ufw):

# Allow port 8181
sudo ufw allow 8181/tcp

# Check status
sudo ufw status

Linux (firewalld):

# Allow port
sudo firewall-cmd --permanent --add-port=8181/tcp
sudo firewall-cmd --reload

Windows Firewall:

# Add rule
New-NetFirewallRule -DisplayName "Areg mtrouter" -Direction Inbound -Protocol TCP -LocalPort 8181 -Action Allow

Service Won't Start (Linux)

Problem: systemctl start fails

Solution:

Check service status:

sudo systemctl status mtrouter.service

Check logs:

sudo journalctl -u mtrouter.service -n 50

Common issues:

1. Executable not found:

# Verify path in service file
grep ExecStart /etc/systemd/system/mtrouter.service

# Verify executable exists
ls -l /usr/local/bin/mtrouter

2. Missing library:

# Check dependencies
ldd /usr/local/bin/mtrouter

# Copy missing library
sudo cp ./product/build/gnu-g++/linux-64-x86_64-release-shared/lib/libareg.so /usr/lib/
sudo ldconfig

3. Permissions:

# Make executable
sudo chmod +x /usr/local/bin/mtrouter

Service Won't Start (Windows)

Problem: Service fails to start in Services app

Solution:

Check Event Viewer:

Win + R → eventvwr.msc
Windows Logs → Application
Look for mtrouter errors

Common issues:

1. Missing DLL:

Ensure areg.dll is in same directory as mtrouter.exe

2. Permission issues:

Install must be run as Administrator

3. Service already exists:

# Uninstall first
.\mtrouter.exe --uninstall

# Then reinstall
.\mtrouter.exe --install

No Connected Instances Shown

Problem: Type -n but shows no instances

Cause: No applications connected yet.

Solution:

1. Start an application:

# From multiprocessing project
./build/myapp_provider

2. Check connection in mtrouter:

Type -n or --instances in mtrouter console.

3. If still shows 0 instances:

Check application configuration (mtrouter address/port)
Verify Application::initApplication() has router enabled (3rd parameter = true)
Check application logs for connection errors
Verify mtrouter is listening on correct address/port

↑ Back to top ↑

Additional Resources

Related Guides:

Quick Project Setup - Create multiprocessing projects
CMake Integration - Integration methods
Persistence Syntax - Configuration file format

Configuration Files:

areg.init - Default configuration
mtrouter.service - Linux service file

Installation:

install.cmake - CMake installation script

Source Code:

mtrouter Module - Router implementation

Help: For questions, open a discussion or issue on GitHub.

↑ Back to top ↑

Help us to make docs greater: See something is wrong, unclear or need a help? Submit a change, open a discussion or ask AREG SDK community a question.

Quick links

Help to make docs greater!

03a Areg SDK Multitarget Router (mtrouter)

Areg SDK Multitarget Router (mtrouter)

Table of Contents

Quick Start

Run mtrouter in 10 Seconds

Overview

What is mtrouter?

When Do You Need mtrouter?

Architecture

Deployment Options

Installation

Option 1: Use from Build Directory

Option 2: Install via CMake

Running as Console Application

Basic Usage

Console Commands

Verbose Mode

Custom Configuration

Running as System Service

Linux Service (systemd)

Step 1: Prepare Files

Step 2: Install Service File

Step 3: Enable and Start Service

Step 4: Manage Service

Windows Service

Step 1: Prepare Binaries

Step 2: Install Service

Step 3: Start Service

Step 4: Configure Startup Type

Step 5: Manage Service

Configuration

Configuration File Location

Configuration Format

Router Configuration Section

Common Configurations

Disable Logging

Command Reference

Command-Line Options

Interactive Console Commands

Application Integration

Connecting to mtrouter

Basic Connection

Connection with Custom Configuration

Application Configuration

Connection Verification

Network Example

Troubleshooting

mtrouter Won't Start

Port Already in Use

Application Cannot Connect

Firewall Blocking Connection

Service Won't Start (Linux)

Service Won't Start (Windows)

No Connected Instances Shown

Additional Resources

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Quick links

Clone this wiki locally