- This topic has 2 replies, 2 voices, and was last updated 5 days, 3 hours ago by
.
-
Posts
-
I just spent 2 hours trying to update the firmware on my 3.4 AC from 2.2.1(3) to 2.2.1(4). After navigating to http://172.31.252.3/update, selecting the firmware file, entering my password, and hitting “Submit”, I see an “Uploading. Please wait…” message, and then absolutely nothing happens. No error message, no indication on the controller that it’s updating, no reboot, nothing.
Looking at the traffic with wireshark/tcpdump, I see a bunch of TCP retransmissions, and then the controller eventually sends an “[RST, ACK]” packet. (Tried to attach pcap file, but apparently I’m not allowed to do so.)
What the heck do I have to do to update this thing?
(Hardware is 3.4 AC.)
Welp. I finally got it to work.
My controller is on an isolated “IOT” VLAN, so my previous attempts all involved using SSH port forwarding to give the browser on my desktop HTTP access to the controller (or running various
curlincantations that Google Gemini suggested directly on the “router”). Those all died pretty much instantly.The solution (such as it is) was to spin up a VM with a direct connection to the IOT VLAN. This involved reconfiguring one of my network switches to make that VLAN available on my hypervisor and creating a new virtual network definition for that VLAN. (The VM also needs to be connected to a network with internet access.) Once I had done all of that, the upgrade process worked as documented.
I can’t help thinking that it shouldn’t be this hard.
Hmmm, it probably depends how you have your vlan access/isolation setup. I have my open sprinkler controller setup on a dedicated IoT VLAN as well. But I was able to update firmware from the browser on my computer that is connected directly to my primary VLAN. However, I have my network configuration setup with stateful ACL to allow connections initiated from my primary VLAN to my IoT VLAN (the reverse isn’t allowed).
This makes device administration on my IoT VLAN much easier in general…
- You must be logged in to reply to this topic.