NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Leroy1
Apr 10, 2014Aspirant
My idea's for Readynas OS 6.2
Hello, I don't know if I can post my ideas here but here is a list of ideas for the upcoming OS I don't use the SSH feauture to lose my warranty - Disk spin-down (already featured) - Firewal...
jhaye1
Apr 29, 2014Aspirant
Fail2ban would definitely be an eagerly desirable feature. For the moment I have a RN104 running as an RSYNC-over-SSH backup server, for a few RN102 clients. Problem is that you can't explicitly tell which SSH port you want to leverage when configuring an RSYNC-over-SSH backup job on the RN clients. Thus I'm forced to expose my backup server's port 22 (i.e. SSH). And guess what ? I have numerous daily SSH intrusion tentatives on my RN104 (as much as 5000 a day, sometimes). Fortunately I'm using 20 characters long password (generated with Keepass), making a brute force attack rather difficult. But still, I don't quite understand why there is no built-in defense mechanism (Fail2ban or alike) in ReadyNAS. This takes me to consider ReadyNAS as a great product, but not a professional one.
And at the first place, I don't get why we still can't specify a port when defining an RSYNC-over-SSH backup job, which sounds like a very trivial features in Linux world, to me. But this is another topic (see http://www.readynas.com/forum/viewtopic.php?f=31&t=73441)
Cheers
Jean-Marc
And at the first place, I don't get why we still can't specify a port when defining an RSYNC-over-SSH backup job, which sounds like a very trivial features in Linux world, to me. But this is another topic (see http://www.readynas.com/forum/viewtopic.php?f=31&t=73441)
Cheers
Jean-Marc
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!