📡 MIVO Connect – Network Guide#

This guide summarizes common network scenarios for MIVO Connect and provides answers to questions related to IP configuration, ports, firewalls, and WAN or LTE connectivity.

General network information#

1. 🧩 Standard Installation with DHCP#

❓ Questions & Answers: - Does the device automatically get an IP address via DHCP?
Yes, MIVO automatically requests an IP address via DHCP during startup.

What happens if no DHCP server is available?
The device waits for an IP address and indicates this with a blinking red WAN LED.
How is this shown through MIVO’s LED indicators?
Blinking red WAN light = No IP address assigned.

📌 Scenario: Common in most networks with a standard router.

2. 🛠 Static IP Address#

❓ Questions & Answers: - When must a static IP address be configured?
When DHCP is unavailable or a fixed IP is required for firewall rules.

How is this configured via the web interface?
Go to System > Network in the MIVO Connect interface.
Which settings are required?
IP address, subnet mask, gateway, and DNS servers must be entered manually.

📌 Scenario: Common in larger networks or industrial systems.

3. 🌐 Wired WAN Connection (Ethernet)#

❓ Questions & Answers: - What happens if the WAN cable is not connected?
The WAN LED will be solid red. No link detected.

How do you verify that MIVO has internet access?
Use the status view in the interface or perform an ICMP ping (e.g. to www.google.com).
Which port/protocol is used for internet connectivity tests?
ICMP (ping).

📌 Scenario: Primary solution for buildings with wired internet.

4. 📶 LTE – Mobile Network#

❓ Questions & Answers: - When should LTE be used instead of a wired connection?
When no wired connection is available or as a backup connection.

How is LTE activated in the interface?
Go to System > Network and enable LTE.
What is required for LTE to work?
SIM card, correctly installed antenna, and configuration via the interface.

📌 Scenario: Ideal for temporary installations or remote locations.

5. 🔄 Router in Front or Behind MIVO#

❓ Questions & Answers: - Should MIVO be directly connected to the internet or behind a router?
Most commonly, MIVO is placed behind a NAT-enabled router.

Which outbound ports must be opened in the firewall?
80 (HTTP), 443 (HTTPS), 2022 (Easy Access), 21 (FTP for export).
Is NAT or port forwarding required?
Only for inbound traffic like VPN access.

📌 Scenario: Common in corporate or centrally managed networks.

6. ☁️ Export to External Systems (FTP/HTTP)#

❓ Questions & Answers: - Which ports must be allowed outbound for export?
Typically port 21 for FTP and port 443 for HTTPS.

Do you need to open port 21 (FTP) or 443 (HTTPS)?
Yes, depending on the chosen export method.
How is authentication handled?
Via username/password or e.g., Bearer Token in the HTTP header.

📌 Scenario: Used when sending data to external platforms or systems.

7. ⚙️ Modbus TCP Communication#

❓ Questions & Answers: - How is Modbus TCP configured in MIVO Connect?
Add a "Modbus TCP Interface" under Infrastructure > Add.

Which IP and port are used (usually 502)?
Port 502 is standard; IP address is entered manually.
Does the firewall need to allow inbound traffic to MIVO?
No, MIVO acts as a client/master and initiates outbound connections.

📌 Scenario: Used to measure electricity, heat, water via external Modbus devices.

8. 🔐 VPN and Secure Remote Access#

❓ Questions & Answers: - Does the OpenVPN server need to be enabled on MIVO (port 1194)?
Yes, if you want to access MIVO remotely via VPN.

When is VPN access required?
When remote access to the web interface is needed outside the local network.
Does this require port forwarding?
Yes, port 1194 (UDP) must be forwarded in the router.

📌 Scenario: For remote maintenance, support, or accessing off-site devices.

9. 🧪 No Internet – Troubleshooting#

❓ Questions & Answers: - How can you tell the device has no internet access?
Check status view in the interface or observe LED indicators.

Which ports should be checked first?
ICMP (ping), 53 (DNS), 80/443 (HTTP/HTTPS).

📌 Scenario: Useful when no data is reporting or remote access fails.

10. 🏢 Multiple MIVO Units in Larger Networks#

❓ Questions & Answers: - How do you avoid IP conflicts?
Use static IP addresses or reserved DHCP leases.

Does each unit need its own static IP?
Yes, it simplifies management and integration.
How do you handle VLANs, segmented networks, or gateway settings?
Set appropriate network parameters per unit based on your topology.

📌 Scenario: For buildings, industrial sites, or large deployments.

🛠 Port Overview#

Port	Protocol	Usage
80	TCP	Web GUI, software updates
443	TCP	HTTPS (Easy Access, cloud API)
502	TCP	Modbus TCP
2022	UDP	Easy Access data channel
67/68	UDP	DHCP request/response
53	UDP/TCP	DNS
1194	UDP	OpenVPN
21	TCP	FTP export (e.g. Elvaco)

🔍 Network Diagnostics Tips#

LED Indicators: Use WAN/LAN/RS485/MBUS LEDs for quick diagnostics.
Web Interface: Live logs and connection status are visible in the browser.
Test Ports: Always check ICMP, 53, 80, and 443 when troubleshooting.
Offline Situations: LTE is a solid alternative if the wired line fails.

MIVO Connect Network Port Usage#

Introduction#

MIVO Connect is a sensor gateway that collects local sensor and meter data and forwards it to a central system. This document describes the network ports used by the MIVO Connect WAN interface.

Inbound Ports#

Port	Type	Description	Default Enabled	Can Be Disabled
68	UDP	DHCP client response port	✅	❌
80	TCP	Web interface	✅	✅
502	TCP	Modbus TCP server	✅	❌
1194	UDP	OpenVPN server	✅	❌
2020	TCP	SSH server for troubleshooting	✅	❌
5355	TCP/UDP	LLMNR/mDNS (hostname lookup)	✅	✅
10001	TCP	M-Bus over IP server	✅	❌

Outbound Ports#

Port	Type	Description	Default Servers	Consequence if Blocked
N/A	ICMP ping	Internet reachability test	www.google.com	Network status will indicate internet is unreachable
53	UDP/TCP	DNS requests	1.1.1.1, 1.0.0.1, 8.8.8.8, 8.8.4.4	Domain resolution fails
67	UDP	DHCP requests	Auto detected	Must use static IP
80	TCP	Manual update checks	update.mivo.se	Software updates fail
123	UDP	NTP (time synchronization)	pool.ntp.org, time1-4.google.com	No time sync → risk of clock drift
443	HTTPS	Easy Access API channel	device-api.mivo.se	Easy Access won’t activate
2022	UDP	Easy Access traffic channel	159.223.224.194	Easy Access won't work

Value Reporting & Integrations – Outbound Ports#

MIVO Connect can send data to external systems. The protocol and port used depends on configuration.

Report Type	Transport	Port
Elvaco 2102	FTP	Configurable (default 21)
Elvaco 3105	HTTP/HTTPS	Configurable
MIVO JSON	HTTP/HTTPS	Configurable
Momentum Energi	FTP	Configurable (default 21)