andreas
753c929e3d
Fixed hostapd-2g.conf to properly specify interface wlx3c3332002066 (D-Link) for 2.4GHz AP. Both APs now operational: - 5GHz: wlp1s0 (MT7925E), channel 149, 802.11ac/ax - 2.4GHz: wlx3c3332002066 (D-Link), channel 6, 802.11n Both bridged to br0 (10.42.1.0/24), served by dnsmasq DHCP. D-Link interface usb-modeswitch now working properly (no CDROM mode). DHCP clients can connect to either band and receive addresses in the 10.42.1.10-254 range with gateway 10.42.1.1. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
26 lines
937 B
Plaintext
26 lines
937 B
Plaintext
interface=wlx3c3332002066
|
|
# Second, independent hostapd instance (hostapd-2g.service) — 2.4GHz band of the same
|
|
# VanLink network, bridged into the same br0 segment as the 5GHz AP and the wired port.
|
|
# Separate process on purpose: a USB wedge on one radio must never take down the other.
|
|
bridge=br0
|
|
# Same ctrl dir as the 5GHz AP — sockets are per-interface, hostapd_cli/watchdog use -i.
|
|
ctrl_interface=/var/run/hostapd
|
|
driver=nl80211
|
|
# Same SSID + PSK as 5GHz: dual-band clients pick a band themselves, 2.4-only IoT
|
|
# devices just join. Rename here (e.g. VanLink-2G) if band pinning is ever needed.
|
|
ssid=VanLink2-2G
|
|
country_code=CA
|
|
ieee80211d=1
|
|
hw_mode=g
|
|
channel=6
|
|
wmm_enabled=1
|
|
# HT20 only — 40MHz in 2.4GHz overlaps most of the band and coexistence would force
|
|
# it back to 20MHz near any neighbor anyway.
|
|
ieee80211n=1
|
|
ht_capab=[SHORT-GI-20]
|
|
auth_algs=1
|
|
wpa=2
|
|
wpa_passphrase=1foot11foot11
|
|
wpa_key_mgmt=WPA-PSK
|
|
rsn_pairwise=CCMP
|