ALPON X4 OS
Operating System
The ALPON X4 ships with a Sixfab-customized build of Raspberry Pi OS Lite 64-bit (Bookworm), optimized for industrial edge computing workloads. Cellular connectivity, Sixfab Connect agent, Docker, and remote management are pre-installed and configured at the factory. Power the device on and it is ready to register with ALPON Cloud, run containers, and accept SSH sessions.
Overview
What operating system does the ALPON X4 run?
The ALPON runs a Sixfab-maintained build of Raspberry Pi OS Lite 64-bit Bookworm tuned for the Raspberry Pi Compute Module 4. The image bundles the cellular stack, the Sixfab Connect agent, Docker, and remote management tooling so the device comes online and registers with ALPON Cloud on first boot with no manual OS setup.
Base Operating System
Raspberry Pi OS Lite 64-bit · BookwormCustomized by Sixfab for industrial IoT and edge AI gateway deployments on the Raspberry Pi CM4. Shipped pre-installed with the Sixfab Connect agent, Docker, and the cellular connectivity stack.
What's pre-installed
The image is ready to boot and register with ALPON Cloud without additional setup. Key components already on the device:
The image is tuned for the ALPON platform. Removing the Sixfab Connect agent, the alpon system user, or the pre-installed connectivity packages will break remote management, OTA updates, and cellular failover. Install and remove your own applications freely; leave Sixfab components intact.
Architecture
The ALPON X4 runs on a 64-bit ARM architecture (arm64 / aarch64) via the Raspberry Pi Compute Module 4. All custom binaries, Docker images, and third-party packages must be compiled for or compatible with arm64. x86 / amd64 binaries are not supported.
Use multi-arch images or pin the platform explicitly: docker pull --platform linux/arm64 <image>. Most official images on Docker Hub publish arm64 variants.
First boot & setup
The ALPON is ready to use the moment it is powered on. On first boot it brings up networking, registers with Sixfab Connect (if provisioned), and starts the device agent. From there, set up user access so you can log in for day-to-day administration.
Default credentials
Every ALPON X4 ships with a factory-configured system user. Use these credentials for initial login only. Change them before deploying the device to production.
Default Username
alponDefault Password
sixfabThe alpon / sixfab pair is shared across all ALPON X4 devices. Run sudo passwd alpon on first boot and do not expose the device to an untrusted network until the password is changed.
alpon user
The alpon account is used internally by the Sixfab Connect agent and other system services. Change its password, but keep the account. If your security policy requires a separate admin identity, create a new user (see Step 4) and keep alpon intact.
Device hostname
Each ALPON X4 has a unique hostname derived from its primary MAC address, in the format:
The MAC address is printed on the device label. This ensures multiple ALPON devices on the same network never conflict, and it lets you reach the device over mDNS as alpon-<MAC>.local without needing to know its IP.
Set up user access
Provision the device in Sixfab Connect
Before you can reach the device remotely, it must be registered to your Sixfab Connect organization. If you haven't done this yet, complete the Quick Start first.
Open a shell on the device
You have two ways to get a shell.
Browser-based remote terminal (recommended): open the device in Sixfab Connect and launch the remote terminal. No SSH client or local network access required.
SSH over LAN: connect a keyboard temporarily, or resolve the device by mDNS:
# Resolve by mDNS hostname ssh alpon@alpon-<MAC>.local # Or connect by IP directly ssh alpon@<DEVICE_IP>
Change the default password
Once logged in as alpon, immediately change the password with passwd. Enter the current password (sixfab), then choose a new one.
passwd # Current password: sixfab # New password: <your_secure_password> # Retype: <your_secure_password>
Pick a strong password of at least 12 characters mixing upper, lower, digit, and symbol. For a fleet, prefer SSH key authentication (see Step 5).
Create a separate admin user (optional but recommended)
If your security policy requires an admin identity distinct from the service account, add a new user and grant sudo privileges. Replace <USERNAME> with the name you want.
# 1. Create the user and home directory sudo useradd -m -s /bin/bash <USERNAME> # 2. Set a password for the new user sudo passwd <USERNAME> # 3. Grant administrative (sudo) privileges sudo usermod -aG sudo <USERNAME>
Log out and log back in as the new user to confirm sudo works before relying on it.
Connect over SSH from your workstation
From a machine on the same network, open an SSH session to the ALPON using the hostname or its IP address.
# Recommended: mDNS hostname (no IP lookup needed) ssh <USERNAME>@alpon-<MAC>.local # Fallback: direct IP ssh <USERNAME>@<DEVICE_IP>
If your network blocks mDNS, use the IP address directly: ssh <USERNAME>@<IP_ADDRESS>. The device IP is visible on the Sixfab Connect device page. When LAN access is unavailable entirely, fall back to the browser-based remote terminal.
Connect a local display Optional
Plug an HDMI display and USB keyboard into the ALPON X4 to log in locally. The HDMI 2.0 port supports up to 4Kp60 output. Connect the display before powering the device on.
Your device now has a secure user account. You can reach the ALPON X4 over SSH or the Sixfab Connect remote terminal and move on to system updates and application deployment.
System updates
The ALPON X4 OS uses standard Debian package tooling. Apply security patches and upgrades with apt, and manage deployed applications separately through Docker or the ALPON Cloud fleet update flow.
How do I update the ALPON X4 OS?
From a shell on the device, run the standard Debian update cycle:
- Refresh the package index with
sudo apt update. - Apply available upgrades with
sudo apt upgrade -y. - Reboot if a kernel or firmware package was upgraded.
# 1. Refresh package lists sudo apt update # 2. Apply available upgrades sudo apt upgrade -y # 3. Reboot if the kernel or firmware was updated sudo reboot
When updating a fleet, stagger the rollout. Reboot one device, confirm it comes back online in Sixfab Connect, and only then proceed to the next. This protects you from regressions in upstream packages.
How do I update deployed applications?
Application updates are separate from OS updates. Use the method that matches how the app was deployed:
- Containers deployed through ALPON Cloud: push a new image tag from the Manage & Deploy Applications dashboard. Sixfab Connect orchestrates the pull, restart, and rollback.
- Manually-run containers: run
docker pull <image>:<tag>on the device, then recreate the container withdocker compose up -dordocker run. - System packages: run
sudo apt install --only-upgrade <package>.
Firmware and modem updates
Modem firmware and the Sixfab Connect agent are delivered through the normal apt channel and, where applicable, through Sixfab Connect OTA. You don't need to manage them manually. When a Sixfab-maintained package is updated, apt upgrade pulls it in.
Avoid apt autoremove unless you know exactly what it is about to remove. If it lists sixfab-* or modemmanager as removable, cancel the operation. Removing those packages disconnects the device from ALPON Cloud and breaks cellular failover.
Troubleshooting apt failures
If apt update or apt upgrade fails, the cause is usually no internet path, a broken GPG key for the Sixfab repository, or a partial upgrade that left dpkg in an inconsistent state. Recover in this order:
# 1. Verify connectivity first ping -c 3 deb.debian.org # 2. Repair any half-configured packages sudo dpkg --configure -a sudo apt -f install # 3. Refresh and retry sudo apt update sudo apt upgrade -y
OS image & re-flashing
The ALPON X4 OS image is pre-installed at the factory on every device and is not distributed as a public download. Shipping the OS on the device avoids the edge cases and hardware-specific quirks that come with end-user flashing of industrial edge computing images.
If your device is in a state where you believe the OS needs to be re-flashed, for example it won't boot after a failed upgrade or it has been misconfigured beyond recovery, contact Sixfab support.
Contact Sixfab support
Have your device serial number ready. Support will verify the fault and provide the correct recovery procedure.
Many "broken OS" symptoms are recoverable over a working shell session:
- Use the Sixfab Connect remote terminal. It works even if LAN or SSH is misconfigured, as long as the cellular link is alive.
- If a recent upgrade broke something, check
journalctl -xeand runsudo apt install --reinstall <package>. - For Docker-related failures:
sudo systemctl restart docker.
Where to next
Updated about 4 hours ago
