ALPON X4 OS

Overview

ALPON X4 OS is a minimal Debian image maintained by Sixfab. It builds on Raspberry Pi OS Lite and uses the apt package manager. This guide covers initial user access, local Wi-Fi configuration, and package updates; it is not a complete deployment-hardening policy. Review your application's permissions, network exposure, and update process before production use.

What's pre-installed

The factory image includes the following components. Register and activate the device in ALPON Cloud before using cloud-managed services:

• Sixfab Connect agent for ALPON Cloud fleet management and the browser-based remote terminal.
• Docker & Docker Compose pre-installed and enabled, ready for container deployments through ALPON Cloud or your own tooling.
• ModemManager & NetworkManager with the LTE Cat 4 cellular and dual-band Wi-Fi 5 stack pre-configured.
• OpenSSH server for local and remote shell access on port 22.
• mDNS / Avahi so the device is reachable as alpon-<MAC>.local on the local network.
• VPN client for the tunnel to ALPON Cloud services; application traffic is not necessarily routed through that tunnel.
• Hardware watchdog for reset on loss of its required heartbeat while enabled. Use one heartbeat owner: do not run a watchdog daemon and application heartbeat simultaneously. See DIP switches & watchdog for timing and polarity.

Architecture compatibility

ALPON X4 runs on a 64-bit ARM architecture (arm64 / aarch64). All custom binaries, container images, and third-party packages must target arm64. x86 / amd64 binaries are not supported.

First boot & setup

On boot, the device starts its networking and system services. Complete registration and activation in the Quickstart, then verify ALPON Cloud connectivity before using the remote terminal. Boot and provisioning duration vary with network conditions.

Default credentials

Every ALPON X4 ships with a factory-configured system user. Use these credentials for initial login only, then change the password before deploying to production.

Device hostname

Each ALPON X4 has a unique hostname derived from its primary MAC address:

The MAC address is printed on the device label. From an existing shell, run hostname to see the exact hostname. If mDNS is available on your LAN, append .local to that hostname; otherwise use the device's IP address.

Set up user access

# 1. Change the password for the current user (alpon)
passwd

# 1. Create the new user (you will be prompted for a password)
sudo useradd -m -s /bin/bash <username>
sudo passwd <username>

# 2. Grant sudo (administrative) privileges
sudo usermod -aG sudo <username>

# 1. Connect by hostname (mDNS)
ssh <username>@alpon-<MAC>.local

# 2. Or by IP address
ssh <username>@<DEVICE_IP>

Local configuration

Two device-local tasks that are not part of cloud onboarding: joining a Wi-Fi network as a client, and driving the programmable RGB LED.

Connect to local Wi-Fi

ALPON X4 OS uses NetworkManager and its nmcli client, also used in the ALPON Wi-Fi hotspot tutorial. The procedure below joins an existing personal Wi-Fi network; it does not create a hotspot or configure an enterprise EAP network.

1. With the device unpowered, attach the Wi-Fi antenna to the W RP-SMA connector. Power on using one supported input.
2. Open a local console or an existing Ethernet-connected shell. Keep that access available: changing Wi-Fi can interrupt a remote session, and connecting as a client replaces any hotspot using the same radio.
3. List interfaces and nearby networks, then connect using the commands below. Replace <WIFI_INTERFACE> with the interface whose TYPE is wifi in the first command, and YOUR_SSID with your network name. Enter the Wi-Fi password at the prompt, not in the command line.

nmcli device status
sudo nmcli radio wifi on
nmcli device wifi list ifname <WIFI_INTERFACE>
sudo nmcli --ask device wifi connect "YOUR_SSID" ifname <WIFI_INTERFACE>
nmcli device show <WIFI_INTERFACE>
nmcli connection show --active

Confirm the Wi-Fi interface is connected and has an IP address. Keep Ethernet connected until you can reach the device over the Wi-Fi address from the same network. A Wi-Fi association does not by itself prove internet or ALPON Cloud access; verify the cloud status separately. If no Wi-Fi interface appears, or the network needs enterprise authentication or a captive portal, consult your network administrator and the NetworkManager reference rather than changing cloud or service settings speculatively.

Hardware-controlled peripherals

The programmable RGB LED is controlled through an I²C GPIO expander, not direct CM4 GPIO outputs. Use the documented interface in Physical Layout & I/O. Confirm the hardware revision and supported control method before writing to the expander.

System updates

ALPON X4 OS uses standard Debian package tooling. Apply security patches with apt, and manage deployed applications separately through Deploy Applications on ALPON Cloud.

Update ALPON X4 OS

Refresh the package index and apply available upgrades:

# 1. Refresh package lists
sudo apt update

# 2. Apply available upgrades
sudo apt upgrade -y

# 3. Reboot if a kernel or firmware package was upgraded
sudo reboot

Update deployed applications

Application updates are independent of OS updates. Pick the path that matches how the application was deployed:

Firmware and modem updates

Use apt for installed package updates. For modem firmware or device-specific recovery, obtain the procedure for your hardware revision from Sixfab support; do not assume an OS package upgrade also updates every firmware component.

Quick command reference

Common ALPON X4 OS administration commands. Run them in a device shell over SSH, the local console, or ALPON Cloud's remote terminal.

OS image & recovery

The ALPON X4 OS image is pre-installed at the factory and is not distributed as a public download. Shipping the OS on the device avoids the hardware-specific edge cases that come with end-user flashing of an industrial edge computer image.

If you believe your device needs to be re-flashed (for example, after a failed upgrade or a recovery-blocking misconfiguration), contact Sixfab support. Support will confirm whether a re-flash is actually needed and provide the recovery procedure for your device's serial.