Hi, I have WL1837MOD WiFi module in AP mode. Our device use Linux OS, kernel 4.14.138. From kernel log:
wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
wlcore: loaded
wlcore: PHY firmware version: Rev 8.2.0.0.242
wlcore: firmware booted (Rev 8.9.0.0.79)
It works fine in the most cases, but sometimes (seldom) it starts and doesn't work. In this case fwlog is full of "Tx Beacon: Beacon Expiry. Consecutive Beacon Miss" messages, see attached 45407450.csv log file. AP cannot be discovered by scan. Hostapd status looks fine:
state=ENABLED
phy=phy5
freq=2462
num_sta_non_erp=0
num_sta_no_short_slot_time=0
num_sta_no_short_preamble=0
olbc=0
num_sta_ht_no_gf=0
num_sta_no_ht=0
num_sta_ht_20_mhz=0
num_sta_ht40_intolerant=0
olbc_ht=0
ht_op_mode=0x0
cac_time_seconds=0
cac_time_left_seconds=N/A
channel=11
secondary_channel=0
ieee80211n=1
ieee80211ac=0
ieee80211ax=0
beacon_int=100
dtim_period=2
ht_caps_info=000c
ht_mcs_bitmask=ff000000000000000000
supported_rates=02 04 0b 16 0c 12 18 24 30 48 60 6c
max_txpower=30
bss[0]=wlan02
bssid[0]=7e:ec:79:f9:0a:10
ssid[0]=WiFi_AP2_55_56_access_list
num_sta[0]=0
Unload/reload of kernel module and restart of hostapd helps. AP is located in laboratory with many (more than about 30) other APs around.
My questions:
- What this message mean - exactly?
- Was beacon actually sent or not if this message occurs?
