Struggling to do an update

[seanige]

Had my R2 since July of last year but it ended up living in a cupboard because I had some frustrations with it early on. Figured I'd jump back in and have another go at getting it working as I want to try out Wireguard and Adblock and was hoping the new firmware would resolve various teething issues. Trying to update over the last few days has been an... interesting experience. Performed several factory resets both from interface and via the pin button at the back. Finally got it back up and running with basic connectivity and for the last few hours at least, it seems to be working pretty well. 

 

Upgrading however is a very different reality! Even after several resets via the pinhole at the back, I keep experiencing the same issue. I go to 'upgrade' and select the firmware the blue bar loads to 100%, I see the loading wheel and then the router reboots. I am seemingly stuck on R2 3.0.205 with no option to upgrade/downgrade (I've tried both.) Same cycle on repeat with various iterations (e.g. trying it via Ethernet and switching out different cables, WiFi on different bands, factory reset, rinse, repeat.)

 

It does seem to be working quite well with WiFi turned off, but I get a sense of deja vu in that it will often just randomly give up the ghost. I'd like to get the new firmware on here if possible. Can this be triggered remotely or via the USB port? I have enabled remote access on the device just in case this is possible. Presumably you can see my IP address from the post. The R2 is currently sat behind a router that I use for general purpose stuff but the R2 is in the DMZ so should play ball.

 

Logs attached for reference.

 

edit: Scratch that. It's back to a reboot cycle with no access to the interface. Internet light goes off for ~10 seconds closely followed by the two WiFi lights, rinse, repeat. Pin reset results in Internet access returning via ethernet but no access to interface with either static or dynamic IP set on my machine. I've even tried running nmap to scan the network for a different IP address but it's just not showing up. Traceroute is showing up my main router as being the next access point in the line 192.168.0.1, even with DNS and IP pointing to the R2. I can't see any hops via the cabled Duma to my main router which seems odd.

 

Any suggestions?

 

 

log-1639096854509.txt

[Netduma Fraser]

Hey, welcome to the forum!

Sorry to hear you're having this issue. I can't see anything too ominous in the logs that would cause that issue. We can force through an upgrade remotely but we do need to have the router be accessible so you will need to try and factory reset it until that happens. Unplug the router from power for 10 minutes, plug in, wait 2 minutes then hold the reset button for 30 seconds, release, wait 2 minutes then try accessing. 

[seanige]

Thanks Fraser!

It's not my first rodeo thankfully. I'm very well aware of how tech can be buggy for all manner of reasons! So we're back up and running. For how long is, as always, a mystery!

 

The router seems to come back up if I disconnect the Ethernet to the modem, let it do a few reboot cycles and then reconnect it once finished setting everything up. As it has stayed on a bit longer than usual this time I was able to capture a more comprehensive log file. I have enabled remote access to tech support in the WAN settings. Is there a particular date or time that you push these updates remotely? I can't guarantee that the router will stay up for any length of time so it's tricky. Every time I try to update locally it reverts back to the boot loop cycle.

log-1639170997936.txt

[Netduma Fraser]

Thanks for that, unfortunately as it is late evening on a Friday in the UK we'll need to get a colleague to remote in on Monday, hopefully it stays up for that long

[seanige]

Apologies for bringing up an old topic, but it seems to have come back to life! albeit in a convoluted setup! I picked up a new power supply, some new ethernet cables etc and thought I'd give it another go!

 

It's sat behind my R1 at the moment, but seems to be behaving itself. WiFi coverage has been good so far. Still the same issue when trying to update but after all the lights go off for ~5 seconds it comes back on with the existing firmware. Would be awesome if someone could work their magic server side and try to force an update.

[Netduma Liam]

9 hours ago, seanige said:

Apologies for bringing up an old topic, but it seems to have come back to life! albeit in a convoluted setup! I picked up a new power supply, some new ethernet cables etc and thought I'd give it another go!

 

It's sat behind my R1 at the moment, but seems to be behaving itself. WiFi coverage has been good so far. Still the same issue when trying to update but after all the lights go off for ~5 seconds it comes back on with the existing firmware. Would be awesome if someone could work their magic server side and try to force an update.

Do you still have remote access enabled? What's the R1 sat behind currently?

[seanige]

So it's Superhub > r1 > r2.

 

The r1 is setup as a DMZ, so effectively exposed to the Internet. The r2 has the remote support option enabled.

[Netduma Fraser]

So the R1 is in the hub DMZ, have you put the R2 in the R1 DMZ as well? You'll need both for us to access the R2

[seanige]

How do you put devices in a DMZ from the r1? I can see options for upnp, port forwarding etc but nothing relating to DMZ. Remote access is setup for both devices so in theory you could do this from the r1?

[Netduma Fraser]

2 minutes ago, seanige said:

How do you put devices in a DMZ from the r1? I can see options for upnp, port forwarding etc but nothing relating to DMZ. Remote access is setup for both devices so in theory you could do this from the r1?

What firmware version are you using on the R1? The R2 needs a direct line to the internet so the R1 could be the blocker.

[seanige]

1.03.6h.

The r2 does have Internet connectivity now so it should be accessible.

[Netduma Fraser]

You're on a very old version, is there a particular reason you haven't upgraded to DumaOS 3.0 on the R1?

On the R1 you haven't told it to pass traffic straight through to the R2 so it's unlikely we'll be able to access it. If you upgrade to 3.0 you can use the DMZ, otherwise for your version you would have to forward all ports to the R2 so 1-65535 TCP/UDP then that will act like a DMZ rule.