Networking - dwhinham/mt32-pi GitHub Wiki

mt32-pi can be connected to your network via Ethernet or Wi-Fi to receive MIDI via the network, or access files remotely via the embedded FTP server.

Networking options by Raspberry Pi model

The networking capabilities of the Raspberry Pi varies by model. The following table provides a summary:

Model	Ethernet	Wi-Fi
Raspberry Pi Zero 2 W	❌	✔ (2.4GHz only)
Raspberry Pi 2 Model B	✔	❌
Raspberry Pi 3 Model A+	❌	✔ (2.4 and 5GHz)
Raspberry Pi 3 Model B	✔	✔ (2.4GHz only)
Raspberry Pi 3 Model B+	✔	✔ (2.4 and 5GHz)
Raspberry Pi 4 Model B	✔	✔ (2.4 and 5GHz)
Raspberry Pi Compute Module 3, 3+	❌	❌
Raspberry Pi Compute Module 4	✔ (if provided by carrier board)	✔ (if using a "with Wi-Fi" model, 2.4 and 5GHz)

Setup

Edit the mode option under the [network] section of the configuration file to enable networking. You can set the mode to be either ethernet or wifi to enable the appropriate network interface.

The default configuration attempts to get an IP address and DNS server from your network via DHCP. If you prefer to use a static IP address, you can edit the ip_address, subnet_mask, default_gateway, and dns_server settings accordingly.

If you have multiple mt32-pi devices on the network, you may wish to edit the hostname option to give them unique names.

With networking enabled, mt32-pi will briefly display its IP address on the LCD once it connects successfully.

Wi-Fi

The wpa_supplicant.conf file and the firmware directory (both included in installation package) must be present on the root of the SD card in order to use Wi-Fi.

You must edit wpa_supplicant.conf to add your country code, SSID and encryption key. Read the file carefully and replace the defaults with your own settings. You may need to amend additional settings if using an encryption setup that isn't WPA2.

A list of supported country codes can be found on this page.

⚠️ Note: Failure to set the correct country code may result in inability to connect to certain Wi-Fi networks, especially 5GHz access points.