NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Failed logins to my QNAP NAS from my Netgear BE9200
With Armour enabled I am seeing numerous failed login attempts reported by all of my QNAP NAS devices The problem is bad enough that my QNAPs are blocking the source IP of my router, which is the...
The NAS just starts a listener because I enabled SSH access. I was going to change the port and decided to simply disable it until I need it.
I think Armor tries to login as part of the vulnerability scanning, QNAP decides it is being hacked and blocks the source IP
But Netgear should document that the scan will attempt SSH as user1, user2, and user3, or whatever
and if it is not doing that, they should admit that there must be a back door and I am being hacked!
The logging logic is horrific! It doesn't log the actual traffic it sees.
It logs port forwarding like it is direct. No public IP is going to connect to my internal private IPs
It should log the incoming traffic and the fact that it performed port forwarding
I think Armor tries to login as part of the vulnerability scanning, QNAP decides it is being hacked and blocks the source IP
Agreed.
Were you able to follow the instructions to remove the QNAP from the scan? It's clear it's already well protected.
But Netgear should document that the scan will attempt SSH as user1, user2, and user3, or whatever
FWIW I don't agree here. If they publish too many details then malware could pass the scan.
The logging logic is horrific!
I've been running Orbi for quite a while (been some years since I used Nighthawk).
Orbi logging could be better too. Better filtering would be nice, since mine have a lot of routine clutter. But I have no problem with the contents port forwarding info.
