{"id":481,"date":"2025-10-06T11:42:08","date_gmt":"2025-10-06T01:42:08","guid":{"rendered":"https:\/\/www.mrmarkyoung.com\/oracle\/?p=481"},"modified":"2026-03-07T14:43:46","modified_gmt":"2026-03-07T04:43:46","slug":"networking-and-amazon-echo-connection-issues","status":"publish","type":"post","link":"http:\/\/www.mrmarkyoung.com\/oracle\/2025\/10\/06\/networking-and-amazon-echo-connection-issues\/","title":{"rendered":"Networking and Amazon Echo Connection Issues on Asus Routers"},"content":{"rendered":"\n<p>Diagnosing Amazon Device Wi-Fi Failures on ASUS Router (Merlin Firmware)<\/p>\n\n\n\n<p>I ran into a persistent issue where my <strong>Amazon Echo Spot<\/strong> and <strong>Kindle<\/strong> refused to connect to my home Wi-Fi network, despite other devices working fine. The Echo would complete setup via my phone\u2019s hotspot, but fail when switching to my router. The Kindle showed an \u201cApplication Error\u201d even after entering the correct Wi-Fi credentials.<\/p>\n\n\n\n<p>Both devices had worked previously, and my network is powered by an <strong>ASUS RT-AX86U Pro running Merlin firmware<\/strong>, with multiple access points and a well-tuned 2.4 GHz band.<\/p>\n\n\n\n<p>Symptoms<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Echo Spot setup would hang on \u201cConnecting\u2026\u201d and eventually fail.<\/li>\n\n\n\n<li>Kindle would show \u201cApplication Error\u201d after attempting to join Wi-Fi.<\/li>\n\n\n\n<li>Both devices connected successfully to a phone hotspot.<\/li>\n\n\n\n<li>Router logs showed <strong>DHCPNAK errors<\/strong> for both devices:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code><strong>DHCPREQUEST 192.168.1.250\nDHCPNAK wrong server-ID<\/strong>\n<\/code><\/pre>\n\n\n\n<p>1. <strong>MAC Address Conflict<\/strong><\/p>\n\n\n\n<p>Initially suspected a duplicate MAC address (<code>0C:DC:91:5B:B8:28<\/code>) on the network. This can cause ARP table flapping and DHCP instability. However, after isolating devices, this was ruled out.<\/p>\n\n\n\n<p>2. <strong>Wireless Compatibility<\/strong><\/p>\n\n\n\n<p>Confirmed router was set to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Wireless Mode: Legacy<\/li>\n\n\n\n<li>Channel Bandwidth: 20 MHz<\/li>\n\n\n\n<li>Control Channel: 11<\/li>\n\n\n\n<li>WPA2-Personal with AES<\/li>\n\n\n\n<li>PMF: Disabled<\/li>\n<\/ul>\n\n\n\n<p>These are ideal settings for legacy Amazon devices.<\/p>\n\n\n\n<p>3. <strong>DHCP Behavior<\/strong><\/p>\n\n\n\n<p>Syslog revealed both devices were:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Successfully associating with Wi-Fi<\/li>\n\n\n\n<li>Completing WPA2 handshake<\/li>\n\n\n\n<li>Then requesting a <strong>stale IP address<\/strong> from a previous session<\/li>\n\n\n\n<li>Router correctly rejected the request with a DHCPNAK<\/li>\n<\/ul>\n\n\n\n<p>This confirmed the issue was <strong>device-side IP caching<\/strong>, not a router fault.<\/p>\n\n\n\n<p>For Echo Spot:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Factory reset<\/strong> the device (mute + volume down for 15 seconds)<\/li>\n\n\n\n<li>Completed setup via phone hotspot<\/li>\n\n\n\n<li>Switched to home Wi-Fi via Alexa app<\/li>\n\n\n\n<li>Assigned <strong>static IP via DHCP reservation<\/strong> on router<\/li>\n<\/ul>\n\n\n\n<p>For Kindle:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Forgot network<\/strong> and rejoined<\/li>\n\n\n\n<li>Assigned static IP via DHCP reservation<\/li>\n\n\n\n<li>Flushed DHCP leases on router<\/li>\n\n\n\n<li>Disabled VPN and IPv6 temporarily<\/li>\n\n\n\n<li>Set DNS to Google (8.8.8.8 \/ 8.8.4.4)<\/li>\n<\/ul>\n\n\n\n<p>After these steps, both devices connected reliably and retained their IPs across reboots.<\/p>\n\n\n\n<p><strong>Lessons Learned<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon devices may cache IPs aggressively and fail DHCP negotiation if the router doesn\u2019t honor stale requests.<\/li>\n\n\n\n<li>Merlin firmware logs are invaluable for tracing DHCP behavior.<\/li>\n\n\n\n<li>Factory resets aren\u2019t always necessary \u2014 DHCP reservations and lease flushes can resolve most issues.<\/li>\n\n\n\n<li>VPN routing and DNS can silently block device registration or service handshakes.<\/li>\n<\/ul>\n\n\n\n<p><strong>Final Recommendations<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>Legacy mode + 20 MHz bandwidth<\/strong> on 2.4 GHz for IoT compatibility<\/li>\n\n\n\n<li>Assign <strong>static IPs via DHCP reservation<\/strong> for sensitive devices<\/li>\n\n\n\n<li>Flush DHCP leases after major network changes<\/li>\n\n\n\n<li>Monitor logs for <code>DHCPNAK<\/code> and <code>disassociation<\/code> events<\/li>\n\n\n\n<li>Disable VPN and IPv6 during device setup<\/li>\n<\/ul>\n\n\n\n<p><strong>Resolution Steps<\/strong><\/p>\n\n\n\n<p>For Echo Spot:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Factory reset<\/strong> the device (mute + volume down for 15 seconds)<\/li>\n\n\n\n<li>Completed setup via phone hotspot<\/li>\n\n\n\n<li>Switched to home Wi-Fi via Alexa app<\/li>\n\n\n\n<li>Assigned <strong>static IP via DHCP reservation<\/strong> on router<\/li>\n<\/ul>\n\n\n\n<p>For Kindle:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Forgot network<\/strong> and rejoined<\/li>\n\n\n\n<li>Assigned static IP via DHCP reservation<\/li>\n\n\n\n<li>Flushed DHCP leases on router<\/li>\n\n\n\n<li>Disabled VPN and IPv6 temporarily<\/li>\n\n\n\n<li>Set DNS to Google (8.8.8.8 \/ 8.8.4.4)<\/li>\n<\/ul>\n\n\n\n<p><strong>Change the Wifi Settings on the router.<\/strong><\/p>\n\n\n\n<p>The Echo Spot doesn&#8217;t handle PMF negotiation on the router\u2019s modern firmware, and disabling PMF removed the security feature it didn\u2019t understand.<\/p>\n\n\n\n<p><strong>Disabling Protected Management Frames (PMF) on 2.4\u202fGHz<\/strong><\/p>\n\n\n\n<p>Everything else I tweaked helped, but <strong>PMF was the real blocker<\/strong>.<br><\/p>\n\n\n\n<p><strong>Why PMF breaks older Echo devices<\/strong><\/p>\n\n\n\n<p>The Echo Spot was released in <strong>2017<\/strong>, long before PMF became standard.<br>Its Wi\u2011Fi chipset:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>doesn\u2019t support PMF<\/li>\n\n\n\n<li>doesn\u2019t understand PMF negotiation<\/li>\n\n\n\n<li>misinterprets PMF\u2011capable beacons<\/li>\n\n\n\n<li>fails DHCP after association when PMF is present<\/li>\n\n\n\n<li>sometimes requests an IP from a \u201cghost\u201d DHCP server because the handshake timing gets thrown off<\/li>\n<\/ul>\n\n\n\n<p>When PMF is set to <strong>Capable<\/strong>, your router still advertises:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PMF support<\/li>\n\n\n\n<li>PMF negotiation options<\/li>\n\n\n\n<li>IGTK (integrity group key) capabilities<\/li>\n\n\n\n<li>stricter key\u2011exchange timing<\/li>\n<\/ul>\n\n\n\n<p>The Echo Spot sees this and basically goes:<\/p>\n\n\n\n<p>\u201cI don\u2019t know what this is, but I\u2019m going to panic and drop the connection.\u201dg to panic and drop the connection.\u201d<\/p>\n\n\n\n<p>After these steps, both devices connected reliably and retained their IPs across reboots.<\/p>\n\n\n\n<p>Lessons Learned<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon devices may cache IPs aggressively and fail DHCP negotiation if the router doesn\u2019t honor stale requests.<\/li>\n\n\n\n<li>Merlin firmware logs are invaluable for tracing DHCP behavior.<\/li>\n\n\n\n<li>Factory resets aren\u2019t always necessary \u2014 DHCP reservations and lease flushes can resolve most issues.<\/li>\n\n\n\n<li>VPN routing and DNS can silently block device registration or service handshakes.<\/li>\n<\/ul>\n\n\n\n<p>\ud83d\udee1\ufe0f Final Recommendations<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>Legacy mode + 20 MHz bandwidth<\/strong> on 2.4 GHz for IoT compatibility<\/li>\n\n\n\n<li>Disabling Protected Management Frames (PMF) on 2.4\u202fGHz<\/li>\n\n\n\n<li>Assign <strong>static IPs via DHCP reservation<\/strong> for sensitive devices<\/li>\n\n\n\n<li>Flush DHCP leases after major network changes<\/li>\n\n\n\n<li>Monitor logs for <code>DHCPNAK<\/code> and <code>disassociation<\/code> events<\/li>\n\n\n\n<li>Disable VPN and IPv6 during device setup<\/li>\n<\/ul>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Diagnosing Amazon Device Wi-Fi Failures on ASUS Router (Merlin Firmware) I ran into a persistent issue where my Amazon Echo Spot and Kindle refused to connect to my home Wi-Fi network, despite other devices working fine. The Echo would complete setup via my phone\u2019s hotspot, but fail when switching to my router. The Kindle showed &#8230; <a title=\"Networking and Amazon Echo Connection Issues on Asus Routers\" class=\"read-more\" href=\"http:\/\/www.mrmarkyoung.com\/oracle\/2025\/10\/06\/networking-and-amazon-echo-connection-issues\/\" aria-label=\"Read more about Networking and Amazon Echo Connection Issues on Asus Routers\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[51,76],"tags":[],"class_list":["post-481","post","type-post","status-publish","format-standard","hentry","category-alexa","category-networking"],"_links":{"self":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts\/481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/comments?post=481"}],"version-history":[{"count":5,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts\/481\/revisions"}],"predecessor-version":[{"id":492,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts\/481\/revisions\/492"}],"wp:attachment":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/media?parent=481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/categories?post=481"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/tags?post=481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}