Problem: R5C spontaneously rebooted due to hardware watchdog timeout Cause 1: van-gps-owntracks in infinite restart loop (MQTT connect failed) Cause 2: mosquitto only listening on localhost, so clients couldn't connect Solution: - Add restart limits to van-gps-owntracks and van-li3-battery services (max 3 restarts per 5 minutes prevents infinite restart loops) - Configure mosquitto to listen on all interfaces (0.0.0.0:1883) - Deploy mosquitto listener config via deploy.sh - Restart mosquitto during deploy to apply config changes This prevents the system from hitting the 11-second hardware watchdog timeout when services crash and systemd auto-restarts them indefinitely. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
26 lines
937 B
Plaintext
26 lines
937 B
Plaintext
interface=@WIFI_2G_IFACE@
|
|
# 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
|