Recent content by Regnar

Thank you all your replies. After shutting down WAN access to SHH the setup runs smoothly without problems. I'll keep your tips regarding remotely accessible SHH in mind if I should decide to open it again. Thanks guys! :)

Ahh, I see. I'll try having ufw deny incoming shh (port 22) connections if that's the best way only allowing local shh? Might as well just close the port forwarding on the router instead, eh? In my syslog I get a lot of the following: May 29 11:46:46 wserver rsyslogd-2007: action 'action 10'...

From my auth.log it seems someone (or rather something) is trying to login with random user/pw entries. Kind of disturbing but shouldn't really be the problem though? May 28 23:38:23 wserver sshd[7125]: Invalid user 1234 from 100.68.204.64 May 28 23:38:23 wserver sshd[7125]...

Yeah, that's what I'm thinking as well.. The RPI's local IP is set up in network/interfaces and as a DHCP reservation.

Alright, thank you. I'll get back with an update when I've checked out the logs.

Thanks for your answer. Just cleared the the router log, so I can have a look at it in ~10 hours. What logs would you recommend checking out on the RPI?

While setting up my raspberry pi with apache2, shh and more at a new address I've encountered a problem. My setup consists of a router (provided by my ISP, Sagemcom F@ST 3890) with port forwarding 80, 443 and 22 to my RPI's static local IP, ethernet connection. Everything runs smoothly for a...