ARMxy Industrial Computer Configuration Guide for Enterprise 802.1X WiFi Authentication

Introduction

In industrial sites and enterprise campus networks, wireless connectivity is no longer simply about “being able to connect.”
As internal network security requirements continue to rise, more and more organizations are adopting enterprise-grade 802.1X WiFi authentication, using RADIUS servers to centrally authenticate and authorize every terminal device.

For ARMxy industrial edge computing devices deployed in the field, connecting securely and reliably to enterprise WiFi networks—without a desktop environment or graphical interface, and running on headless Linux systems—often becomes a critical step during project implementation.

This guide is based on the preinstalled wpa_supplicant tool on ARMxy devices. It walks through the complete process of enterprise 802.1X WiFi access, including:

• Configuration file creation

• Authentication and connection

• IP address acquisition

• Status verification and troubleshooting

The goal is to help you deploy successfully in real industrial environments, avoiding common pitfalls and unnecessary detours.

1. Why ARMxy Needs to Support Enterprise 802.1X WiFi

In industrial sites and enterprise intranet environments, traditional WPA2-PSK (password-based WiFi) can no longer meet modern security requirements:

• Shared passwords increase risk when personnel change

• Device identities cannot be uniquely distinguished

• Centralized management and auditing are difficult

Enterprise-grade 802.1X WiFi authentication has therefore become the mainstream solution:

• Centralized authentication via RADIUS servers

• Per-device identity using individual accounts or certificates

• High security, supporting certificates and mutual authentication

• Industrial suitability, widely used in factories, campuses, and enterprise networks

ARMxy devices come with wpa_supplicant preinstalled, enabling enterprise WiFi access directly from the command line.

2. Prerequisites

Before starting configuration, make sure the following information and tools are ready:

2.1 System and Tool Requirements

• Operating System: Linux

• Wireless Tool: wpa_supplicant (preinstalled on ARMxy)

• Access Method: SSH or serial console

2.2 Enterprise WiFi Information

• SSID: Company_WiFi

• Authentication Method: PEAP / MSCHAPv2 or EAP-TLS

• Credentials:

  • Username + password

  • or client certificate + private key

• Optional: CA root certificate

3. Creating the wpa_supplicant Configuration File

For easier maintenance, it is recommended to store configuration files in the following directory:

Example file name:

4. Common Enterprise Authentication Configuration Examples

Option 1: PEAP / MSCHAPv2 (Username + Password)

👉 Most common and lowest deployment cost

Parameter explanation:

• ssid: Enterprise WiFi name

• identity: Username (employee ID or account)

• password: Login password

• phase2: Phase 2 authentication method

• ca_cert: Strongly recommended to enhance security

⚠️ Disabling server certificate validation is not recommended for long-term use and should only be done for testing.

Option 2: EAP-TLS (Certificate-Based Authentication)

👉 Highest security level, commonly used for critical devices

Parameter explanation:

• client_cert: Client certificate

• private_key: Private key file

• ca_cert: RADIUS server CA certificate

5. Connecting to Enterprise WiFi (Recommended Two-Step Method)

Step 1: Foreground Mode (Debugging)

• -c: Specify configuration file

• -i: Wireless interface name (e.g., wlan0)

Success indicator:

Once confirmed, press Ctrl + C to exit test mode.

Step 2: Background Mode (Production Use)

• -B: Run as a background daemon

6. Obtaining an IP Address (Critical Step)

Successful authentication does not automatically mean network access.
You must still obtain an IP address via DHCP:

Verify the result:

Checkpoints:

• inet address exists → IP obtained

• Not 169.254.x.x → DHCP functioning normally

7. Quick Connection Verification Checklist

• Interface status:

  ip addr show wlan0

  Interface is UP and has an IP address

• WiFi association:

  iw dev wlan0 link

  Shows Connected to

• Process status:

  ps | grep wpa_supplicant

  Process is running

• Network connectivity:

  ping -c 4 8.8.8.8

  Normal replies received

8. Common Issues and Troubleshooting

8.1 Check Authentication Logs (Primary Method)

Focus on keywords:

• EAP

• authentication

• failed

• timeout

8.2 Common Problems Reference Table

9. Conclusion: The Value of ARMxy + Enterprise WiFi

With 802.1X enterprise WiFi, ARMxy devices can achieve:

✅ Secure access to enterprise intranets
✅ Controlled and traceable device identities
✅ Seamless integration with IT security systems

This makes the solution especially suitable for:

• Smart manufacturing

• Factory intranets

• Energy systems

• Campus-scale industrial deployments