NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Current RAX120 firmware version
The web site download page shows the current firmware version as 1.0.2.136. This morning I checked using the phone app, and it shows a version 1.2.0.16 available. Installed OK but want to verify th...
Similar issues as reported earlier in the thread here. While I hadn't narrowed it down to LAN devices, that would fit the behaviour I have experienced. My media server and other published web servicess were no longer accessible externally. I only performed minimal troubleshooting, but it's worth noting that SSHing to some of these devices to further assess the problem I was able to ping out. Now I should have followed up with traceroutes and other tests, but in the end downgraded quickly upon finding this thread.
A correctly completing ping would indicate the return path is fine so traceroute may be of limited use regardless. I had surmised it may be due to UPNP not mapping the ports correctly, but my media server was also unable to access online updates or other such features, so not only was inbound media services impacted, but outbound web traffic (port 80) as well. It was only noted to impact clients on the LAN, which would fall in line with others experiences.
I did not test factory resetting, while I appreciate this is a useful troubleshooting tactic, that's not a valid and permanent solution. Especially when it would be ridiculous to expect general consumers to do so for a minor version upgrade, all without a hint of warning this may be required in the first place.
The fact the firmware is still fully available with no notes or acknowledgment from Netgear is poor. This release states it addresses a number of security vulnerabilities (of which Netgear has seen ever increasing exposure to) and it is unfortuante that I am now running a firmware version that potentially exposes the security and privacy of my home network. Even ignoring the generally poor functionality and value adds Netgear provide in firmware releases, my very expensive RAX120 router should warrant some such continued support, my friends touting Ubiquiti as a far superior product are becoming increasingly harder to ignore. The hardware is decent, the support and firmware are becoming frustratingly bottom rung consumer.
I downloaded it from https://www.netgear.com/support/product/RAX120.aspx#download and installed manually and also reset my rax120 and I'm still getting the same issues of none of my LAN connections being able to access internet. Everything connected via wifi still works. I'm usually quite patient but this is getting ridiculous.
Newfiedrool sorry I know I came across slightly over the top and somewhat belligerent, I would honestly prefer to understand the issue, and for Netgear to resolve it at the package level rather than mandate resets (I do understand the usefulness of a hard reset nethertheless).
It seems others have reported the issue persists even after hard reset, which played a part in my avoidance of continuing troubleshooting, especially when it involves hard resets and reloading configs. While not horrible time consuming I spend my weekdays troubleshooting such problems, hardly something I wanted to spend a Sunday doing for my own home.
It would be nice to get some acknowldegement from someone Netgear side here, this doesn't seem to be a couple of isolated cases. I'm not certain, but did someone say they'd pulled it from the NA support area, it's definitely still available for AUS.
Not a problem, we would all like to have seen this update maybe handled a little different.
I can with my hand on heart say after a reset and watching and carefully monitoring the WiFi issues mentioned I have no issues and neither has my friend who I regularly talk too. Lan ports are fine too. It just needed something to warn users a reset was required. It seems the auto update introduced more issues than doing it manually.
I would dearly like to see a better QoS and I'm hoping we may yet see one and a few minor bug fixes which I need to have a peep at as one was missing log info after a week up. It's a great bit of kit, wonderful coverage, just needs those finishing touches.
soeun wrote:I downloaded it from https://www.netgear.com/support/product/RAX120.aspx#download and installed manually and also reset my rax120 and I'm still getting the same issues of none of my LAN connections being able to access internet. Everything connected via wifi still works. I'm usually quite patient but this is getting ridiculous.
Did you perform a software reset or the pinhole reset?
- Would like to reiterate for the thread that I also have had issues with the LAN ports after an upgrade and full reset. I’ve tried resets through the web interface as well as the pinhole. I’ve tried downgrading (which immediately restored functionality), erasing again, upgrading and re-erasing a third time via the web interface. I’ve tried not using a settings backup and creating a minimal config - but nothing works.
The LAN ports do still ping out and I can actually use curl to pull down non-SSL websites. The issue seems to be that any secure connection is blocked by some internal service or firewall on the router. Here’s an example:
~ ❯❯❯ curl -v https://google.com
* Trying 172.217.14.238:443...
* Connected to google.com (172.217.14.238) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /opt/chef-workstation/embedded/ssl/certs/cacert.pem
* CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to google.com:443
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to google.com:443
The expected “Server Hello” inbound traffic never makes it, unless the client is on WiFi and then there’s no issue.Could you try downloading the update via the support page and try install manually then performing a factory reset.
- I did the pinhole reset.
