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.
Please do not assume you know the reason I turn my router off. Its done so all my logs start zeroed from boot which is how I have always done my updates and is a personal thing. Also it clears the cache and you will notice that RAM useage drops after a power down with the power supply removed for about 10 minutes. If this was such a myth why do Sony suggest to do this to clear the cache on Android TV's and the cache on PlayStations!
As far as a pin hole reset I take it you have not read R Merlins report on factory resetting? This person has his own Asus fork on smallnetbuilder and also patches for Asus themselves with many years of doing this behind him, so excuse me if I belive him over you. Here is a link that may be helpful about factory resets.
https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/
As far as the current firmware there has been a change in the QCA SDK I cannot talk anymore about this as I am under a NDA. I have factory reset my router, set it up from scratch and all ports work, I also powered it down as usual to clear the cache and reset all the logs (personal choice on powerdown) The issue with the ports is a known one and a reset or re-downloading the firmware then logging out after updating and resetting should sort the issue out. If it does not please contact Netgear support.
I assumed nothing about you, you've contribute minimally to the thread and certainly nothing since I started reading.
Powering off versus powering off 'for 15 minutes' are two entirely different things and I made no such claim on the former. Powering off and even soft resetting in most cases (where firmware is appropriately configured) will zero logs and perform other beneficial functions, believing powering off for 15 minutes does anything contrary to this is ridiculous and I beg you go claim such to anyone with an electrical engineering degree.
Clearing NVRAM isn't even being discussed and this can be mitigated from within firmware.
Come on guys, all the rest of us are doing is highlighting a problem with the firmware and even discussing where it may lie. If you don't want to join the discussion that's fine, otherwise your solutions are somewhat rudimentory and non viable to the rest of us.
Killhippie I believe is pretty clued up and I'm really sorry clearing the NVram is required and that's the same across many manufacturers. I know he beta tested this way back in July 2018 and he just explained it's a known issue and that's all he can say as can I due to Non Disclosure Aggreements.
clearing the cache is not mandatory but was mentioned in the thread which some do and some don't.
Have you read the post linked or are you saying Merlin has no idea I'm a bit confused.
If you have an issue maybe a mod may pick up on it and you maybe able to help if they deem it productive but your best action is to contact Netgear support as no one on here knows what internal changes to the SDK took place and if you have an issue only support can lead you to further help.
I would raise a ticket and link to this thread and see what happens but as end users we can't help solve it once you have reset the router and a problem persists.
We can both go to secure sights via lan connections so we are not suffering the issue you have and we have no way to know what steps you took which leads back to support who will insure you follow the steps to resolve your issue.This forum has a limit which is basic Netgear testing procedures. We are not here to change OpenGPL or OpenSSL or try and recompile the firmware let alone Netgears own proprietary packages. The issue is not present in my RAX120 or Newfies, this was cured by updating the firmware from Netgears support site and doing a factory reset which was sugested by Engeering as this appears to be a known issue due to QCA SDK changes that I am not privy to.
No one on here can solve your issue beyond the simple steps Netgear provide, you could of course try a TFTP install of the firmware which is as good as an end user can get. Anything beyond what has been discused here is for Netgear support.
If you have not factory reset then I suggest you download the firmware, pinhole reset for 20-30 seconds and set up as new. This is a known method to clear issues on many routers, see Merlins post in the link provided about NVRAM and here is a segmant from that link. Its a basic trouble shooting forum not an engineering forum and so I have given you the only options Netgear can offer as trouble shooting tools."Why do I sometime need to do a factory default reset?
In addition to those user-entered settings, there's all those system level settings I previously mentioned. Sometimes, the manufacturer will need to change some of those low-level settings, either to resolve an issue, or to adapt to a newer wireless driver that they started using.
If you fail to do a factory default reset, then your router will still have the old values, and it will keep using them. That can lead to performance issues (especially in changes related to the wireless driver), or flat out odd behaviour (if one of the settings no longer works the same way as before)."
Please read merlins link and I hope you mange to sort out your issues, but the forum is basic and as I said its for Netgear engeering to sort firmware issues out, not us as we can only report bugs. They may ask you to set up debug mode but thats up to whoever is in contact with you at Netgear.Killhippie so, because yours is correct all the issues are not true.
I hope Netgear will contact you for any problem they may have in future as you have the solution.
