ESP8266/Embedded devices unable to connect to 2.4Ghz Radio

I am trying to setup the wireless camera over 2.4ghz access point on 3200ACM running openwrt r6302/r6365 using the latest driver on 3200ACM with all the possible encryption and channels but it just fails after authentication and hence dhcp is unable to detect and allocate an IP to it. Here are the logs that I observed on various settings.

Fri Mar  2 14:07:05 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX IEEE 802.11: associated (aid 4)
Fri Mar  2 14:07:06 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 88:83:5d:XX:XX:XX
Fri Mar  2 14:07:06 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX WPA: pairwise key handshake completed (RSN)
Fri Mar  2 14:07:17 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX IEEE 802.11: authenticated
Fri Mar  2 14:07:51 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 88:83:5d:XX:XX:XX
Fri Mar  2 14:07:51 2018 kern.debug kernel: [43300.431211] ieee80211 phy1: staid 4 deleted

Sat Mar  3 02:53:37 2018 kern.debug kernel: [43405.708782] ieee80211 phy1: staid 4 deleted
Sat Mar  3 02:53:40 2018 daemon.info hostapd: wlan1: STA 88:83:5d:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Sat Mar  3 02:53:41 2018 daemon.notice hostapd: handle_auth_cb: STA 88:83:5d:xx:xx:xx not found
Sat Mar  3 02:53:41 2018 daemon.notice hostapd: handle_auth_cb: STA 88:83:5d:xx:xx:xx not found
Sat Mar  3 02:53:41 2018 daemon.notice hostapd: handle_auth_cb: STA 88:83:5d:xx:xx:xx not found
Sat Mar  3 02:53:43 2018 daemon.info hostapd: wlan1: STA 88:83:5d:xx:xx:xx IEEE 802.11: associated (aid 4)
Sat Mar  3 02:53:43 2018 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 88:83:5d:xx:xx:xx
Sat Mar  3 02:53:44 2018 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 88:83:5d:xx:xx:xx
Sat Mar  3 02:53:45 2018 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 88:83:5d:xx:xx:xx

After allocating static ip:

Fri Mar  2 14:10:22 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX IEEE 802.11: associated (aid 1)
Fri Mar  2 14:10:23 2018 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 88:83:5d:XX:XX:XX
Fri Mar  2 14:10:23 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX WPA: pairwise key handshake completed (WPA)
Fri Mar  2 14:10:23 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX WPA: group key handshake completed (WPA)
Fri Mar  2 14:10:27 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:30 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:33 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:37 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:40 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:43 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:43 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX IEEE 802.11: authenticated
Fri Mar  2 14:10:48 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:51 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:54 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:59 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:11:02 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:11:05 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:11:08 2018 daemon.notice hostapd: wlan1-1: AP-STA-DISCONNECTED 88:83:5d:XX:XX:XX

At first I though it was an issue with dnsmasq, but then I was able to connect the camera with radio2 over 2.4ghz.

AP-STA-POSSIBLE-PSK-MISMATCH?
If static ip is used, why DHCP packets still sent out? BTW, wlan1-1 is used for multi-BSSID? Can you give your setting for the router?

