Red Pitaya

CHECKING NETWORK STATE

Network service is not responding. Check nginx and the scripts under /opt/redpitaya/www/apps/network_manager/scripts.

Overview

Status

Interfaces

Wired

Wireless

Scan

Access point

Security

HTTPS

Status

Diagnostic WiFi

Shown because something needs attention. Lines marked ! or × are the ones to act on.

Not run yet.

Wired — eth0

Written to /etc/systemd/network/wired.network.

Protocol

Address

IPv4 address

Netmask

Gateway

DNS server

Wireless — wlan0

Client mode. Written to /opt/redpitaya/wpa_supplicant.conf.

Radio

Regulatory country

Left unset, every 5 GHz channel is passive-scan only — visible in a scan, impossible to join.

Network

SSID

Passphrase

Key management

Protected management frames

Hidden network

probe for the SSID (scan_ssid=1)

Scan

	SSID	Security	Signal
No scan yet.

Access point

Written to /opt/redpitaya/hostapd.conf. Mutually exclusive with client mode — starting the AP stops the supplicant.

Radio

SSID

Passphrase

8 to 63 characters, or empty for an open network.

Channel

Radio mode

Country code

Taken from the wireless section; written as country_code with ieee80211d=1.

Network

Board address

Netmask

Lease pool

First address

Pool size

—

Lease time, s

DNS for clients

Left empty, clients are given this board as their resolver.

associated stations
Address	MAC	Signal	Connected	Rx	Tx
No stations.

HTTPS

Settings in /etc/redpitaya/https.conf, certificate in /etc/redpitaya/ssl. Both are on the root filesystem, so an ecosystem update keeps them.

This nginx build has no SSL module. Rebuild the ecosystem with --with-http_ssl_module before turning HTTPS on.

HTTPS was turned off at the last boot: nginx could not load the certificate, so the board came up on plain http. Install a working certificate and apply again. The reason is in dmesg.

Trusting this file on the machines that open the board stops the browser warning a self-signed certificate causes. Linux: copy it to /usr/local/share/ca-certificates/ and run update-ca-certificates. Windows: import into Trusted Root Certification Authorities. macOS: add to the login keychain and set it to Always Trust. Firefox keeps its own store, under Settings → Certificates. Check the SHA-256 above against what you imported.

Server

HTTPS Serve the web interface over TLS

Port

Redirect Send plain HTTP requests to HTTPS

Port 80 keeps working either way. Leaving the redirect off is the safer choice: if a certificate turns out to be unusable, the board is still reachable over http.

Certificate

Source

Common name

Also valid for

Comma separated. The hostname, its .local name and the board's current addresses are always included. Listing more names does not give this board another name to answer to — it answers to its hostname, and mDNS publishes that one name only; rename the board if you want a different one. Extra names are for the other boards this certificate is to be shared with.

Valid for, days