Communications with MiWire and third parties
This page lists every network service a RouDem unit communicates with on its own, and what it sends. All of these connections are opened by the unit, outbound over the mobile network, and are encrypted. No service connects inbound to the unit.
MiWire services
Section titled “MiWire services”| Service | Purpose | What the unit sends | How often |
|---|---|---|---|
enroll.miwire.net, renew.miwire.net |
Issue and renew the unit’s own device certificate, which identifies it to the MiWire services | The unit’s IMEI and a certificate request | Once at set-up; renewal automatically before expiry |
coveragemap.miwire.net |
Connection statistics and operation of the service | Connection quality (signal, serving cell, operator), data usage, GPS position, SIM identifiers, firmware version and state, antenna state, the SIM and APN settings needed to administer the subscription, security events (see below), and for fixed installations a lookup of the serving cell’s position | Statistics hourly; health report every few minutes |
health-check.miwire.net |
Online check | That the unit is online, its firmware version and link state | Every few minutes |
roudem-update-service.miwire.net |
Firmware update check | IMEI, hardware type, current firmware version | Hourly, and when “Check for update” is pressed |
miwireblob.blob.core.windows.net (MiWire storage at Microsoft Azure) |
Download of a firmware image offered by the update service | A download request | Only when an update is installed |
mqtt.miwire.net |
Status channel: MiWire’s management system can ask the unit for its current status | The same status data as the statistics upload, on request and once a minute | Connection kept open |
| MiWire support relay | Remote support by MiWire staff; support logins are recorded in the security event log | Nothing by itself; carries the support session when MiWire connects | Connection kept open |
trackwire-cloud.miwire.net |
TrackWire asset tracking, only on units where the customer has ordered it | Position and tracking data | Only when the service is enabled |
The earlier MiWire interface api.miwire.net, contacted by older firmware, is retired.
Third-party services
Section titled “Third-party services”| Service | Purpose | What the unit sends |
|---|---|---|
ntp1.miwire.net, ntp2.miwire.net, time.cloudflare.com |
Time synchronisation. The customer can replace the list in the web interface. | Standard NTP requests, no identifying data |
1.1.1.1, 8.8.8.8 |
Connectivity probe (ping) used by the antenna logic and the health check | ICMP echo requests only, no DNS queries |
| The mobile network operator | Internet connectivity and DNS resolution | The LAN’s traffic, as with any router; the SIM’s identity to the network |
Security event log
Section titled “Security event log”The unit records security-relevant events (logins to the web interface and over SSH, configuration changes, firmware updates, service switches, certificate renewals, support access) and uploads them to MiWire so that MiWire can detect misuse and account for support access. The upload can be switched off on the Services page. Retention is described under Data processed.
Partner installations
Section titled “Partner installations”Units delivered through a MiWire partner can be set at the factory to use the partner’s instance of the services above under the partner’s own host names. Purpose and data are the same.