Log 1: Openwrt r6302 (davidc502 build), Kernel 4.9.82, WPA2-PSK-CCMP [10.3.4.0-20180226] Log 3: Openwrt r6302 (davidc502 build), Kernel 4.9.82, multi-wlan1 bssid to test various encryption (WPA/WPA2-PSK-CCMP/TKIP) Log 2: Openwrt r6365 (snapshot), Kernel 4.14.23 (WPA-PSK-CCMP) (switched regular snapshot to use on radio2, since disabled on david's build)

Wireless config:

config wifi-device 'radio0'
    option type 'mac80211'
    option channel '36'
    option hwmode '11a'
    option path 'soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'
    option htmode 'VHT80'
    option disabled '1'

config wifi-iface 'default_radio0'
    option device 'radio0'
    option network 'lan'
    option mode 'ap'
    option ssid 'OpenWrt'
    option encryption 'none'

config wifi-device 'radio1'
    option type 'mac80211'
    option hwmode '11g'
    option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
    option country 'US'
    option legacy_rates '1'
    option htmode 'HT20'
    option txpower '30'
    option channel '2'

config wifi-iface 'default_radio1'
    option device 'radio1'
    option network 'lan'
    option mode 'ap'
    option ssid '2_4_SSID'
    option key 'SECURE_PASS'
    option wmm '0'
    option encryption 'psk2'

5Ghz disabled (different router), 2.4ghz opened for IoT devices (Espressif)

wlan2 (wpa2-psk-ccmp) log:

Sat Mar  3 12:02:22 2018 daemon.info hostapd: wlan2: STA 88:83:5d:xx:xx:xx IEEE 802.11: associated
Sat Mar  3 12:02:24 2018 daemon.notice hostapd: wlan2: AP-STA-CONNECTED 88:83:5d:xx:xx:xx
Sat Mar  3 12:02:24 2018 daemon.info hostapd: wlan2: STA 88:83:5d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sat Mar  3 12:02:25 2018 daemon.info dnsmasq-dhcp[3369]: DHCPDISCOVER(br-lan) 88:83:5d:xx:xx:xx
Sat Mar  3 12:02:25 2018 daemon.info dnsmasq-dhcp[3369]: DHCPOFFER(br-lan) 192.168.1.200 88:83:5d:xx:xx:xx
Sat Mar  3 12:02:25 2018 daemon.info dnsmasq-dhcp[3369]: DHCPREQUEST(br-lan) 192.168.1.200 88:83:5d:xx:xx:xx
Sat Mar  3 12:02:25 2018 daemon.info dnsmasq-dhcp[3369]: DHCPACK(br-lan) 192.168.1.200 88:83:5d:xx:xx:xx Hikam-0505

radio2 went out shortly (12hrs), is it because it's used for DFS scan?

Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.604192] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x16c/0x248
Sat Mar  3 16:49:49 2018 kern.info kernel: [42473.612497] NETDEV WATCHDOG: wlan2 (mwifiex_sdio): transmit queue 1 timed out
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.619665] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT slhc rfcomm nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack mwifiex_sdio mwifiex iptable_mangle iptable_filter ip_tables hidp hci_uart crc_ccitt btusb btmrvl_sdio btmrvl btintel bnep bluetooth hid evdev input_core mwlwifi mac80211 cfg80211 compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables ecdh_generic kpp ecb cmac gpio_button_hotplug
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.687105] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.23 #0
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.693137] Hardware name: Marvell Armada 380/385 (Device Tree)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.699097] [<c010f3d0>] (unwind_backtrace) from [<c010b134>] (show_stack+0x10/0x14)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.706880] [<c010b134>] (show_stack) from [<c060e4c4>] (dump_stack+0x8c/0xa0)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.714137] [<c060e4c4>] (dump_stack) from [<c0121e1c>] (__warn+0xe4/0x100)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.721130] [<c0121e1c>] (__warn) from [<c0121e70>] (warn_slowpath_fmt+0x38/0x48)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.728646] [<c0121e70>] (warn_slowpath_fmt) from [<c053b518>] (dev_watchdog+0x16c/0x248)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.736864] [<c053b518>] (dev_watchdog) from [<c016f340>] (call_timer_fn+0x24/0x98)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.744556] [<c016f340>] (call_timer_fn) from [<c016f510>] (run_timer_softirq+0x15c/0x1e8)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.752857] [<c016f510>] (run_timer_softirq) from [<c01015f0>] (__do_softirq+0xd0/0x21c)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.760986] [<c01015f0>] (__do_softirq) from [<c01265f4>] (irq_exit+0xb0/0xd8)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.768245] [<c01265f4>] (irq_exit) from [<c015d388>] (__handle_domain_irq+0x9c/0xac)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.776111] [<c015d388>] (__handle_domain_irq) from [<c0101438>] (gic_handle_irq+0x58/0x98)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.784499] [<c0101438>] (gic_handle_irq) from [<c010bdcc>] (__irq_svc+0x6c/0x90)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.792013] Exception stack(0xdf465f80 to 0xdf465fc8)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.797087] 5f80: 00000001 00000000 00000000 c0114b60 df464000 c0946410 df465fd8 00000000
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.805301] 5fa0: 00000000 414fc091 00000000 00000000 df465fc8 df465fd0 c01082fc c0108300
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.813513] 5fc0: 60000013 ffffffff
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.817017] [<c010bdcc>] (__irq_svc) from [<c0108300>] (arch_cpu_idle+0x34/0x38)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.824452] [<c0108300>] (arch_cpu_idle) from [<c01540f4>] (do_idle+0xd0/0x188)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.831795] [<c01540f4>] (do_idle) from [<c0154408>] (cpu_startup_entry+0x18/0x1c)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.839398] [<c0154408>] (cpu_startup_entry) from [<001017cc>] (0x1017cc)
Sat Mar  3 16:49:49 2018 kern.warn kernel: [42473.846223] ---[ end trace 13e6eee65b64e4a8 ]---
Sat Mar  3 16:49:49 2018 kern.info kernel: [42473.850868] mwifiex_sdio mmc0:0001:1: 4215929 : Tx timeout(#1), bss_type-num = 1-0
Sat Mar  3 16:49:49 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:49:52 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:49:54 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:49:55 2018 kern.info kernel: [42479.681635] mwifiex_sdio mmc0:0001:1: 4216512 : Tx timeout(#2), bss_type-num = 1-0
Sat Mar  3 16:49:57 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:49:59 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:03 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:05 2018 kern.info kernel: [42489.605060] mwifiex_sdio mmc0:0001:1: 4217504 : Tx timeout(#3), bss_type-num = 1-0
Sat Mar  3 16:50:06 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:09 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:11 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:14 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:15 2018 kern.info kernel: [42499.608485] mwifiex_sdio mmc0:0001:1: 4218504 : Tx timeout(#4), bss_type-num = 1-0
Sat Mar  3 16:50:16 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:19 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:23 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:25 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: associated
Sat Mar  3 16:50:25 2018 kern.info kernel: [42509.621922] mwifiex_sdio mmc0:0001:1: 4219505 : Tx timeout(#5), bss_type-num = 1-0
Sat Mar  3 16:50:26 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:28 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:28 2018 daemon.notice hostapd: wlan2: AP-STA-DISCONNECTED dc:4f:22:84:c1:b5
Sat Mar  3 16:50:28 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: disassociated
Sat Mar  3 16:50:30 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: associated
Sat Mar  3 16:50:31 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:33 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:33 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: disassociated
Sat Mar  3 16:50:35 2018 kern.info kernel: [42519.615359] mwifiex_sdio mmc0:0001:1: 4220504 : Tx timeout(#6), bss_type-num = 1-0
Sat Mar  3 16:50:35 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: associated
Sat Mar  3 16:50:36 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:38 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:38 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: disassociated
Sat Mar  3 16:50:40 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: associated
Sat Mar  3 16:50:41 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: disassociated
Sat Mar  3 16:50:43 2018 daemon.info hostapd: wlan2: STA dc:4f:22:c3:c4:8f IEEE 802.11: associated
Sat Mar  3 16:50:43 2018 daemon.info hostapd: wlan2: STA dc:4f:22:84:c1:b5 IEEE 802.11: disassociated
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.618796] mwifiex_sdio mmc0:0001:1: 4221504 : Tx timeout(#7), bss_type-num = 1-0
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.626403] mwifiex_sdio mmc0:0001:1: tx_timeout_cnt exceeds threshold.   Triggering card reset!
Sat Mar  3 16:50:45 2018 kern.err kernel: [42529.740722] mwifiex_sdio mmc0:0001:1: EVENT: BT coex wlan param update
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.747805] mwifiex_sdio mmc0:0001:1: info: shutdown mwifiex...
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.753848] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.758223] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.762605] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.766978] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.771355] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.775731] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.780109] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.784483] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.788859] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.793233] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.797606] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.801983] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.806357] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.810734] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.warn kernel: [42529.815108] mwifiex: Have pending ack frames!
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.819669] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.825619] mwifiex_sdio mmc0:0001:1: Failed to delete mgmt IEs!
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.831663] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.837609] mwifiex_sdio mmc0:0001:1: Failed to stop the BSS
Sat Mar  3 16:50:45 2018 daemon.notice netifd: Network device 'wlan2' link is down
Sat Mar  3 16:50:45 2018 kern.info kernel: [42529.843651] br-lan: port 2(wlan2) entered disabled state
Sat Mar  3 16:50:45 2018 kern.info kernel: [42530.009044] device wlan2 left promiscuous mode
Sat Mar  3 16:50:45 2018 kern.info kernel: [42530.013511] br-lan: port 2(wlan2) entered disabled state
Sat Mar  3 16:50:45 2018 kern.info kernel: [42530.019016] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
Sat Mar  3 16:50:45 2018 kern.info kernel: [42530.024968] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
Sat Mar  3 16:50:45 2018 kern.info kernel: [42530.030925] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
Sat Mar  3 16:50:45 2018 daemon.notice hostapd: wlan2: AP-STA-DISCONNECTED dc:ef:ca:73:1e:7d
Sat Mar  3 16:50:45 2018 daemon.notice hostapd: wlan2: AP-STA-DISCONNECTED dc:4f:22:c0:f5:13
Sat Mar  3 16:50:45 2018 daemon.notice hostapd: wlan2: INTERFACE-DISABLED
Sat Mar  3 16:50:45 2018 kern.info kernel: [42530.253627] mwifiex_sdio mmc0:0001:1: WLAN FW already running! Skip FW dnld
Sat Mar  3 16:50:45 2018 kern.info kernel: [42530.260664] mwifiex_sdio mmc0:0001:1: WLAN FW is active
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.502536] mwifiex_sdio mmc0:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id = 0xa9, act = 0x0
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.511371] mwifiex_sdio mmc0:0001:1: num_data_h2c_failure = 0
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.517240] mwifiex_sdio mmc0:0001:1: num_cmd_h2c_failure = 0
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.523015] mwifiex_sdio mmc0:0001:1: is_cmd_timedout = 1
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.528437] mwifiex_sdio mmc0:0001:1: num_tx_timeout = 0
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.533777] mwifiex_sdio mmc0:0001:1: last_cmd_index = 0
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.539111] mwifiex_sdio mmc0:0001:1: last_cmd_id: a9 00 28 00 28 00 28 00 b2 00
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.546542] mwifiex_sdio mmc0:0001:1: last_cmd_act: 00 00 93 00 93 00 93 00 00 00
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.554065] mwifiex_sdio mmc0:0001:1: last_cmd_resp_index = 4
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.559835] mwifiex_sdio mmc0:0001:1: last_cmd_resp_id: b5 80 28 80 28 80 28 80 b2 80
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.567703] mwifiex_sdio mmc0:0001:1: last_event_index = 1
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.573215] mwifiex_sdio mmc0:0001:1: last_event: 43 00 76 00 2c 00 2d 00 2c 00
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.580559] mwifiex_sdio mmc0:0001:1: data_sent=1 cmd_sent=1
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.586245] mwifiex_sdio mmc0:0001:1: ps_mode=0 ps_state=0
Sat Mar  3 16:50:56 2018 kern.info kernel: [42540.591899] mwifiex_sdio mmc0:0001:1: info: _mwifiex_fw_dpc: unregister device

Radio 2 is not mwlwifi.
Can you use the same version to test DHCP and static IP? Please get the log for me.
Don't use WEP or TKIP.

Log 1 repeats for DHCP and static IP. If I create a secondary radio on wlan1, I get Log 3. Logread doesn't output anything else, its just keep repeating.

On a single session, after making several changes to the AP(2.4)'s settings, the rest of the devices doesn't seem to get discovered as well. Here are 2 other ESP device's log:

