Repository navigation
Replies: 11 comments 17 replies
|
hmm will review, might be some service remaining still certainly nothing we're recording/doing intentionally here |
|
Additionally, it might be good to be able to set the DNS server that the device uses (instead of letting the router handle it), to help catch any issues like this. For Pihole, Adguard, etc. users. Normally I'd just block internet access to these entirely, but they still rely on Github for updates, I believe. At least with the DNS server you can blackhole everything that isn't Github, or local LAN. |
|
@tonymaro I realized this earlier, but you might also want to mention which OS you're using. FireOS 5 (amonet v1.10 when you rooted it), or the newer FireOS 6 (amonet 2.0+ when you rooted it). It's possible that if you're using FireOS 6 that something got missed that wasn't present in FireOS 5, or vice versa. |
|
@electroflame Initially I flashed 6674.1 but it broke things - wouldn't finish providing root, so I reflashed as 6.5.7.4. Both acquired here: https://ftvdb.com/echo/firmware/com.amazon.biscuit.android.os/ |
|
Once you had it rooted with amonet (either 1.10 or 2+) you should've just had to use the echoctl (now echolocal) binary to handle the firmware flashing. If you re-installed Echo firmware after that (since the first failed) you might've re-enabled services EchoLocal disabled. (I believe you can re-run the echolocal installer again and see if it picks up any services that shouldn't be running. Last time I did it it maintained all of the device's data, so it should be safe.) The DNS traffic is helpful, too. (Which is why I still think it'd be helpful to be able to set the DNS these Echo devices use!) Can you elaborate about how you flashed your devices? Might be more info in there that's helpful. This might be a FireOS 6 issue with a dangling service that the echolocal installer missed. |
|
Step 9 in the rooting instructions on XDA states: "At this point, in order to have a bootable device, the best thing you can do is flash the latest FireOS version. Note that FireOS 5 versions won't boot starting with version 2.0 of amonet." The latest FireOS version broke things so I went back just a bit older. |
|
To be clear, I installed EchoLocal after flashing the FireOS recommended on XDA. |
|
Alright, got it. Unfortunately I'm out of ideas, so until we have deeper DNS routing options to more closely monitor individual devices (since mine are also on a separate VLAN) I'm out of ideas. @ygelfand Might have some more. At the very least, I still have some FireOS 5 devices (haven't upgraded to 6 yet) so we can compare if there were changes. I haven't noticed any cloudfront connections on my end, but with the VLAN separation it's difficult to capture since I only open it up for updates anyway. If we get DNS configuration for the devices I can set up a separate Pihole and stick it on the VLAN and point them to it, since its routing is physically separate here. |
|
I block them anyway so it's not a risk for me, but I wasn't sure you guys were aware, and clearly not, that it was going on. I'm like that - vlan, blocked internet, AND pihole. It ain't gettin' out here unless I say so. I'm more concerned over wasted cpu cycles on whatever it's trying to do tbh. |
|
Since the AWS traffic is plain HTTP, a short packet capture would show exactly what it is asking for. The Host header and the request path usually tell you whether it is an update check, a captive portal probe or something else. On the IoT VLAN, something like If the paths point to an update or OTA endpoint, that probably means a FireOS 6 service the installer did not disable. |

Uh oh!
There was an error while loading. Please reload this page.
I block traffic from my IoT vlan to the Internet and noticed the counter on the rule constantly ticking up.
This firmware is trying to communicate unencrypted with AWS on multiple IP's every couple of minutes.
All reactions