Amazon Fire HD 8 Tablets cannot see the Internet
This is an odd one. Since setting up my Firewalla Gold, most things have worked fine. A few have just needed a reboot. In the worst cases, a handful of the wireless devices (we use a Plume wireless mesh) benefited from a 'forget this network' and re-join dance in order to work properly.
But for reasons I can't explain, a couple of our Fire HD 8 tablets report that they are connected to WiFi, but that the Internet is not available. Of all of our Amazon devices, it seems to only be these tablets which are affected -- the Fire TVs work fine, as do the various Amazon Alexa and smart-home devices sprinkled around the house.
As far as I know, I haven't done anything to single these tablets out. They're in a device group with all the other Amazon devices. The only special configuration I have for them is DNS of HTTPS, but that was turned on *after* the connectivity issues started.
Unfortunately, I can't say whether the problem started after I put them in the "Amazon" group I made, or before. I did all that yesterday but I only looked at the tablets in earnest this morning.
I do see signs that at one point one of the tablets worked. The Firewalla recorded some traffic going to the device yesterday.
On a whim, I removed the Fire HD 8 tablets from their group so they're just connected directly to LAN1. Still no joy.
For what it's worth the Plume says that these tablets are connected (to the WiFi it manages) and doing fine. It's just Firewalla that seems to be reporting them as offline, and of course they are self reporting as connected to the network but disconnected from the Internet.
-
Thanks for the reply!
Topology is as you described:
.oO(Internet)0o. <--> [Cable Modem] <--> [Gold] <--> [Plume] <--> [Devices]
The Plume is in Auto (Bridge) mode.The Fire HD 8 Tablets are getting 192.168.196.* IP addresses, which is the same set the Firewalla* is handing out. Previously they were on 192.168.0.* addresses (from a TP-Link Load Balancing VPN router the Firewalla replaced).
[edit: I previously said the Plume was handing out IP addresses; I meant the Firewalla.]
-
Ok, for additional color, our Plume mesh started degrading today. First one node in the mesh went down and I asked Plume what to do about it. They said to plug it in directly to the main 'SuperPod' and let them talk for 15 minutes, then disconnect them.
Well, once I did that, the main node went offline, almost like it got infected by a virus from the faulty one. (zounds!)
Additionally, our WiFi printer stopped printing things. It would appear as 'offline' to windows, even though it would pass all of its own network self-checks, though the IPs it was getting were bizarre.So I thought as an experiment I'd set the network up the way it was before Firewalla entered the picture. I unplugged the Firewalla and put the TP-Link R600 back in place of it. I plugged the master Plume pod (and our other network devices) into the TP-Link. I power cycled all the mesh nodes. I waited about 10 minutes for the WiFi mesh to re-establish. I then power-cycled the printer and release/renewed all the DHCP leases on systems that hadn't figured out that it needed to.Now, without Firewalla Gold in the picture at all, the mesh as back up and stable. No down nodes, everything working as it should. Printer prints again.So, I don't know what I misconfigured or what Firewalla was doing, but it completely destroyed my Plume mesh's ability to do its work. Yikes.I'm hoping you guys can work with Plume (http://www.plume.com) to figure out what it takes to get Plume working with their hardware... I've already got a dialog going with them on this, but I am *not* a network engineer. Your expertise is appreciated.I'm willing to try additional troubleshooting steps here as well (of course), but it's costly and I can only do it at times when the entire household (which runs off our wireless mesh) can afford to be offline while I'm figuring things out.
Please sign in to leave a comment.
Comments
6 comments