Arch Linux

UwU25

Member

Registered: 2025-05-04

Posts: 2

Issue connecting to Enterprise Wi-Fi (PEAP/MSCHAPv2) on Arch Linux

Hey everyone,

I’m currently running Arch Linux (using the Omarchy installer) and I’m having a specific issue with my university’s Wi-Fi (KIIT).

The Setup:

    SSID: KIIT-WIFI-NET

    Security: WPA/WPA2 Enterprise

    Authentication: PEAP

    Inner Authentication: MSCHAPv2

    Backend: I've tried both wpa_supplicant and the latest iwd (Impala).

The Problem:
I can connect perfectly fine to the Wi-Fi when I am in my hostel room using the local router/AP there. However, as soon as I move to another room, the library, or anywhere else on campus, it fails to connect—even though the credentials and SSID are identical. On Windows, the roaming works perfectly.

I have "No CA certificate is required" checked (as seen in my settings) because that’s what works in my room.

What I’ve tried:

    Switching from wpa_supplicant to the updated iwd (Impala).

    Running iwctl directly to connect.

    Checking logs, but I'm not seeing a clear "handshake failed" reason other than generic de-authentication when moving between APs.

Has anyone dealt with enterprise networks that behave differently across different access points on Linux? Is there a specific iwd or NetworkManager configuration I might be missing regarding roaming or BSSID handling?

I really don't want to switch back to Windows just for the campus Wi-Fi. Any help is appreciated!

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 74,664

Re: Issue connecting to Enterprise Wi-Fi (PEAP/MSCHAPv2) on Arch Linux

(using the Omarchy installer)

https://bbs.archlinux.org/misc.php?action=rules

Please post your complete system journal for a boot covering such roaming failures, eg.

sudo journalctl -b -1 | curl -F 'file=@-' https://0x0.st

for the previous boot ("-1")

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc