I have three Amazon echo devices (Echo dot 2nd Gen, Echo dot 3rd Gen and Echo Show 5 1st Gen). Since I have configured OpenWrt on my router these devices keeps losing wifi connection randomly and then picks them back up again after few hours. I have tried to change the DTIM interval value to (1, 2 ,3) on the IOT wifi interface but that doesn't seem to impact the connection dropouts.
I have three VLAN's configured on my Belkin RT3200:
LAN - Phones/Tablets/Laptops
IOT - For smart devices
Guest - Wireguard VPN
Here us the network config
package network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdf5:d78d:0440::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config interface 'lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option device 'br-lan.99'
config interface 'wan'
option device 'wan'
option proto 'dhcp'
option peerdns '0'
list dns '208.67.220.220'
list dns '208.67.222.222'
config interface 'wan6'
option device 'wan'
option proto 'dhcpv6'
list dns '2620:119:35::35'
list dns '2620:119:53::53'
option peerdns '0'
config bridge-vlan
option device 'br-lan'
option vlan '3'
list ports 'lan2:t'
config bridge-vlan
option device 'br-lan'
option vlan '4'
list ports 'lan2:t'
config bridge-vlan
option device 'br-lan'
option vlan '99'
list ports 'lan1:u*'
list ports 'lan2:t'
config interface 'IOT'
option device 'br-lan.3'
option proto 'static'
option ipaddr '192.168.3.1'
option netmask '255.255.255.0'
list dns '208.67.220.220'
list dns '208.67.222.222'
config interface 'Guest'
option proto 'static'
option device 'br-lan.4'
option ipaddr '192.168.4.1'
option netmask '255.255.255.0'
list dns '162.252.172.57'
list dns '149.154.159.92'
config rule
option in 'lan'
option lookup '100'
config rule
option in 'IOT'
option lookup '100'
config route
option interface 'wan'
option target '0.0.0.0'
option netmask '0.0.0.0'
option metric '200'
option table '100'
config interface 'wg0'
option proto 'wireguard'
option private_key 'IEvLBV8S5tuHJGVCXXXXXXwyh7GAuwdctDFiNdPW5Fc='
list addresses '10.14.0.2/8'
option mtu '1350'
option dns '1.0.0.1 1.1.1.1'
config wireguard_wg0
option public_key 'o07k/2dsaQkLLSR0dCI/FXXXXLik/F/HBBcOGUkNQGo='
option route_allowed_ips '1'
list allowed_ips '172.16.0.36/32'
option persistent_keepalive '25'
option description 'WG_1'
option endpoint_host 'wgs.prod.surfshark.com'
option endpoint_port '51820'
config wireguard_wg0
option public_key '+dmGrWPM9NI3vQkZ9E7hXXXXJKYzd3YMXGq10sjbN0A='
list allowed_ips '0.0.0.0/0'
option persistent_keepalive '25'
option description 'WG_2'
option route_allowed_ips '1'
option endpoint_host 'in-del.prod.surfshark.com'
option endpoint_port '51820'
It seems to be a DHCP issue from the logs, I have assigned static IP address from Openwrt interface but that didn't help, here are the recent system logs:
Mon Feb 20 09:26:29 2023 daemon.info hostapd: wlan1-2: STA 88:57:1d:11:f8:0f WPA: group key handshake completed (RSN)
Mon Feb 20 09:26:55 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:27:24 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:29:10 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:29:39 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:30:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:30:24 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:30:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:31:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:31:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:32:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:33:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:33:39 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:34:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 74:d6:37:a8:0b:2c WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 08:84:9d:0b:37:cc WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 00:03:7f:33:3b:5a WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:96:65:39 WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:96:4e:70 WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 34:3e:a4:02:aa:8c WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA b0:4a:39:2e:26:1b WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 28:6d:97:a4:8b:2d WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 54:e0:19:88:7e:c8 WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:c7:27:b4 WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:74:f6:cc WPA: group key handshake completed (RSN)
Mon Feb 20 09:34:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:35:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:36:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:36:24 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:36:29 2023 daemon.info hostapd: wlan1-2: STA 44:65:0d:51:40:af WPA: group key handshake completed (RSN)
Mon Feb 20 09:36:29 2023 daemon.info hostapd: wlan1-2: STA 88:57:1d:11:f8:0f WPA: group key handshake completed (RSN)
Mon Feb 20 09:37:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:37:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:38:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:38:39 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:39:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:39:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.3) 192.168.3.234 18:b4:30:c7:27:b4
Mon Feb 20 09:39:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.3) 192.168.3.234 18:b4:30:c7:27:b4 09AA01AC24170QKQ
Mon Feb 20 09:40:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:40:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:43:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 08:84:9d:0b:37:cc WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 00:03:7f:33:3b:5a WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 74:d6:37:a8:0b:2c WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:96:65:39 WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:96:4e:70 WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA b0:4a:39:2e:26:1b WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 28:6d:97:a4:8b:2d WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 34:3e:a4:02:aa:8c WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 54:e0:19:88:7e:c8 WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:74:f6:cc WPA: group key handshake completed (RSN)
Mon Feb 20 09:44:50 2023 daemon.info hostapd: wlan0-1: STA 18:b4:30:c7:27:b4 WPA: group key handshake completed (RSN)
Mon Feb 20 09:45:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:46:29 2023 daemon.info hostapd: wlan1-2: STA 88:57:1d:11:f8:0f WPA: group key handshake completed (RSN)
Mon Feb 20 09:46:30 2023 daemon.info hostapd: wlan1-2: STA 44:65:0d:51:40:af WPA: group key handshake completed (RSN)
Mon Feb 20 09:47:24 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:48:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:48:39 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:49:09 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:49:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:50:39 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:51:24 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:51:54 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:52:24 2023 user.info : luci: accepted login on / for root from 192.168.1.171
Mon Feb 20 09:52:39 2023 daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com
Mon Feb 20 09:52:45 2023 authpriv.info dropbear[29853]: Child connection from 192.168.1.171:64896
Is anyone facing a similar issue or can assist me to solve this issue ?
I had an echo which just moved to the wrong SSID itself , seems echos can store multiple wifi passwords even though the alexa app makea it look like one ssid can be actively used. It moved to the SSID/PSK it had before I moved it to the IOT wifi . And I verified double-ckecked that it got there really. Happened after IOT Ssid was short time unavailable.
That was the case earlier all three were going to old SSID. So I did a factory reset on all of them and added them back one by one (This was done a week ago) on IOT SSID. But they still keep losing network connection.
Amazon stores wifi passwords so if you’ve previously had them on a different SSID at one point, call Amazon Alexa support and have them wipe the wifi record clean (I had to do this before and you have to call them, it’s the only way).
Amazon devices are also very fickle with fast transition and boot from low ack, so if you are using FT, turn it off and also disable the disassociate from low ack option in the wireless settings.
Amazon doesn’t store them per device, they store them per account, so resetting the device doesn’t help. You have to call Amazon and have them remove the old wifi info from the entire account.
You might want to use a smaller bandwidth (say VHT40) and select a channel that is not in the DFS range.
other things... max_inactivity could be causing a problem, as could the encryption. Best to use WPA2 PSK, since that is the best supported for these types of devices.
Thanks @Catfriend1@psherman , I have updated the Wireless config today, will monitor it for next 24 hours.
Disabling Disassociate On Low Acknowledgement and updating the encryption to psk2 didn't resolve the issue. So I have updated the bandwidth and channel. Here is the updated Wireless config:
Thanks @anon4457646@mmstano, I do not see any disconnections on the Echo devices when using a single ESSID. I will add one VLAN and as opposed to two and see if the issue comes back.