NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

felipe_ceglia's avatar
Jul 07, 2014

RN102 v6.1.8 - cant access SSH

Hello folks,

I have a RN 102, now upgraded to 6.1.8.

I used to access it via SSH and rsync files from another RN102 to it. Suddenly I cannot access it via SSH anymore. Web interface is ok.

I tried booting, disabling and re-enabling sshd on web interface, no joy.

I investigated and the most relevant information I found on logfiles is:

Jul 06 21:32:44 NAS sshd[6277]: pam_unix(sshd:session): session opened for user ******** by (uid=0)
Jul 06 21:32:44 NAS sshd[6277]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jul 06 21:32:44 NAS sshd[6277]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jul 06 21:32:44 NAS sshd[6279]: Received disconnect from 192.168.2.20: 11: disconnected by user
Jul 06 21:32:44 NAS sshd[6277]: pam_unix(sshd:session): session closed for user ********

I tried axaplorer4 to access the filesystem, but no joy.

Any suggestion?

Thanks,

Felipe

13 Replies

Replies have been turned off for this discussion
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    You could edit the sqlite3 database /var/readynas/db.sq3 to make changes stick.
  • Good to know, but I won't need to do it.
    My config is a cp command away and contains only a few things like perf improvement and modified headers to secure a little bit more. Having a Cisco device with protocol inspection activated, IPS activated, then going to an UTM that provides a captive portal and then connects to my NAS, acting as a middle man, while using snort, and then having iptables on my NAS. I think I'm pretty safe without fake headers anyway ;)
    As I said, I tend to avoid problems, modifying apache is not hard and with a backup of the original config, any problem is solved within seconds and can't ever impact any other service. I don't want to mess up an SQLite database that I'm not sure about what it does in the NAS grand scheme of existence to save myself the trouble of a command once every 1-2 months...

    I could also make settings persistent with a cron job using cat & grep to see if I can find a personalized comment, if not copy the file.
    But as said before, I dislike to mess things up on a NAS, the only thing I did was to enhance security a little bit.
    But now with a serious firewall I feel way more comfortable knowing that only HTTPS connections can go through my firewall (HTTP on the same port won't pass, neither will SSH...) and that I have two IPS guarding angels. Not bullet proof but quite reasonable for non-enterprise data.
    That said, fail2ban & iptables should be integrated directly in the NAS interface (as an option) as they don't use too much ressources even for the 104, are free and provide decent protection (combined with mail alerts). I would have liked snort with limited rules to what's running but the 104 will take a performance hit with that.
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Other options for apache would be to make changes a bit like how add-ons do them. For that you could look at the SDK.

    You can use chattr to lock files so they can't be edited, but that probably wouldn't fit with your idea of not messing things up.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More