Fix regulatory domain persistence for 5GHz AP on boot
Problem: wlan1 regulatory domain not set on boot, defaults to 2.4GHz-only mode, preventing channel 149 (5GHz) from being available. hostapd fails on startup. Solution: 1. Modified regdomain.service to: - Run BEFORE hostapd/hostapd-2g services (Before= directive) - Run earlier in boot (After= sysinit.target) - RemainAfterExit=yes to persist setting 2. Added 80-regdomain.rules udev rule: - Triggers on regulatory device changes - Executes 'iw reg set CA' automatically 3. Added hostapd drop-in config: - Explicitly requires regdomain.service - Adds Wants= to ensure it starts This ensures the regulatory domain is set BEFORE hostapd attempts to use channel 149, fixing the boot-time AP failure loop. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,4 @@
|
||||
# Ensure regdomain.service runs before hostapd
|
||||
[Unit]
|
||||
After=regdomain.service
|
||||
Wants=regdomain.service
|
||||
Reference in New Issue
Block a user