angriff aus dem internet, wie richtig schützen?

[bersos]

guten tag, seit gestern versucht sich immer jemand auf meine ds einzuloggen, wie kann ich das unterbinden, zumal er es meinstens mit root probiert.

Stufe    Protokoll    Datum & Zeit    Benutzer    Ereignis
Warning    Verbindung    2013/03/26 12:08:24    SYSTEM    User [webadmin2] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:07:14    SYSTEM    User [ssh] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:07:06    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:06:58    SYSTEM    User [test] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:06:51    SYSTEM    User [crof] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:06:43    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:06:37    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:06:13    SYSTEM    User [acumen] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:05:25    SYSTEM    User [boa] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:05:19    SYSTEM    User [gamme] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:05:12    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:05:05    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:04:58    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:04:52    SYSTEM    User [syslog] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:04:13    SYSTEM    User [system] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:04:07    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:04:01    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:03:55    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:03:48    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:03:41    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:03:34    SYSTEM    User [nmrsu] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:03:28    SYSTEM    User [usario] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:03:21    SYSTEM    User [usario] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:02:07    SYSTEM    User [royalsoft] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:55    SYSTEM    User [po] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:49    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:42    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:36    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:28    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:22    SYSTEM    User [sniff] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:14    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:08    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 12:00:01    SYSTEM    User [ocadmin] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:59:54    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:59:47    SYSTEM    User [bin] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:48    SYSTEM    User [last] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:41    SYSTEM    User [temp] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:35    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:27    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:20    SYSTEM    User [golf] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:14    SYSTEM    User [user] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:07    SYSTEM    User [user] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:58:01    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:54    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:47    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:40    SYSTEM    User [denis] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:33    SYSTEM    User [denis] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:27    SYSTEM    User [virus] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:21    SYSTEM    User [marketing] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:15    SYSTEM    User [belinda] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:09    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:57:03    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:56:44    SYSTEM    User [jackwang] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:54:30    SYSTEM    User [system] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:54:23    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:54:18    SYSTEM    User [ssh] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:54:11    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:53:45    SYSTEM    User [system] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:53:38    SYSTEM    User [system] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:53:32    SYSTEM    User [system] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:53:26    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:53:20    SYSTEM    User [system] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.
Warning    Verbindung    2013/03/26 11:53:14    SYSTEM    User [root] from [220.161.148.178] failed to log in via [SSH] due to authorization failure.

 

[Perry2000]

Du könntest das unterbinden in dem Du ins Handbuch schaust, oder die Suche im Forum benutzt
http://www.synology-forum.de/showthread.html?39037-IP-Adressen-automatisch-sperren

 

[bersos]

hab mal gegoogelt,...soll wo aus china sein die ip...die ham doch langeweile, als ob man von nem privatanwender groß wichtige daten bekommen könnte...?! rofl

 

[jahlives]

...als ob man von nem privatanwender groß wichtige daten bekommen könnte...?! rofl

und woher soll der Chinese wissen dass du ein Privateanwender bist? Das sieht man einer IP im allgemeinen nicht wirklich an
Mehr als Autoblock und ein starkes Passwort kannst du eigentlich nicht machen. Aber das hilft sehr
Dann vielleicht noch ganz grundsätzlich überlegen welche Dienste du von extern erreichbar haben willst d.h. jede Portweiterleitung am Router an die DS sollte genau überlegt werden.
Viele User hier nutzen auch VPN um von aussen auf die DS zuzugreifen ohne viele Ports am Router öffnen zu müssen.