Сервер атакует робот

[VitKost 0]

Какой-то урод на протяжении нескольких месяцев атакует сервер. Я так понимаю это робот.

автоматическую блокировку я включил (5 попыток 5 минут)

Прошу помочь советом

 

Выдержка из журнала:

Уровень Журнал Дата и время Пользователь Событие

Warning Подключение 2013/08/07 04:34:27 SYSTEM User [internet] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:22 SYSTEM User [mihai] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:17 SYSTEM User [nathan] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:13 SYSTEM User [david] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:08 SYSTEM User [daniel] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:02 SYSTEM User [hacker] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:58 SYSTEM User [kevin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:52 SYSTEM User [john] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:48 SYSTEM User [matilda] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:43 SYSTEM User [michael] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:38 SYSTEM User [george] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:33 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:28 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:23 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:18 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:13 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:09 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:04 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:59 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:54 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:49 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:44 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:39 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:34 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:30 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:25 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:20 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:15 SYSTEM User [wwwdata] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:10 SYSTEM User [stephanie] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:05 SYSTEM User [filip] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:00 SYSTEM User [danny] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:31:55 SYSTEM User [white] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:31:51 SYSTEM User [russ] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:31:46 SYSTEM User [kayla] from [202.77.120.67] failed to log in via [sSH] due to authorization failu

[dr_coyote 0]

Какой-то урод на протяжении днескольких месяцев атакует сервер. Я так понимаю это робот.

автоматическую блокировку я включил (5 попыток 5 минут)

Прошу помочь советом

 

Выдержка из журнала:

Уровень Журнал Дата и время Пользователь Событие

Warning Подключение 2013/08/07 04:34:27 SYSTEM User [internet] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:22 SYSTEM User [mihai] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:17 SYSTEM User [nathan] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:13 SYSTEM User [david] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:08 SYSTEM User [daniel] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:34:02 SYSTEM User [hacker] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:58 SYSTEM User [kevin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:52 SYSTEM User [john] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:48 SYSTEM User [matilda] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:43 SYSTEM User [michael] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:38 SYSTEM User [george] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:33 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:28 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:23 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:18 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:13 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:09 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:33:04 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:59 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:54 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:49 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:44 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:39 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:34 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:30 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:25 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:20 SYSTEM User [admin] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:15 SYSTEM User [wwwdata] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:10 SYSTEM User [stephanie] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:05 SYSTEM User [filip] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:32:00 SYSTEM User [danny] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:31:55 SYSTEM User [white] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:31:51 SYSTEM User [russ] from [202.77.120.67] failed to log in via [sSH] due to authorization failure.

Warning Подключение 2013/08/07 04:31:46 SYSTEM User [kayla] from [202.77.120.67] failed to log in via [sSH] due to authorization failu

 

У меня нас стоит за роутером, на котором 22 порт закрыт, и на роутере настроен триггер с порта 8022 на 22 порт наса.

[Accelerator 0]

Лучше действительно поменять порт. Тогда таких товарищей становиться в разы меньше.

Ну и можно по IP занести его в бан.

[SergeS 0]

Лучше действительно поменять порт. Тогда таких товарищей становиться в разы меньше.

Ну и можно по IP занести его в бан.

 

А почему блокировка по IP не срабатывает?

[Accelerator 0]

А почему блокировка по IP не срабатывает?

Скорее всего этот лог автор получил до того как включил блокировку по IP.

[hellstream 0]

У меня кстати тоже как включил почтовый сервер, постоянно кто то с разных айпишников туда лезет, это спамеры?

[VitKost 0]

А почему блокировка по IP не срабатывает?

Блокировка по Ip работает, но после блокировки какого-то IP атака продолжается с другого и так бесконечно. Уже больше трех месяцев...

[Madnicks 0]

А по другому и не будет. Закройте 22 порт на роутере. Нафига его вообще наружу выставлять без необходимости.

Либо сделайте проброс, как советовали выше.

на роутере настроен триггер с порта 8022 на 22 порт наса

[VitKost 0]

Блокировка по Ip работает, но после блокировки какого-то IP атака продолжается с другого и так бесконечно. Уже больше трех месяцев...

по блокировке выдержка:

Warning Система 2013/05/27 17:33:29 SYSTEM Host [1.25.202.50] was blocked via [sSH].

Warning Система 2013/06/04 00:56:46 SYSTEM Host [106.240.250.244] was blocked via [sSH].

Warning Система 2013/05/31 19:18:23 SYSTEM Host [106.240.250.246] was blocked via [sSH].

Warning Система 2013/06/27 21:29:52 SYSTEM Host [109.169.77.208] was blocked via [sSH].

Warning Система 2013/07/17 07:29:07 SYSTEM Host [112.124.3.53] was blocked via [sSH].

Warning Система 2013/07/29 09:20:45 SYSTEM Host [112.216.82.130] was blocked via [sSH].

Warning Система 2013/07/21 07:15:17 SYSTEM Host [112.65.244.94] was blocked via [sSH].

Warning Система 2013/06/10 15:19:22 SYSTEM Host [112.78.7.60] was blocked via [sSH].

Warning Система 2013/05/26 08:22:44 SYSTEM Host [112.90.90.20] was blocked via [sSH].

Warning Система 2013/07/11 23:02:53 SYSTEM Host [113.108.220.13] was blocked via [sSH].

Warning Система 2013/07/06 00:00:54 SYSTEM Host [113.142.37.114] was blocked via [sSH].

Warning Система 2013/06/24 10:00:57 SYSTEM Host [114.80.202.30] was blocked via [sSH].

Warning Система 2013/07/04 05:21:08 SYSTEM Host [114.80.224.90] was blocked via [sSH].

Warning Система 2013/07/06 23:24:37 SYSTEM Host [115.112.237.214] was blocked via [sSH].

Warning Система 2013/07/22 14:55:02 SYSTEM Host [117.141.96.7] was blocked via [sSH].

Warning Система 2013/06/07 02:50:58 SYSTEM Host [118.244.14.49] was blocked via [sSH].

Warning Система 2013/06/07 22:56:26 SYSTEM Host [121.199.29.116] was blocked via [sSH].

Warning Система 2013/06/09 20:44:01 SYSTEM Host [121.199.29.162] was blocked via [sSH].

Warning Система 2013/05/30 01:20:45 SYSTEM Host [122.72.120.105] was blocked via [sSH].

Warning Система 2013/06/06 05:23:53 SYSTEM Host [122.72.120.117] was blocked via [sSH].

Warning Система 2013/07/24 07:10:47 SYSTEM Host [123.157.254.30] was blocked via [sSH].

Warning Система 2013/06/04 06:09:51 SYSTEM Host [124.160.194.27] was blocked via [sSH].

Warning Система 2013/07/29 17:52:39 SYSTEM Host [124.160.194.82] was blocked via [sSH].

Warning Система 2013/06/25 04:24:05 SYSTEM Host [125.22.76.77] was blocked via [sSH].

Warning Система 2013/06/28 13:07:13 SYSTEM Host [125.45.229.163] was blocked via [sSH].

Warning Система 2013/06/29 00:53:16 SYSTEM Host [125.45.229.168] was blocked via [sSH].

Warning Система 2013/06/06 05:28:47 SYSTEM Host [125.46.13.163] was blocked via [sSH].

Warning Система 2013/07/28 22:13:14 SYSTEM Host [125.46.42.28] was blocked via [sSH].

Warning Система 2013/05/22 08:18:22 SYSTEM Host [141.255.160.247] was blocked via [sSH].

Warning Система 2013/06/25 03:06:24 SYSTEM Host [162.211.127.163] was blocked via [sSH].

Warning Система 2013/06/03 06:45:04 SYSTEM Host [164.164.82.107] was blocked via [sSH].

Warning Система 2013/06/24 11:39:44 SYSTEM Host [166.78.167.82] was blocked via [sSH].

Warning Система 2013/06/28 15:55:10 SYSTEM Host [173.45.66.18] was blocked via [sSH].

Warning Система 2013/06/08 04:52:25 SYSTEM Host [174.142.61.133] was blocked via [sSH].

Warning Система 2013/06/23 12:03:41 SYSTEM Host [175.236.216.38] was blocked via [sSH].

Warning Система 2013/06/26 18:28:54 SYSTEM Host [176.53.114.119] was blocked via [sSH].

Warning Система 2013/06/01 21:55:06 SYSTEM Host [178.20.227.191] was blocked via [sSH].

Warning Система 2013/05/25 10:27:56 SYSTEM Host [180.210.243.138] was blocked via [sSH].

Warning Система 2013/05/28 17:41:01 SYSTEM Host [182.140.240.27] was blocked via [sSH].

Warning Система 2013/06/02 23:25:17 SYSTEM Host [183.232.32.24] was blocked via [sSH].

Warning Система 2013/07/27 03:23:50 SYSTEM Host [183.245.142.44] was blocked via [sSH].

Warning Система 2013/07/27 05:40:26 SYSTEM Host [185.7.234.21] was blocked via [sSH].

Warning Система 2013/07/17 18:25:30 SYSTEM Host [188.127.225.85] was blocked via [sSH].

Warning Система 2013/07/22 15:22:52 SYSTEM Host [188.132.208.228] was blocked via [sSH].

Warning Система 2013/06/05 02:05:35 SYSTEM Host [188.190.98.6] was blocked via [sSH].

Warning Система 2013/05/28 14:52:53 SYSTEM Host [188.241.179.171] was blocked via [sSH].

Warning Система 2013/07/29 03:53:39 SYSTEM Host [189.11.70.211] was blocked via [sSH].

[Doctor Synology 0]

Настраивать блокировку IP-адреса. Причем не на сутки или неделю, а надолго.

Или менять порт со стандартного на нестандартный на самом накопителе и пробрасывать новый порт.

 

Видимо, Вы где-то засветили свой IP или DynDNS адрес, и он попал в базы, по которым идет перебор. Увы.

[svd819 0]

Настраивать блокировку IP-адреса. Причем не на сутки или неделю, а надолго.

Или менять порт со стандартного на нестандартный на самом накопителе и пробрасывать новый порт.

 

Видимо, Вы где-то засветили свой IP или DynDNS адрес, и он попал в базы, по которым идет перебор. Увы.

Сейчас столкнулся с той же проблемой.

Идёт постоянная атака на admin

Как избавиться?

Все варианты защиты стоят. Даже учётку admin отключил

Но робот бьется башкой в отключенную запись админ.

За ночь приходит порядка 50 писем о попытках входа.

Как все это побороть?

[svd819 0]

по блокировке выдержка:

Warning Система 2013/05/27 17:33:29 SYSTEM Host [1.25.202.50] was blocked via [sSH].

Warning Система 2013/06/04 00:56:46 SYSTEM Host [106.240.250.244] was blocked via [sSH].

Warning Система 2013/05/31 19:18:23 SYSTEM Host [106.240.250.246] was blocked via [sSH].

Warning Система 2013/06/27 21:29:52 SYSTEM Host [109.169.77.208] was blocked via [sSH].

Warning Система 2013/07/17 07:29:07 SYSTEM Host [112.124.3.53] was blocked via [sSH].

Warning Система 2013/07/29 09:20:45 SYSTEM Host [112.216.82.130] was blocked via [sSH].

Warning Система 2013/07/21 07:15:17 SYSTEM Host [112.65.244.94] was blocked via [sSH].

Warning Система 2013/06/10 15:19:22 SYSTEM Host [112.78.7.60] was blocked via [sSH].

Warning Система 2013/05/26 08:22:44 SYSTEM Host [112.90.90.20] was blocked via [sSH].

Warning Система 2013/07/11 23:02:53 SYSTEM Host [113.108.220.13] was blocked via [sSH].

Warning Система 2013/07/06 00:00:54 SYSTEM Host [113.142.37.114] was blocked via [sSH].

Warning Система 2013/06/24 10:00:57 SYSTEM Host [114.80.202.30] was blocked via [sSH].

Warning Система 2013/07/04 05:21:08 SYSTEM Host [114.80.224.90] was blocked via [sSH].

Warning Система 2013/07/06 23:24:37 SYSTEM Host [115.112.237.214] was blocked via [sSH].

Warning Система 2013/07/22 14:55:02 SYSTEM Host [117.141.96.7] was blocked via [sSH].

Warning Система 2013/06/07 02:50:58 SYSTEM Host [118.244.14.49] was blocked via [sSH].

Warning Система 2013/06/07 22:56:26 SYSTEM Host [121.199.29.116] was blocked via [sSH].

Warning Система 2013/06/09 20:44:01 SYSTEM Host [121.199.29.162] was blocked via [sSH].

Warning Система 2013/05/30 01:20:45 SYSTEM Host [122.72.120.105] was blocked via [sSH].

Warning Система 2013/06/06 05:23:53 SYSTEM Host [122.72.120.117] was blocked via [sSH].

Warning Система 2013/07/24 07:10:47 SYSTEM Host [123.157.254.30] was blocked via [sSH].

Warning Система 2013/06/04 06:09:51 SYSTEM Host [124.160.194.27] was blocked via [sSH].

Warning Система 2013/07/29 17:52:39 SYSTEM Host [124.160.194.82] was blocked via [sSH].

Warning Система 2013/06/25 04:24:05 SYSTEM Host [125.22.76.77] was blocked via [sSH].

Warning Система 2013/06/28 13:07:13 SYSTEM Host [125.45.229.163] was blocked via [sSH].

Warning Система 2013/06/29 00:53:16 SYSTEM Host [125.45.229.168] was blocked via [sSH].

Warning Система 2013/06/06 05:28:47 SYSTEM Host [125.46.13.163] was blocked via [sSH].

Warning Система 2013/07/28 22:13:14 SYSTEM Host [125.46.42.28] was blocked via [sSH].

Warning Система 2013/05/22 08:18:22 SYSTEM Host [141.255.160.247] was blocked via [sSH].

Warning Система 2013/06/25 03:06:24 SYSTEM Host [162.211.127.163] was blocked via [sSH].

Warning Система 2013/06/03 06:45:04 SYSTEM Host [164.164.82.107] was blocked via [sSH].

Warning Система 2013/06/24 11:39:44 SYSTEM Host [166.78.167.82] was blocked via [sSH].

Warning Система 2013/06/28 15:55:10 SYSTEM Host [173.45.66.18] was blocked via [sSH].

Warning Система 2013/06/08 04:52:25 SYSTEM Host [174.142.61.133] was blocked via [sSH].

Warning Система 2013/06/23 12:03:41 SYSTEM Host [175.236.216.38] was blocked via [sSH].

Warning Система 2013/06/26 18:28:54 SYSTEM Host [176.53.114.119] was blocked via [sSH].

Warning Система 2013/06/01 21:55:06 SYSTEM Host [178.20.227.191] was blocked via [sSH].

Warning Система 2013/05/25 10:27:56 SYSTEM Host [180.210.243.138] was blocked via [sSH].

Warning Система 2013/05/28 17:41:01 SYSTEM Host [182.140.240.27] was blocked via [sSH].

Warning Система 2013/06/02 23:25:17 SYSTEM Host [183.232.32.24] was blocked via [sSH].

Warning Система 2013/07/27 03:23:50 SYSTEM Host [183.245.142.44] was blocked via [sSH].

Warning Система 2013/07/27 05:40:26 SYSTEM Host [185.7.234.21] was blocked via [sSH].

Warning Система 2013/07/17 18:25:30 SYSTEM Host [188.127.225.85] was blocked via [sSH].

Warning Система 2013/07/22 15:22:52 SYSTEM Host [188.132.208.228] was blocked via [sSH].

Warning Система 2013/06/05 02:05:35 SYSTEM Host [188.190.98.6] was blocked via [sSH].

Warning Система 2013/05/28 14:52:53 SYSTEM Host [188.241.179.171] was blocked via [sSH].

Warning Система 2013/07/29 03:53:39 SYSTEM Host [189.11.70.211] was blocked via [sSH].

Как то победили?

[xibyt 0]

Как то победили?

Закрыть проброску стандартных портов извне.

Если доступ извне нужен, поменяйте порт на нестандартный.

Например пробросить порт 51001 на 22, 51002 на 5000 и так далее, в зависимости от фантазии

Берите любые порты из диапазона 49152—65535

[ishtvan 0]

Как то победили?

Пару дней подолбятся и устанут, не стоит беспокоится. Впрочем, в брандмауере запретил любые входящие из Китая, Гонконга и Сингапура - китаёзы ломятся в основном. И укров с вьетнамами запретил тоже, не помню уже почему - видимо тоже ломились. И двухэтапную аутентификацию включил.

[Diafilm 0]

То же самое, ломятся на 5000-й порт.

Переназначил его на роутере - проблема ушла.

Фаерволл всё дропает.

[svd819 0]

То же самое, ломятся на 5000-й порт.

Переназначил его на роутере - проблема ушла.

Фаерволл всё дропает.

На какой заменили?

[Diafilm 0]

На какой заменили?

На нестандартный. 30000+.

На приложениях телефона в поле адреса нужно дописывать номер порта, тогда будет логиниться.

По типу: *****.com:#####

Это в ds file / ds audio и т.д.

[svd819 0]

На нестандартный. 30000+.

На приложениях телефона в поле адреса нужно дописывать номер порта, тогда будет логиниться.

По типу: *****.com:#####

Это в ds file / ds audio и т.д.

Спасибо буду пробовать

[kucher 0]

Та же фигня. Причём началось это недавно. Заметил, когда NAS начал сообщать что бла-бла... "учётка "admin" защищена". Отключил учётку admin. Чуть позже сменю порты. Особо не расстроился, обычное дело. Главное - всё закрыть по возможности. По логам - у топикастера бот ломится не только по логину admin.

[svd819 0]

Та же фигня. Причём началось это недавно. Заметил, когда NAS начал сообщать что бла-бла... "учётка "admin" защищена". Отключил учётку admin. Чуть позже сменю порты. Особо не расстроился, обычное дело. Главное - всё закрыть по возможности. По логам - у топикастера бот ломится не только по логину admin.

Плиз кинь потом в личку, какие порты поменял и на что 🙏

[kucher 0]

Список используемых Synology портов можно посмотреть тут:

https://www.synology.com/ru-ru/knowledgebas...nology_services

 

Synology DSM и Synology Drive используют порты 5000, 5001 и 6690.

Порт 6690 используется для Winows-клиента Drive. Не нашёл где его указать (не принимает он синтаксис <IP:PORT>), потому оставил так.

 

Просто выбирайте те что не задействованы:

https://ru.wikipedia.org/wiki/%D0%A1%D0%BF%..._TCP_%D0%B8_UDP

 

P.S. Сменил порты. По логам можно сказать, что атаки сразу прекратились.

[Volk65 0]

У меня аналогично. Только сегодня заметил. Две попытки и смена адреса. В минуту от 7 до 15 попыток

[enzain 0]

Ну подбирают и подбирают, чем они вам мешают то?....

 

по ссш авторизацию по паролю отключите, оставте только по ключу, и флаг в руки, барабан на шею ...

[dmitrypro 0]

Граждане, а кто-нибудь знает почему Synology не даёт добавить в список блокируемых IP - диапазон. Только отдельные IP. При этом в список доверенных - пожалуйста. Может как-то можно это обойти или убедить Synology исправить в новых прошивках. Достали попытки SPAMеров по авторизации по SMTP.

[Siroc-co 0]

Граждане, а кто-нибудь знает почему Synology не даёт добавить в список блокируемых IP - диапазон. Только отдельные IP. При этом в список доверенных - пожалуйста. Может как-то можно это обойти или убедить Synology исправить в новых прошивках. Достали попытки SPAMеров по авторизации по SMTP.

Это можно сделать через "Брандмауэр". Выбирайте приложение\порт(или диапазон портов), выбирайте направление(входящие\исходящие), выбирайте IP(один, диапазон, или автоматически по регионам).

А список "разрешённых\блокированных" IP это только кусок функционала от полноценного браундмаэра, суть его в основном в том, что он показывает заблоченный айпишник, и если он случайно заблочен, его можно по быстрому найти и отменить блокировку.