Sun Mar  4 00:13:37 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:13:37 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: disassociated
Sun Mar  4 00:13:37 2018 kern.debug kernel: [69110.826839] ieee80211 phy1: staid 3 deleted
Sun Mar  4 00:13:38 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Mar  4 00:13:40 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:13:40 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:13:40 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 00:13:40 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:13:40 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:13:59 2018 kern.debug kernel: [69132.918797] ieee80211 phy1: staid 3 deleted
Sun Mar  4 00:14:03 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:14:03 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:14:03 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 00:14:06 2018 kern.debug kernel: [69140.408993] ieee80211 phy1: staid 1 deleted
Sun Mar  4 00:14:06 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  4 00:14:06 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:14:06 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 00:14:15 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:14:15 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:14:15 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:14:22 2018 kern.debug kernel: [69156.009745] ieee80211 phy1: staid 3 deleted
Sun Mar  4 00:14:22 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:14:22 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:14:22 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 00:14:38 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:14:42 2018 authpriv.info dropbear[23493]: Child connection from 192.168.1.151:54099
Sun Mar  4 00:14:48 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:14:48 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: disassociated
Sun Mar  4 00:14:48 2018 kern.debug kernel: [69181.811196] ieee80211 phy1: staid 3 deleted
Sun Mar  4 00:14:49 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Mar  4 00:14:51 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:14:51 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:14:51 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 00:15:05 2018 kern.debug kernel: [69199.324638] ieee80211 phy1: staid 1 deleted
Sun Mar  4 00:15:05 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  4 00:15:05 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:15:05 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 00:15:07 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:15:07 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:15:25 2018 kern.debug kernel: [69219.207861] ieee80211 phy1: staid 3 deleted
Sun Mar  4 00:15:25 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:15:25 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:15:25 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)

after successful handshake, does mwlwifi notify about the new device to DHCP?

Second update: Disabling encryption allows all the three devices to login (discovered by DHCP).

Sun Mar  4 00:32:15 2018 daemon.err hostapd: Using interface wlan1 with hwaddr 60:38:e0:xx:xx:xx and ssid "BSSID_NAME"
Sun Mar  4 00:32:15 2018 kern.debug kernel: [70228.922074] ieee80211 phy1: change: 0x100
Sun Mar  4 00:32:15 2018 kern.debug kernel: [70228.935141] ieee80211 phy1: change: 0x42
Sun Mar  4 00:32:15 2018 kern.info kernel: [70229.105066] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Sun Mar  4 00:32:15 2018 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ENABLED
Sun Mar  4 00:32:15 2018 daemon.notice hostapd: wlan1: AP-ENABLED
Sun Mar  4 00:32:15 2018 daemon.notice netifd: Network device 'wlan1' link is up
Sun Mar  4 00:32:16 2018 daemon.notice hostapd: Station dc:4f:22:xx:xx:xx trying to disassociate, but it is not associated
Sun Mar  4 00:32:16 2018 daemon.notice hostapd: Station dc:4f:22:xx:xx:xx trying to disassociate, but it is not associated
Sun Mar  4 00:32:16 2018 daemon.notice hostapd: Station dc:4f:22:xx:xx:xx trying to disassociate, but it is not associated
Sun Mar  4 00:32:16 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  4 00:32:16 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 2)
Sun Mar  4 00:32:16 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.235 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPREQUEST(br-lan) 192.168.1.235 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPACK(br-lan) 192.168.1.235 dc:4f:22:xx:xx:xx ESP_C0F513
Sun Mar  4 00:32:16 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:32:16 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPREQUEST(br-lan) 192.168.1.235 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:16 2018 daemon.info dnsmasq-dhcp[30747]: DHCPACK(br-lan) 192.168.1.235 dc:4f:22:xx:xx:xx ESP_C0F513
Sun Mar  4 00:32:16 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:32:16 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:18 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:18 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:19 2018 kern.debug kernel: [70233.755306] ieee80211 phy1: staid 3 deleted
Sun Mar  4 00:32:19 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:32:19 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:19 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:19 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.249 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:19 2018 daemon.info dnsmasq-dhcp[30747]: DHCPREQUEST(br-lan) 192.168.1.249 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:19 2018 daemon.info dnsmasq-dhcp[30747]: DHCPACK(br-lan) 192.168.1.249 dc:4f:22:xx:xx:xx ESP_84C1B5
Sun Mar  4 00:32:22 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:22 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:22 2018 daemon.info dnsmasq-dhcp[30747]: DHCPREQUEST(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:22 2018 daemon.info dnsmasq-dhcp[30747]: DHCPACK(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx ESP_C3C48F
Sun Mar  4 00:32:27 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:32:27 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:32:55 2018 kern.debug kernel: [70269.223629] ieee80211 phy1: staid 1 deleted
Sun Mar  4 00:32:55 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  4 00:32:55 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:55 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:55 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:57 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:32:57 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:01 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:01 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:01 2018 daemon.info dnsmasq-dhcp[30747]: DHCPREQUEST(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:01 2018 daemon.info dnsmasq-dhcp[30747]: DHCPACK(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx ESP_C3C48F
Sun Mar  4 00:33:02 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 00:33:21 2018 kern.debug kernel: [70295.140470] ieee80211 phy1: staid 3 deleted
Sun Mar  4 00:33:21 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 00:33:21 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:21 2018 daemon.info dnsmasq-dhcp[30747]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:21 2018 daemon.info dnsmasq-dhcp[30747]: DHCPOFFER(br-lan) 192.168.1.249 dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:21 2018 daemon.info dnsmasq-dhcp[30747]: DHCPREQUEST(br-lan) 192.168.1.249 dc:4f:22:xx:xx:xx
Sun Mar  4 00:33:21 2018 daemon.info dnsmasq-dhcp[30747]: DHCPACK(br-lan) 192.168.1.249 dc:4f:22:xx:xx:xx ESP_84C1B5

Please don't disable WMM.

I was trying to find out if any of those were conflicting with this issue, apparently they do not. I have set the wlan to AES only (not auto nor TKIP)

Don't disable WMM and use CCMP only.
Only test with problem client.
Get log for DHCP and static IP. The logs should be different and you should check ping for static IP if connection is established.

This is DHCP, how about static IP?

BTW, aid 2 and 3 are the same kind of client?

I've allocated static ip for all the 3 clients. They're all same kind of client (3) and one camera which is offline.

In this image

I believe the clients have IP on them only because I had them on static list. There is no ip on the hostname if the client does not have a static ip

Removing them from static list, the log (after rebooting router):

Sun Mar  4 04:07:41 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:07:41 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:07:50 2018 authpriv.info dropbear[3371]: Child connection from 192.168.1.151:57119
Sun Mar  4 04:08:07 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:08:07 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: disassociated
Sun Mar  4 04:08:07 2018 kern.debug kernel: [  105.684705] ieee80211 phy1: staid 3 deleted
Sun Mar  4 04:08:08 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Mar  4 04:08:10 2018 kern.debug kernel: [  107.923936] ieee80211 phy1: staid 2 deleted
Sun Mar  4 04:08:10 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 2)
Sun Mar  4 04:08:10 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:08:10 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:08:13 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 04:08:13 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:08:13 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:08:16 2018 daemon.err uhttpd[1810]: luci: accepted login on / for root from 192.168.1.1
Sun Mar  4 04:08:26 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:08:26 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:08:26 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:08:26 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:08:44 2018 kern.debug kernel: [  141.932637] ieee80211 phy1: staid 2 deleted
Sun Mar  4 04:08:44 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 2)
Sun Mar  4 04:08:44 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:08:44 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:08:44 2018 kern.debug kernel: [  142.629431] ieee80211 phy1: staid 3 deleted
Sun Mar  4 04:08:48 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 04:08:48 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:08:48 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:09:22 2018 kern.debug kernel: [  180.723186] ieee80211 phy1: staid 3 deleted
Sun Mar  4 04:09:22 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 04:09:23 2018 kern.debug kernel: [  181.044324] ieee80211 phy1: staid 2 deleted
Sun Mar  4 04:09:23 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 2)
Sun Mar  4 04:09:23 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:09:23 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:09:26 2018 kern.debug kernel: [  184.838938] ieee80211 phy1: staid 3 deleted
Sun Mar  4 04:09:26 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 04:09:28 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:09:28 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:09:34 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:09:34 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:09:34 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:09:34 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:09:34 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:09:34 2018 kern.debug kernel: [  191.989466] ieee80211 phy1: staid 3 deleted
Sun Mar  4 04:09:34 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  4 04:10:06 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 3)
Sun Mar  4 04:10:06 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:10:06 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  4 04:10:07 2018 kern.debug kernel: [  225.251038] ieee80211 phy1: staid 2 deleted
Sun Mar  4 04:10:07 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 2)
Sun Mar  4 04:10:07 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Sun Mar  4 04:10:07 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)

For static IP, it means you set IP to the client, so the client won't ask IP from DHCP server. After connection, if ping is all right, we can make sure data encryption is all right.
Can you just use one client to do the test？

The terminal screenshot in my previous post had devices allocated with static ip and that is when I get "DHCP packet received from wlan1 which has no address"

Setup for only ESP device with static ip and log after a reboot. cat /etc/config/dhcp


config dnsmasq
option domainneeded '1'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.auto'
option nonwildcard '1'
option localservice '1'

config dhcp 'lan' option interface 'lan' option start '100' option limit '150' option leasetime '12h' list dhcp_option '6,8.8.8.8,8.8.4.4'

config dhcp 'wan' option interface 'wan' option ignore '1'

config odhcpd 'odhcpd' option maindhcp '0' option leasefile '/tmp/hosts/odhcpd' option leasetrigger '/usr/sbin/odhcpd-update' option loglevel '4'

config host option name 'DESKTOP-XX' option dns '1' option mac 'xx:xx:xx:xx:xx' option ip '192.168.1.199' option leasetime 'infinite'

config host option name 'VelopNode1' option dns '1' option mac '58:ef:xx:xx:xx:xx' option ip '192.168.1.151' option leasetime 'infinite'

config host option name 'Hikam-0505' option dns '1' option mac '88:83:5d:xx:xx:xx' option ip '192.168.1.200' option leasetime 'infinite'

config host option name 'ESP_C0F513' option dns '1' option mac 'dc:4f:22:xx:xx:xx' option ip '192.168.1.235' option leasetime 'infinite'

cat /etc/config/wireless

config wifi-device 'radio0' option type 'mac80211' option channel '36' option hwmode '11a' option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0' option htmode 'VHT80'

config wifi-iface 'default_radio0' option device 'radio0' option network 'lan' option mode 'ap' option ssid 'OpenWrt' option encryption 'none' option disabled '1'

config wifi-device 'radio1' option type 'mac80211' option hwmode '11g' option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0' option country 'US' option channel '11' option txpower '29' option htmode 'HT20' option legacy_rates '1'

config wifi-iface 'default_radio1' option device 'radio1' option network 'lan' option mode 'ap' option ssid 'SSID' option key 'PASSWORD' option encryption 'psk2+ccmp'


Log:

Sun Mar 4 12:45:37 2018 daemon.err uhttpd[1810]: luci: accepted login on /admin/network/wireless for root from 192.168.1.1 Sun Mar 4 12:45:48 2018 daemon.notice netifd: radio1 (11006): command failed: Not supported (-95) Sun Mar 4 12:45:48 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf Sun Mar 4 12:45:48 2018 kern.debug kernel: [ 546.593951] ieee80211 phy1: change: 0xffffffff Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.683234] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.690075] br-lan: port 2(wlan1) entered blocking state Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.695453] br-lan: port 2(wlan1) entered disabled state Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.700905] device wlan1 entered promiscuous mode Sun Mar 4 12:45:48 2018 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE Sun Mar 4 12:45:48 2018 daemon.err hostapd: Using interface wlan1 with hwaddr 60:38:e0:xx:xx:xx and ssid "SSID" Sun Mar 4 12:45:49 2018 kern.debug kernel: [ 546.756698] ieee80211 phy1: change: 0x100 Sun Mar 4 12:45:49 2018 kern.debug kernel: [ 546.769749] ieee80211 phy1: change: 0x42 Sun Mar 4 12:45:49 2018 kern.info kernel: [ 546.937221] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready Sun Mar 4 12:45:49 2018 kern.info kernel: [ 546.943666] br-lan: port 2(wlan1) entered blocking state Sun Mar 4 12:45:49 2018 kern.info kernel: [ 546.949012] br-lan: port 2(wlan1) entered forwarding state Sun Mar 4 12:45:49 2018 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ENABLED Sun Mar 4 12:45:49 2018 daemon.notice hostapd: wlan1: AP-ENABLED Sun Mar 4 12:45:49 2018 kern.debug kernel: [ 547.027698] ieee80211 phy1: change: 0x20 Sun Mar 4 12:45:49 2018 daemon.notice netifd: Network device 'wlan1' link is up Sun Mar 4 12:45:53 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1) Sun Mar 4 12:45:54 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx Sun Mar 4 12:45:54 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN) Sun Mar 4 12:46:26 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated


Ping: (no response, not even timeout)

root@XXXXX:~# ping 192.168.1.235 PING 192.168.1.235 (192.168.1.235): 56 data bytes

Have you not tried to set a static IP address inside the wireless clients themselves and not within the router that still talks to DHCP.

Sounds like you keep setting a static DHCP lease within the router and not client.

If you set a static IP within the wireless clients and not the router, do you still have these problems?

On Mar 4, 2018 11:50, "Ganesh Kumar" notifications@github.com wrote:

1.

The terminal screenshot in my previous post had devices allocated with static ip and that is when I get "DHCP packet received from wlan1 which has no address" 2.

Setup for only ESP device with static ip and log after a reboot. cat /etc/config/dhcp

config dnsmasq option domainneeded '1' option localise_queries '1' option rebind_protection '1' option rebind_localhost '1' option local '/lan/' option domain 'lan' option expandhosts '1' option authoritative '1' option readethers '1' option leasefile '/tmp/dhcp.leases' option resolvfile '/tmp/resolv.conf.auto' option nonwildcard '1' option localservice '1'

config dhcp 'lan' option interface 'lan' option start '100' option limit '150' option leasetime '12h' list dhcp_option '6,8.8.8.8,8.8.4.4'

config dhcp 'wan' option interface 'wan' option ignore '1'

config odhcpd 'odhcpd' option maindhcp '0' option leasefile '/tmp/hosts/odhcpd' option leasetrigger '/usr/sbin/odhcpd-update' option loglevel '4'

config host option name 'DESKTOP-XX' option dns '1' option mac 'xx:xx:xx:xx:xx' option ip '192.168.1.199' option leasetime 'infinite'

config host option name 'VelopNode1' option dns '1' option mac '58:ef:xx:xx:xx:xx' option ip '192.168.1.151' option leasetime 'infinite'

config host option name 'Hikam-0505' option dns '1' option mac '88:83:5d:xx:xx:xx' option ip '192.168.1.200' option leasetime 'infinite'

config host option name 'ESP_C0F513' option dns '1' option mac 'dc:4f:22:xx:xx:xx' option ip '192.168.1.235' option leasetime 'infinite'

cat /etc/config/wireless

config wifi-device 'radio0' option type 'mac80211' option channel '36' option hwmode '11a' option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0' option htmode 'VHT80'

config wifi-iface 'default_radio0' option device 'radio0' option network 'lan' option mode 'ap' option ssid 'OpenWrt' option encryption 'none' option disabled '1'

config wifi-device 'radio1' option type 'mac80211' option hwmode '11g' option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0' option country 'US' option channel '11' option txpower '29' option htmode 'HT20' option legacy_rates '1'

