RBRE950 Firmware Update problem

[FURRYe38]

So bridge mode didn't work either? 

[Psychopasta]

I didn't try it. I thought the DMZ test would do the same thing.

[FURRYe38]

Not necessarily. Seem some ISP modems not implement DMZ properly. 

[Psychopasta]

Hey guys,

My apologies for going dark on this, I got caught up on some other issues and let this slip.

So where I am now is that I'm running the Orbi in Access Point mode so it is no longer dishing out IP addresses via DHCP, and I have no 'double NAT' issues anymore. However, the Orbi still fails to check for updates, giving the same 'Service Unavailable' message.

Any thoughts as to what's next?

On additional question. Now the Cox box is doing DHCP, I'm on the 192.168.0.xxx subnet instead of the 10.0.0.x subnet that the Orbi chose. Everything is working fine, and I've checked that everything has a new 192.etc IP address. However, the Orbilogin.com website still shows a few devices as having 10. addresses when I know they don't. Is there anything I can do to flush the Orbi's cache of IP addresses?

- Mark 

[Psychopasta]

Hey @CrimpOn 

I tried the nslookup you suggested and got

C:\WINDOWS\system32>nslookup http.fw.updates1.netgear.com
Server: cdns1.cox.net
Address: 68.105.28.11

Non-authoritative answer:
Name: e70.g.akamaiedge.net
Address: 104.119.67.89
Aliases: http.fw.updates1.netgear.com
http.fw.updates1.netgear.com.edgekey.net

[FURRYe38]

Can you try a tracert on that same URL and post the results? 

[Psychopasta]

C:\WINDOWS\system32>tracert http.fw.updates1.netgear.com

Tracing route to e70.g.akamaiedge.net [104.119.67.89]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.0.1
2 11 ms 10 ms 10 ms 10.81.8.1
3 11 ms 12 ms 11 ms 100.120.109.84
4 12 ms 11 ms 14 ms 100.120.109.103
5 18 ms 18 ms 17 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 15 ms 21 ms 16 ms 68.105.30.159
7 31 ms 30 ms 23 ms ae22.r03.border101.lax01.fab.netarch.akamai.com [23.203.155.27]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 17 ms 18 ms 19 ms a104-119-67-89.deploy.static.akamaitechnologies.com [104.119.67.89]

Trace complete.

[CrimpOn]

---

@Psychopasta wrote:

However, the Orbilogin.com website still shows a few devices as having 10. addresses when I know they don't. Is there anything I can do to flush the Orbi's cache of IP addresses?

---

The devices with 10.* IP addresses:

• Should not have internet access, because they are looking for an internet gateway at 10.0.0.1
• Will seek to renew their DHCP lease every 12 hours.  If it has been longer than 12 hours and they still show the incorrect IP address, my guess is that the ISP DHCP process has the same basic flaw (i.e. bug, wrong, stupid) that Orbi DHCP has and is telling devices, "sure. fine. keep using what you've got."  In that case, a power cycle of the device should begin a brand new DHCP process resulting in the correct IP assignment.

p.s.  It has been a long day of absolute failure on a friend's computer/network, so I may be a bit incoherent.

[Psychopasta]

Thanks Crimpon! The devices have registered new 192**. its just that the Orbi router still shows their old addresses. Everything is working though and we all have bigger fish to fry...

[FURRYe38]

You might power OFF the Orbi system for 1 minute or longer then back ON. Should clear out any old addresses from the routers page.

[Psychopasta · Accepted solution]

Hi Furry,

I'll try that next time I can power cycle without the family moaning. It's purely a web server issue, all devices are actually on the new subnet so its not causing any operational problems.

I'm still curious why it won't find the firmware service but my guess is it'll be cured by the next formware update anyway. No need to stress out on this, I'll just keep my eyes open for firmware updates for the 950 series.

- Mark