Any further reports backs about stability on this update now you guys had it running for a period of time?
Slightly reluctant to upgrade with the issues we are having with premium disc's firmware, these BTWH01 discs running v1.02.12 build02 has been very stable for a long time.
Meanwhile I'm still unable to even upgrade, routing to upgrade server still broken.
I wonder how many other people this will be impacting?
As far as i believe you must be running v1.02.12 build02 not an earlier build.
If your using running a raspberry pi to run pi-hole or any other adblocker disable it.
Reboot disc's retry upgrade.
If still failing you could look at changing your DNS settings in router or if all else fails upgrade using a vpn.
As far as i believe you must be running v1.02.12 build02 not an earlier build. - Correct
If your using running a raspberry pi to run pi-hole or any other adblocker disable it. - Disabled
Reboot disc's retry upgrade. - Done
If still failing you could look at changing your DNS settings in router or if all else fails upgrade using a vpn. - DNS config'd as 18.104.22.168 - Could setup VPN but not sure I want to, would rather understand why I can't connect and get it fixed if possible.
Tracing route to dbtsu.bt.motive.com [22.214.171.124]
over a maximum of 30 hops:
0 ****INFO REMOVED****
1 ****INFO REMOVED****
5 10ge0-7.core3.lon1.he.net [126.96.36.199]
6 100ge0-75.core3.lon2.he.net [188.8.131.52]
7 100ge8-1.core1.lon2.he.net [184.108.40.206]
8 100ge0-79.core3.nyc4.he.net [220.127.116.11]
9 0.2-1-5.BR2.NYC4.ALTER.NET [18.104.22.168]
10 0.ae2.GW9.DFW7.ALTER.NET [22.214.171.124]
11 * * *
It seems online traceroute tools are able to complete the trace and I'm able to trace when using my mobile. So guessing the issue might be with my connection from public address 185.164.183.xxx
i had same issue and when i looked at the disc logs i could see it failing to resolve DNS so no firmware downloaded, it went through and completed the upgrade but never updated obviously, mine turned out to be my pi-hole blocking it, but if you have disabled your pi-hole and rebooted discs it should have worked.
Check the master disc log to see what is going on
Master disc log - 09.12.2021 16:05:44 HTTP-Can't connect to BT auto upgrade server.
No issue with DNS, tcpdump shows master disc trying to connect to 126.96.36.199 on tcp port 443
16:04:03.066921 IP 192.168.1.247.53028 > 188.8.131.52.https: Flags [S], seq 2659809379, win 14600, options [mss 1460,sackOK,TS val 256835724 ecr 0,nop,wscale 4], length 0
16:04:19.085744 IP 192.168.1.247.53028 > 184.108.40.206.https: Flags [S], seq 2659809379, win 14600, options [mss 1460,sackOK,TS val 256839728 ecr 0,nop,wscale 4], length 0
I've just taken the plunge and upgraded to this build,
i rebooted disc's first and checked for firmware and started download and it failed.
i disabled pi-hole from interface and rebooted disc's on second attempt with pi off for me it completed. i had this same issue with upgrading Premium disc's.
09.12.2021 17:38:26 [2 4 1] HTTP-Find new Firmware v1.02.13 build07 from BT auto upgrade server.
09.12.2021 17:38:50 [2 4 3] APP-FW upgraded by 127.0.0.1
09.12.2021 17:38:50 [2 2 1] HTTP-Firmware Upgrade Failed from IP 192.168.49.2.
09.12.2021 17:38:50 [2 2 2] OWL-Firmware upgrade failed for Fail to download firmware from remote server.
09.12.2021 17:38:52 [2 2 1] HTTP-Can't connect to BT auto upgrade server.
Then after disabling pi-hole
09.12.2021 17:42:48 [2 5 1] Firmware Upgrade - arc_owl_fwupgrade POST fwupload to OWL SUCCESS.
09.12.2021 17:42:48 [2 5 2] OWL-Firmware download from 192.168.49.27 done.
09.12.2021 17:42:54 [2 5 1] Firmware Upgrade - arc_owl_fwupgrade POST fwwrite to OWL SUCCESS.
09.12.2021 17:42:54 [2 5 2] OWL-Send ALL pkt(fwwrite):t(0)
09.12.2021 17:42:55 [2 5 2] Firmware upgrade - Receive fwwrite msg.
09.12.2021 17:43:58 [2 4 2] OWL-Firmware upgrade success from v1.02.12_build02 to v1.02.13_build07.
for me it was my pi-hole.
So firmware upgrade on the two hard wired disc but not on the WiFi connected one.
After firmware process had completed 1 hardwired disc reported as off line and although some devices connected lots were not working / able to find a WiFi connection.
After powering off discs and a network restart this led to a working state but now have two disc in 1.02.13 build 7
And 1 on 1.02.12 build 2
When asking for firmware update tells me they are all up to date.
Connect the wireless disc to ethernet and leave for 5 mins to force the update, once up to date and working move disc back to wireless backhaul.