config wifi-iface 'default_radio1' option device 'radio1' option network 'lan' option mode 'ap' option ssid 'SSID' option key 'PASSWORD' option encryption 'psk2+ccmp' option disabled '1'

Logs:

Sun Mar 4 12:45:37 2018 daemon.err uhttpd[1810]: luci: accepted login on /admin/network/wireless for root from 192.168.1.1 Sun Mar 4 12:45:48 2018 daemon.notice netifd: radio1 (11006): command failed: Not supported (-95) Sun Mar 4 12:45:48 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf Sun Mar 4 12:45:48 2018 kern.debug kernel: [ 546.593951] ieee80211 phy1: change: 0xffffffff Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.683234] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.690075] br-lan: port 2(wlan1) entered blocking state Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.695453] br-lan: port 2(wlan1) entered disabled state Sun Mar 4 12:45:48 2018 kern.info kernel: [ 546.700905] device wlan1 entered promiscuous mode Sun Mar 4 12:45:48 2018 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE Sun Mar 4 12:45:48 2018 daemon.err hostapd: Using interface wlan1 with hwaddr 60:38:e0:xx:xx:xx and ssid "SSID" Sun Mar 4 12:45:49 2018 kern.debug kernel: [ 546.756698] ieee80211 phy1: change: 0x100 Sun Mar 4 12:45:49 2018 kern.debug kernel: [ 546.769749] ieee80211 phy1: change: 0x42 Sun Mar 4 12:45:49 2018 kern.info kernel: [ 546.937221] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready Sun Mar 4 12:45:49 2018 kern.info kernel: [ 546.943666] br-lan: port 2(wlan1) entered blocking state Sun Mar 4 12:45:49 2018 kern.info kernel: [ 546.949012] br-lan: port 2(wlan1) entered forwarding state Sun Mar 4 12:45:49 2018 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ENABLED Sun Mar 4 12:45:49 2018 daemon.notice hostapd: wlan1: AP-ENABLED Sun Mar 4 12:45:49 2018 kern.debug kernel: [ 547.027698] ieee80211 phy1: change: 0x20 Sun Mar 4 12:45:49 2018 daemon.notice netifd: Network device 'wlan1' link is up Sun Mar 4 12:45:53 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1) Sun Mar 4 12:45:54 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx Sun Mar 4 12:45:54 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN) Sun Mar 4 12:46:26 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated

Ping: (no response, not even timeout)

root@XXXXX:~# ping 192.168.1.235 PING 192.168.1.235 (192.168.1.235): 56 data bytes

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kaloz/mwlwifi/issues/278#issuecomment-370248739, or mute the thread https://github.com/notifications/unsubscribe-auth/ARIphG_fVsnqSeB2CJi-JP1_Wff9s1SFks5tbCl6gaJpZM4Sa2UI .

@rs-se the problem is these are ESP8285 based devices and configuring static ip is not possible because they run proprietary firmware. I am not sure about the camera's wifi module but all these devices can be configured from their respective apps to join 2.4Ghz networks.

As of now the devices connect without issues to the radio2 on 3200acm (which is not mwlwifi, dhcp discovers it) and my velop mesh nodes.

So this issue is related to ESP8285?
Can you let me know version of mwlwifi and firmware.
Please use monitor mode to check if DHCP packets can be received. You can use open to check it first, then check via security. Thanks.

I don't think so because these are able to join other networks.

kmod-mwlwifi - 4.14.23+2018-02-26-51350a3e-1
mwlwifi-firmware-88w8964 - 2018-02-26-51350a3e-1

phy0

driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version: 10.3.4.0-20180226
firmware version: 0x09030205
power table loaded from dts: no
firmware region code: 0x10
mac address: 60:38:e0:xx:xx:xx
2g: disable
5g: enable
antenna: 4 4
irq number: 50
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000000
radio: disable
iobase0: e0e00000
iobase1: e1080000
tx limit: 1024
rx limit: 16384

phy1:

driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version: 10.3.4.0-20180226
firmware version: 0x09030205
power table loaded from dts: no
firmware region code: 0x10
mac address: 60:38:e0:xx:xx:xx
2g: enable
5g: disable
antenna: 4 4
irq number: 51
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000000
radio: disable
iobase0: e1200000
iobase1: e1480000
tx limit: 1024
rx limit: 16384

I did not get you, how do I capture DHCP packets in monitor mode again?

PS: I was going through this issue https://github.com/kaloz/mwlwifi/issues/242, I see similar issue with authentication.

I just want to make sure the client is ESP8285.
Using following commands to create monitor interface: iw wlan0/wlan1 interface add mon0 type monitor ifconfig mon0 up
The way to dump dhcp packets: tcpdump -vvvi mon0 -n port 67 and port 68
The way to dump icmp packets: tcpdump -vvvi mon0 icmp

Please use open to test and get log:

Prepare mon0 to dump dhcp packets and then connect client to AP.
Prepare mon0 to dump icmp packets, try to ping AP from client after connection is established.

Run the same test under security mode and get log.

Had one ESP client running, right after enabling wlan1 and setting up the monitor mode it connected! I tried turned on all the clients as of now and DHCP allocated the static ip. Had the clients connected over wlan2 for the previous 18hrs. This is bizarre.

Will continue to monitor them and report with monitor logs if it occurs.

Apologies, due to my absent mindedness, I forgot to look at the encryption being disabled. So I followed your steps to get mon0 up and monitoring tcpdump.

Mon Mar  5 23:55:53 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 2)
Mon Mar  5 23:55:53 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
Mon Mar  5 23:55:53 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Mon Mar  5 23:56:17 2018 daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
Mon Mar  5 23:56:52 2018 kern.debug kernel: [111031.348942] ieee80211 phy1: staid 2 deleted

root@HOST:~# tcpdump -vvvi mon0 icmp
tcpdump: listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes

root@HOST:~# tcpdump -vvvi mon0 -n port 67 and port 68
tcpdump: listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes

I do not happen to see any connection/dhcp packet on the tcpdumps. Tried pinging the client with static ip allocated, but no response.

Please use open mode to do the test first:

Set AP to open mode.
Issue "tcpdump -vvvi mon0 -n port 67 and port 68" and connect client to AP (get the log from tcpdump).
Stop tcpdump (ctrl-C).
Issue "tcpdump -vvvi mon0 icmp"
Ping from cilent and get log from tcpdump).

Since open mode is all right according to your description, tcpdump should get DHCP and Ping packets.

Run the same test for security mode, I want to know if DHCP packets can be received by the router.

Finally, run the test for security mode but set static IP to client.

Here you go:

root@openwrt:~# iw wlan1 interface add mon0 type monitor
root@openwrt:~# ifconfig mon0 up
root@openwrt:~# iw wlan1 info
Interface wlan1
    ifindex 7343
    wdev 0x1000007ab
    addr 60:38:e0:xx:xx:xx
    ssid SSID
    type AP
    wiphy 1
    channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz
    txpower 30.00 dBm
root@openwrt:~# uci show wireless.radio1
wireless.radio1=wifi-device
wireless.radio1.type='mac80211'
wireless.radio1.hwmode='11g'
wireless.radio1.path='soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
wireless.radio1.country='US'
wireless.radio1.channel='11'
wireless.radio1.htmode='HT20'
wireless.radio1.legacy_rates='1'
wireless.radio1.txpower='30'
root@openwrt:~# uci show wireless.default_radio1
wireless.default_radio1=wifi-iface
wireless.default_radio1.device='radio1'
wireless.default_radio1.network='lan'
wireless.default_radio1.ssid='SSID'
wireless.default_radio1.key='PASSWORD'
wireless.default_radio1.mode='ap'
wireless.default_radio1.encryption='psk2'

# changing encryption to nothing

root@openwrt:~# uci set wireless.default_radio1.encryption=''
root@openwrt:~# uci commit wireless; wifi
root@openwrt:~# iw wlan1 interface add mon0 type monitor
root@openwrt:~# ifconfig mon0 up

root@openwrt:~# tcpdump -vvvi mon0 -n port 67 and port 68
tcpdump: listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes
tcpdump: pcap_loop: The interface went down
0 packets captured
2 packets received by filter
0 packets dropped by kernel

# bringing mon0 up again after commit

root@openwrt:~# tcpdump -vvvi mon0 -n port 67 and port 68
tcpdump: listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes
09:51:27.370789 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 255, id 9992, offset 0, flags [none], proto UDP (17), length 336)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from dc:4f:22:xx:xx:xx, length 308, xid 0xc4daac6a, Flags [none] (0x0000)
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Discover
        MSZ Option 57, length 2: 1500
        Hostname Option 12, length 10: "ESP_C3C48F"
        Parameter-Request Option 55, length 12: 
          Subnet-Mask, Default-Gateway, BR, Domain-Name-Server
          Domain-Name, Netbios-Name-Server, Netbios-Node, Netbios-Scope
          Router-Discovery, Static-Route, Classless-Static-Route, Vendor-Option
        END Option 255, length 0
        PAD Option 0, length 0, occurs 34
09:51:27.371232 6.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 17190, offset 0, flags [none], proto UDP (17), length 329)
    192.168.1.1.67 > 192.168.1.223.68: [udp sum ok] BOOTP/DHCP, Reply, length 301, xid 0xc4daac6a, Flags [none] (0x0000)
      Your-IP 192.168.1.223
      Server-IP 192.168.1.1
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Offer
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 43200
        RN Option 58, length 4: 21600
        RB Option 59, length 4: 37800
        Subnet-Mask Option 1, length 4: 255.255.255.0
        BR Option 28, length 4: 192.168.1.255
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name Option 15, length 3: "lan"
        Domain-Name-Server Option 6, length 8: 8.8.8.8,8.8.4.4
        END Option 255, length 0
09:51:29.163009 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 255, id 9993, offset 0, flags [none], proto UDP (17), length 336)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from dc:4f:22:xx:xx:xx, length 308, xid 0xc4daac6a, Flags [none] (0x0000)
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Discover
        MSZ Option 57, length 2: 1500
        Hostname Option 12, length 10: "ESP_C3C48F"
        Parameter-Request Option 55, length 12: 
          Subnet-Mask, Default-Gateway, BR, Domain-Name-Server
          Domain-Name, Netbios-Name-Server, Netbios-Node, Netbios-Scope
          Router-Discovery, Static-Route, Classless-Static-Route, Vendor-Option
        END Option 255, length 0
        PAD Option 0, length 0, occurs 34
09:51:29.163511 [bit 15] IP (tos 0xc0, ttl 64, id 17265, offset 0, flags [none], proto UDP (17), length 329)
    192.168.1.1.67 > 192.168.1.223.68: [udp sum ok] BOOTP/DHCP, Reply, length 301, xid 0xc4daac6a, Flags [none] (0x0000)
      Your-IP 192.168.1.223
      Server-IP 192.168.1.1
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Offer
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 43200
        RN Option 58, length 4: 21600
        RB Option 59, length 4: 37800
        Subnet-Mask Option 1, length 4: 255.255.255.0
        BR Option 28, length 4: 192.168.1.255
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name Option 15, length 3: "lan"
        Domain-Name-Server Option 6, length 8: 8.8.8.8,8.8.4.4
        END Option 255, length 0
09:51:33.151352 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 255, id 9994, offset 0, flags [none], proto UDP (17), length 336)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from dc:4f:22:xx:xx:xx, length 308, xid 0xc4daac6a, Flags [none] (0x0000)
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Discover
        MSZ Option 57, length 2: 1500
        Hostname Option 12, length 10: "ESP_C3C48F"
        Parameter-Request Option 55, length 12: 
          Subnet-Mask, Default-Gateway, BR, Domain-Name-Server
          Domain-Name, Netbios-Name-Server, Netbios-Node, Netbios-Scope
          Router-Discovery, Static-Route, Classless-Static-Route, Vendor-Option
        END Option 255, length 0
        PAD Option 0, length 0, occurs 34
09:51:33.151817 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 17502, offset 0, flags [none], proto UDP (17), length 329)
    192.168.1.1.67 > 192.168.1.223.68: [udp sum ok] BOOTP/DHCP, Reply, length 301, xid 0xc4daac6a, Flags [none] (0x0000)
      Your-IP 192.168.1.223
      Server-IP 192.168.1.1
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Offer
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 43200
        RN Option 58, length 4: 21600
        RB Option 59, length 4: 37800
        Subnet-Mask Option 1, length 4: 255.255.255.0
        BR Option 28, length 4: 192.168.1.255
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name Option 15, length 3: "lan"
        Domain-Name-Server Option 6, length 8: 8.8.8.8,8.8.4.4
        END Option 255, length 0
09:51:33.161433 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 255, id 9995, offset 0, flags [none], proto UDP (17), length 336)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from dc:4f:22:xx:xx:xx, length 308, xid 0x87a54e1, Flags [none] (0x0000)
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Request
        MSZ Option 57, length 2: 1500
        Requested-IP Option 50, length 4: 192.168.1.223
        Server-ID Option 54, length 4: 192.168.1.1
        Parameter-Request Option 55, length 12: 
          Subnet-Mask, Default-Gateway, BR, Domain-Name-Server
          Domain-Name, Netbios-Name-Server, Netbios-Node, Netbios-Scope
          Router-Discovery, Static-Route, Classless-Static-Route, Vendor-Option
        Hostname Option 12, length 10: "ESP_C3C48F"
        END Option 255, length 0
        PAD Option 0, length 0, occurs 22
09:51:33.161915 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 17503, offset 0, flags [none], proto UDP (17), length 329)
    192.168.1.1.67 > 192.168.1.223.68: [udp sum ok] BOOTP/DHCP, Reply, length 301, xid 0x87a54e1, Flags [none] (0x0000)
      Your-IP 192.168.1.223
      Server-IP 192.168.1.1
      Client-Ethernet-Address dc:4f:22:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: ACK
        Server-ID Option 54, length 4: 192.168.1.1
        Lease-Time Option 51, length 4: 43200
        RN Option 58, length 4: 21600
        RB Option 59, length 4: 37800
        Subnet-Mask Option 1, length 4: 255.255.255.0
        BR Option 28, length 4: 192.168.1.255
        Default-Gateway Option 3, length 4: 192.168.1.1
        Domain-Name Option 15, length 3: "lan"
        Domain-Name-Server Option 6, length 8: 8.8.8.8,8.8.4.4
        END Option 255, length 0
^C
8 packets captured
8 packets received by filter
0 packets dropped by kernel

root@openwrt:~# tcpdump -vvvi mon0 icmp
tcpdump: listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes
09:44:33.637280 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 64, id 59337, offset 2960, flags [none], proto ICMP (1), length 68)
    172.20.20.20 > 172.20.20.1: icmp
09:45:18.723786 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 64, id 36034, offset 2960, flags [none], proto ICMP (1), length 68)
    172.20.20.20 > 172.20.20.1: icmp
09:45:31.422138 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 64, id 60039, offset 2960, flags [none], proto ICMP (1), length 68)
    172.20.20.20 > 172.20.20.1: icmp
09:49:16.399876 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 64, id 5584, offset 2960, flags [none], proto ICMP (1), length 68)
    172.20.20.20 > 172.20.20.1: icmp
tcpdump: pcap_loop: The interface went down
4 packets captured
4 packets received by filter
0 packets dropped by kernel

#getting mon0 up again

root@openwrt:~# tcpdump -vvvi mon0 icmp
tcpdump: listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes
09:51:36.152332 2.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 63580, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 9998, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:39.141206 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 63806, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10000, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:40.130078 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 63834, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10001, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:41.119908 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 63910, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10003, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:43.110549 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 63945, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10005, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:44.805429 1.0 Mb/s 2462 MHz 11b 0dBm signal antenna 0 IP (tos 0x0, ttl 64, id 60163, offset 0, flags [DF], proto ICMP (1), length 72)
    172.20.20.1 > 172.20.20.20: ICMP echo reply, id 1611, seq 1, length 52
09:51:47.069355 2.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 64085, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10011, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:48.061170 1.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 64176, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10012, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:50.049335 [bit 15] IP (tos 0xc0, ttl 64, id 64371, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10014, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:54.040579 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 64517, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10016, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:55.030141 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 64531, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10017, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:56.026488 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 64609, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10018, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:51:58.001075 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 64725, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10020, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:01.990393 [bit 15] IP (tos 0xc0, ttl 64, id 65034, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10022, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:02.979849 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 65055, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10024, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:04.977891 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 65191, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10025, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:07.970345 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 65354, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10027, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:08.971615 [bit 15] IP (tos 0xc0, ttl 64, id 65385, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10029, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:09.962487 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 65422, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10030, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:11.951276 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 65444, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10032, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:15.940014 2.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 65484, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10034, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:16.929977 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 5, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10035, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:18.878399 1.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 78, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10044, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:22.870646 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 399, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10046, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:23.860260 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 480, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10048, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:24.849949 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 542, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10049, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:26.851893 2.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 560, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-a.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10051, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-a.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:30.820435 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 820, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10053, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:31.810006 5.5 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 851, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10054, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
09:52:33.790113 2.0 Mb/s [bit 15] IP (tos 0xc0, ttl 64, id 886, offset 0, flags [none], proto ICMP (1), length 90)
    CyFi.lan > ESP_C3C48F.lan: ICMP google-public-dns-b.google.com udp port 53 unreachable, length 70
    IP (tos 0x0, ttl 254, id 10056, offset 0, flags [none], proto UDP (17), length 62)
    ESP_C3C48F.lan.49153 > google-public-dns-b.google.com.53: [udp sum ok] 0+ A? mq.gw.tuyaus.com. (34)
^C
30 packets captured
30 packets received by filter
0 packets dropped by kernel

daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
kern.debug kernel: [147108.775654] ieee80211 phy1: staid 1 deleted
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1)
daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated
kern.debug kernel: [147157.746569] ieee80211 phy1: staid 1 deleted
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1)
daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx WPA: pairwise key handshake completed (RSN)
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated

# rebooting wlan1 without encryption

kern.info kernel: [147208.126601] device wlan1 left promiscuous mode
kern.info kernel: [147208.131207] br-lan: port 2(wlan1) entered disabled state
daemon.notice hostapd: wlan1: interface state ENABLED->DISABLED
daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED dc:4f:22:xx:xx:xx
daemon.notice netifd: radio2 (10768): Could not find PHY for device 'radio2'
daemon.notice netifd: radio2 (10790): WARNING: Variable 'data' does not exist or is not an array/object
daemon.notice hostapd: wlan1: AP-DISABLED
daemon.notice hostapd: wlan1: CTRL-EVENT-TERMINATING
daemon.notice hostapd: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
daemon.notice netifd: radio0 (10783): command failed: Not supported (-95)
daemon.notice hostapd: nl80211: Failed to remove interface wlan1 from bridge br-lan: Invalid argument
kern.debug kernel: [147208.296360] ieee80211 phy1: staid 1 deleted
kern.debug kernel: [147208.314028] ieee80211 phy1: change: 0x40
kern.debug kernel: [147208.395013] ieee80211 phy1: change: 0x100
daemon.notice netifd: radio1 (10837): command failed: Not supported (-95)
daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
kern.debug kernel: [147208.985220] ieee80211 phy1: change: 0xffffffff
kern.info kernel: [147209.074433] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
kern.info kernel: [147209.081237] br-lan: port 2(wlan1) entered blocking state
kern.info kernel: [147209.086678] br-lan: port 2(wlan1) entered disabled state
kern.info kernel: [147209.092222] device wlan1 entered promiscuous mode
kern.info kernel: [147209.097060] br-lan: port 2(wlan1) entered blocking state
kern.info kernel: [147209.102490] br-lan: port 2(wlan1) entered forwarding state
daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
daemon.err hostapd: Using interface wlan1 with hwaddr 60:38:e0:xx:xx:xx and ssid "SSID"
kern.debug kernel: [147209.108943] ieee80211 phy1: change: 0x100
kern.debug kernel: [147209.122078] ieee80211 phy1: change: 0x42
kern.info kernel: [147209.272310] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ENABLED
daemon.notice hostapd: wlan1: AP-ENABLED
daemon.notice netifd: Network device 'wlan1' link is up
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: associated (aid 1)
daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:4f:22:xx:xx:xx
daemon.info dnsmasq-dhcp[3326]: DHCPDISCOVER(br-lan) dc:4f:22:xx:xx:xx
daemon.info dnsmasq-dhcp[3326]: DHCPOFFER(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
daemon.info dnsmasq-dhcp[3326]: DHCPREQUEST(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx
daemon.info dnsmasq-dhcp[3326]: DHCPACK(br-lan) 192.168.1.223 dc:4f:22:xx:xx:xx ESP_C3C48F
daemon.info hostapd: wlan1: STA dc:4f:22:xx:xx:xx IEEE 802.11: authenticated

PS: I have the client blocked from accessing the internet (hence the port 53 unreachable)

I also flashed factory image (FW_WRT3200ACM_1.0.6.186168_prod) to check if there was something wrong with the hardware but the clients were able to join 2.4ghz radio AP.

Hi! Can you check the arp tables on the clients? On my wrt1200 with 802.11w enabled arp broadcast are not delivered after some time. But im also not sure if this a client bug. Maybe this is somehow related?

In your case it seems like with encryption(ccmp) enabled arp broadcast are not transmitted somehow?

@schm0 I'm afraid, I can't. These clients run embedded programs and do not have an interface to debug. You can either flash the firmware with config stating the WiFi credentials or configure them via web interface if supported. I suspect the device state after authentication.

The other thing that also bothers me is that my phone/macbook gets connected to 2.4Ghz AP but not these NodeMCU(ESP8266)/Cameras (Clients) on 2.4Ghz AP. These connect to factory firmware on 3200acm and also different routers with same SSID/encryption.

For me it is bit different. With 802.11w enabled: The clients can always ping the router. Also other clients but only for a short time after they associated. When they ARP entries expire, the communication under the clients breaks because the ARP broadcasts are not delivered anymore. However the router's ARP table is always well populated and clients can browse the web just fine.

Esp8266 it is possible to run static with ESP8266 basic I do it all the time actually. I did a fairly cool home automation project with these and use static IP's.

Aside from that my lack of knowledge of this project my comment not having logs etc no raw data I understand it may be a useless comment.

Something I have noticed is DDWRT has a problem with mixed mode encryption on the WRT3200ACM it does effect the ability to connect. AES from my experience is best in the case.

1 of my access points is seen with my phone. But when I run wifi analyzer the access points show up but the SSID's show up as asteriks.

The other issue I should share is if you do any daily reboots they always force the router into a condition where you have to manually get the router back up and running on a couple occasions I had to reset the router completely to get it running. So there is something that is being missed somewhere as to why these things happen.

RECAP OF WHAT I AM SHARING: Daily scheduled reboots = Cause issues. DDWRT latest version Cryptographic Method Mixed = Cause issues. DDWRT latest version ESP8266 Basic = Allows for static IP Configuration Just fine Android Wifi Analyzer = Sees WRT3200ACM wifi connections SSID's as ** Asteriks If certain configurations are in play.

What this means how to fix it or if it will provide any help just simple observations from a simple minded person. I am almost at the point of getting a refund on this router now that belkin is being purchased by foxconn and such it is hard to say if anything will be fixed or pushed to be fixed. Although this at current is arguably their flagship product if they want to gain any support under the foxconn name.

I was kinda hoping to see some results and then I seen the Belkin get aquired by foxconn.

I will state that my WRT3200ACM is also an RM2 which they have recently released as a remanufactured item more or less.

@forlotto hey i'm the dd-wrt developer. one comment for mixed connections. with mixed connections (aes+tkip) for instance group keys will be always tkip. otherwise broadcast cannot work between clients. but tkip will always disable 802.11n and 802.11ac operation. so never use tkip+aes, but aes only for full 802.11n and 802.11ac operation. by specification tkip is not allowed for 802.11n and 802.11ac. this will also explain any dhcp issues since dhcp packets are broadcast based. so use only AES only for 802.11n and 802.11ac.

in addition. dd-wrt does ignore this specification and does allow tkip in 802.11n and 802.11ac, but your esp8266 will not. so this will create incompatiblities. so this special type of operation will only work between dd-wrt based devices (in client and ap modes). but tkip encryption does prevent packet aggregation so its not recommended to use tkip in any way. its obsolete and a insecure protocol

@brainslayer thx for this oddly I never had these problems on my EA6500 or other ac routers in mixed mode same with the E4200 older solid wireless N performer mixed mode I can scan with wifi analyzer zero issues the SSID's don't turn from SSIDNAME to **** it is an odd problem that only exhibits it's self on the wrt3200ACM (RM2 in my case) err I feel as if I am hijacking the thread I just was curious if the same things were consistent with this project as well as a host of other oddities. Enlightening though I did subscribe to the TKIP fallacy based on too many people pushing it for compatibility I looked into it but wasn't aware of links in speed or that it was insecure I do know that it essentially salts the SSID with the passphrase beyond that I knew very little. After you posting this I feel stupid for knowing so much and missing this based on a fallacy. I was unaware that it was specification driven rather than device driven compatibility more or less which kills me that people promote it so openly as a compatibility must have. Nearly all instances I know of personally be it business or household it is pointless to use TKIP these days after knowing this! I cannot think of a single scenario where I would suggest the use of TKIP anymore! I feel dumb here. It makes me wonder if other people are not experiencing the same issues due to this heavily promoted fallacy. I will say it is however very obvious there are still problems with this router scheduled reboots with this router cause issues and it may be due to TKIP or it may not be I am not sure now but there is a lot of strangeness going on with this router.

Oddly in the case of ESP devices, it has caused me zero issues when using the EA6500 and the E4200 to use "compatibility mode" or mixed mode WPA2 everything worked as planned 3 AP's zero issues 6 ESP's about 10 devices many wired devices. But I upgraded now that I have a 1GB/1GB connection. Including this, a switch and an edge router to my network to achieve 1GB speeds real 1GB speeds. https://www.speedtest.net/my-result/d/4e7e2f10-9d8e-4648-832f-e0f2b428e2c3

But never the less I wanted better LAN throughput essentially so I opted for this router. As a side question in this, what router do you recommend for best heavy traffic multiple connections to run DD-WRT at this point in time and distance? I figured it would be this router but there are far too many issues with it and I live down the road from a small town airport so it could be part of my issue with this router I suppose but when daily reboots cause issues non recoverable from just removing power it makes me wonder what else is up.

But I thank you for your help very revealing a huge fallacy I had kept in my education in the case of TKIP time to fix this and fix my brain. I have a great dislike for fallacies more and more I am less inclined to take peoples word for anything even with things like OpenVPN for instance. I feel stupid for not seeing what was obvious in speed during my testing but I assumed changes may have been linked to location and beamforming bad assumption how foolish man I feel a bit gullible for this one a huge mistake on my part. But this fallacy was plastered everywhere and preached by even the likes of Cisco back in 2010 ish which makes sense there were more G devices in operation back then.

There are still problems with this router clearly I am very inclined to return it and opt for a different model. Another interesting thing from a security standpoint it would be nice to somehow mask the hardware being used in DD-WRT to make it difficult for attackers targeting specific equipment, for example, the latest Microtik exploits and so forth. It would be great to mask this info somehow to the outside I so wish it was possible obscurity, in this case, may help network security to a large degree. So many attacks now hardware focused out in the open are a new angle to worry about now that the cat is out of the bag with vault 7 release and so on.

Anyways I thank you very much for your response. @iganeshk And Sincerely apologize to all for the hijack potential of this all I just figured the experiences I had may be of help it was not my intention to get to this point.

Hello,

i am having the same issue with my ESP8266 devices on my WRT3200ACM on 2G wlan1 interface. They seem to connect but do not get an IP address via DHCP.

Do you have an solution for this issue?

Thanks.

@marc-o94 at the moment @yuhhaurlin seems to be working on mu-mimo only, right now. You can try using the radio2 for the time being.

I read your posts that you are also having issues with radio2 when DFS kicks in. I am having the same issue with this radio. How did you solve this issue? Reboot the router every time it is disconnected?

I experienced radio2 issues a lot when devices disconnect. I couldn't pin point the root cause of the radio malfunction but if you keep the devices connected and prevent them from disconnecting, it would be stable enough.

Is this module the correct one that I should try?

Or anyone can take picture of your device and post here, so I can try to get one to do test. Thanks.

@yuhhaurlin You could try these:

NodeMCU (Original/Compatible) using ESP8266 - AliExpress

WLAN Adapter using RTL8188EUS - AliExpress

Thanks for your information.

Hello,

Had the exact same error code with a device that uses an esp8266. My search for an answer went to this thread and I have an WRT3200ACM. However, I was using an old netgear router (ar71xx) running openwrt. It was the exact same error listed on the logs posted above. Of course the device would not connect to the WRT3200ACM and had the same error.

The exact chip in the device is an ESP-WROOM-02 this chip is based on the esp8266.

Found the solution when reading the forums for some users and it was recommended to turn Wireless "N" off and use only Wireless "G". That worked but not really happy about the solution. The esp8266 is supposed to support b/g/n.

I guess it could be something else going on other than the mwlwifi driver. This is above my knowledge level but wanted to throw this out there as another data point. I would be glad to get additional information if needed.

Thanks

Updated post -1: After more testing. I think the problem lies with the esp8266 at least on the iot device I have. I found out it that the iot device will make a reliable connection with wireless "N" mode every time if I turned the device off and on again. Strange looks like the esp8266 needs a hard reset to make a reliable connection at least with my netgear and wrt3200acm. For the iot device I am using it is not a problem to turn off and on (the device adjusts the temperature on a charcoal grill). Just another data point.

Updated post - 2: All tests with the wrt3200acm. Wireless "N" connects after turning iot device on and off, but after 15-20 minutes the device disconnects and does not reconnect unless I turn the iot device on and off.

Using Wireless "G" only mode for 3 hours and so far no disconnects.

Will continue to monitor.

I recently acquired a wifi-enabled RGB LED strip. This device seems to be based on a ESP chip (as implied by the name sent to the DHCP server). It connects fine to radio2, but on radio1 DHCP packets seem to be lost: hostapd accepts the connection, but then dnsmasq does not log any request.

The ESP is embedded in the device, I cannot confirm its firmware version, or even wether it's a ESP8266 or a ESP32.

If it is a MagicHome RGB controller, an ESP12S or ESP8285 (older version) will be installed (I have the same device running here). If the WMM option is switched off, the device runs perfectly on radio-1.

But I flashed the firmware with Tasmota. Would be possible that the compatibility increased thereby.

Yes, it's just a "Magic Home" device, relabeled to something else. But this device only works on the 2.4GHz band (radio1 on the WRT32000ACM, if I am not mistaken).

I do not think I want to disable WMM, however.

I'll probably have a look to that firmware, thanks for the tip.

(Of course, radio-1 not 0)

I operate an additional WLAN network on the radio-1 where my IoT devices are, with the WMM option turned off.

kaloz / mwlwifi

ESP8266/Embedded devices unable to connect to 2.4Ghz Radio #278