Network Configuration Settings

The Network configuration section (Config > Network) controls how ESP32-based Meshtastic nodes connect to IP networks - WiFi and Ethernet - and associated services like NTP and remote logging. These settings are only relevant for ESP32 hardware; nRF52-based boards (like the RAK4631) do not support WiFi natively and these settings have no effect on them, with the exception of Ethernet on RAK builds fitted with a RAK13800 module.

Access these settings in the Meshtastic app under Settings > Radio Configuration > Network, or via the Python CLI with meshtastic --set network.*.

Note: Network connectivity unlocks important Meshtastic features: the web interface, MQTT gateway, APRS bridging, NTP time synchronization, and remote syslog. If you are using ESP32-based hardware (T-Beam, T-Lora, Heltec WiFi LoRa, Station G2, etc.), understanding these settings is important for gateway and infrastructure deployments.


WiFi SSID

Config key: network.wifi_ssid
Default: Empty (WiFi disabled)

The SSID (network name) of the WiFi network the node should connect to as a client. Case-sensitive. Maximum 32 characters.

To enable WiFi: Set both WiFi SSID and WiFi Password. The node will attempt to join the network on boot and reconnect if the connection drops.

Important considerations:


WiFi Password

Config key: network.wifi_psk
Default: Empty

The passphrase for the WiFi network specified by WiFi SSID (max 64 characters). Stored in the device's flash memory. Supports open networks (leave password empty if the network has no password, though this is strongly discouraged for security reasons).

Security note: The WiFi password is stored in plaintext in the device's NVS (Non-Volatile Storage) flash partition. Anyone with physical access to the device and a serial connection can potentially extract it. Do not configure a node with your primary home WiFi password on a device that could be physically compromised; consider using a dedicated IoT VLAN or guest network.


WiFi Mode

ESP32-based Meshtastic nodes connect to WiFi in client (station / STA) mode only. The firmware does not support SoftAP (Access Point) mode - there is no setting to make the node create its own WiFi access point, and there is no network.wifi_mode config key. WiFi is controlled simply by whether a WiFi SSID and password are set.

In client mode the node connects to an existing WiFi network as a client (station). This is the standard mode for gateway nodes that need internet access. In client mode, the node:

No phone-direct AP option: Because SoftAP mode is not supported, you cannot connect a phone or laptop directly to the node's own WiFi. For field configuration without an existing WiFi network, use Bluetooth or a USB serial connection instead.


Ethernet Enabled

Config key: network.eth_enabled
Default: false

Enables the Ethernet interface on hardware that supports it. The documented Ethernet reference hardware is the RAK4631 paired with the RAK13800 Ethernet module (a W5500-class SPI Ethernet controller). Note that JSON MQTT output is not supported on the nRF52 platform.

Advantages of Ethernet over WiFi for infrastructure nodes:

Use when: Deploying a fixed infrastructure node (ROUTER or gateway) at a location with Ethernet infrastructure - server room, communications closet, network rack. Ethernet-connected gateway nodes are more reliable than WiFi-connected ones for long-term unattended operation.


NTP Server

Config key: network.ntp_server
Default: meshtastic.pool.ntp.org

The hostname or IP address of the NTP (Network Time Protocol) server the node uses to synchronize its real-time clock when IP networking is available. Accurate time is important for:

Meshtastic nodes without internet connectivity rely on time received from other nodes on the mesh (nodes share time information in packets). An NTP-synced node improves its own clock accuracy; that time can then propagate to other nodes via the normal packet exchange, but the firmware docs do not promise that a single NTP node becomes an authoritative time source for the entire mesh.

ServerDescriptionUse When
meshtastic.pool.ntp.orgDefault NTP pool used by the firmwareGeneral use, internet-connected nodes
time.cloudflare.comCloudflare NTP (anycast, fast)Reliable alternative with good global coverage
time.google.comGoogle Public NTPReliable alternative
time.nist.govNIST time serverWhen US government standard time is needed
192.168.x.x (local)Your own local NTP serverIsolated networks, high-accuracy requirements, no internet

Local NTP server: If your deployment has a local NTP server (common in enterprise and government networks, and in some emergency operations centers), set this to that server's address. This reduces internet dependency and may improve synchronization accuracy.

NTP without internet: If the node has no internet access but is on a local network with a router that provides NTP (most home routers do), using the router's IP address as the NTP server works well: 192.168.1.1 or similar.


rsyslog Server

Config key: network.rsyslog_server
Default: Empty (disabled)

Configures remote syslog logging. When set to a hostname or IP address (with optional port, e.g., 192.168.1.100:514), the node sends its log output to a remote syslog server over UDP using the standard syslog protocol (RFC 3164/5424).

Why use remote logging:

Setup requirements:

Example rsyslog configuration to receive Meshtastic logs on a Linux server:

# /etc/rsyslog.d/meshtastic.conf
module(load="imudp")
input(type="imudp" port="514")

# Save Meshtastic logs to a dedicated file
if $fromhost-ip == '192.168.1.50' then /var/log/meshtastic/node1.log

Practical Configuration Guidance

Standard Home Gateway Node

For a mains-powered T-Beam or Station G2 acting as a gateway and router at home:

Field Deployment - No Internet

For a node deployed at an event or emergency operation without internet access:

Ethernet-Connected Infrastructure

For a fixed ROUTER node on a rack or network closet:

Local Web Access

When the node is connected to your WiFi or Ethernet network, you can reach the Meshtastic web client in a browser:


Revision #6
Created 2026-05-03 05:55:56 UTC by Mesh America Admin
Updated 2026-06-09 12:04:35 UTC by Mesh America Admin