Hub One firmware push required

[#1]

Hi @bobpullen

Our Hub One is a bit out of date with the firmware, currently on .263, which can be remotely upgraded thankfully.
We have not used it for a few years so it may have fallen off the management platform (last few digits of serial number are 277).

Thanks in advance.

[#2]

Factory reset your hub by inserting something into the pinhole at the rear until the status light flashes green and then give it a few days.

Should be good after that (I've made some changes this side).

[#3]

Transfer complete, it says in the log. File name contains MR4.2 which I presume is the latest hub one firmware.
Now just wait for the hub to reboot and install it I guess.

[#4]

Hub rebooted last night (new firmware in place) but failed to connect using the WAN port. Tried a factory reset but still failing to connect with an external modem in use. Not sure what’s going wrong but it doesn’t look like it’s communicating via the WAN port (no ppp attempt in the logs).

Will try direct broadband line later tonight after everyone else has gone to bed, try and get it to kick back into working correctly.

[#5]

@RPMozley - did you manage to sort things out?

[#6]

I’m afraid not @bobpullen although the dsl connection works as normal, I cannot get the WAN auto-sensing to pick up the PPPoE connection from the external modem. It was previously working for the .263 firmware as that’s how it updated itself.

[#7]

Very odd

What modem are you using?

Throughout the whole (very laboured) development of this update, I was testing builds with an FTTP connection so fully dependent on the WAN port. Didn't experience any issues with the PPP link.

I also see a significant number of devices on the management platform configured in WAN mode and online/working.

Would be a mighty conincidence, but perhaps worth swapping the WAN ethernet cable out if you can. Also might be worth another factory reset.

[#8]

I’m using a TP-Link td-w9970 v3 in bridge mode.

I will try out a different ethernet cable in the off chance it’s somehow not working with this firmware version, seems very unlikely when working fine before.

Will post back after trying a few cables out.

[#9]

Nope 👎 still no link up using other cables. Even a few more factory resets failed to spark it into connecting.

Last thing to try, as it might mess with the DLM, a reboot of the TP-Link. Something to try later...

[#10]

Still no dice, hub is just not switching modes. Stuck on DSL only and won’t communicate with the TP-Link via WAN port.
Only difference appearing in the logs are some spoofing protection notices on eth1 but not entirely sure they are anything to do with this problem.

[#11]

And presumably there's no RJ-11 connector in the DSL port when trying the WAN connection?

Up to you where we go from here. We can: -

1. Hook up Hub One in DSL mode and I can push the older firmware image (will invoke a factory reset on reboot).
2. Ship a replacement Hub One.
3. Ship somethign else.

I'd quite like to try 1 first if you don't mind, as that's probably the most solid indicator of whether or not this is anything firmware related, or just an unfortunate coincidence.

[#12]

OK Bob should be able to do 1. I’ll put the hub one in DSL for the firmware push before bed, all ready for you tomorrow (or later today if you’re pedantic).

And yes nothing in the DSL port, although I did try putting something in at one time during my tests.

[#13]

Thanks. Give me a nudge when everything's in place.

[#14]

Hub is all ready, waiting for the firmware downgrade. I’m currently not at home but will be back in a few hours.

[#15]

All done. It will downgrade/factory reset when you next reboot.