Подключаю роутер DLink Dir 300 к сети билайн, все прекрасно работает, но после 10-15 мин, начинается разрыв, не WIFI не сам компьютер не открывает интернет, все настройки в норме и прошивка стоит билайн , звонил в службу поддержки билайн сказали проблемы с роутером, но дня 2 назад у меня был другой роутер не рекомендованный сетью билайн, все было тоже самое.
На прямую через компьютер интернет нормально работает.

Какая прошивка роутера?

_________________
Ответы на все вопросы здесь: http://www.dlink.ru/ru/contacts/

версия 1.0.1.0, которую рекомендует билайн и скачана с их сайта

Вы лучше покажите логи на момент разрыва.

_________________
Полезные настройки

извините конечно, за нубство, а где их можно просмотреть?

по менюшкам полазийте, там есть...

_________________
С уважением, Matrox.
DFL, HPE, QNAP, Netgear и прочее железо...

Посмотрите наклейку на роутере. Что написано после H/W?

_________________
Полезные настройки

C1

так в этом и весь прикол, что когда он вырубает интеренет, я не могу к нему в морду зайти((

если есть в нем SYSlog - вас это спасет , если нету - то даже и не знаю что делать .....

_________________
Своим вопросом Вы загоняете меня в ГУГЛ.....
DFL-210 -архив образов
Меня можно найти в боте Телеграмма @MyKingdombot когда РКН перестанет заниматься ерундой :-)
Готовыe платить - пишите
Прикуплю неисправные девайсы ради корпусов ....-> в личку

А на официальной не пробовали?

_________________
Полезные настройки

ща попробую самую свежую залить

чуть поработал и тоже самое, вот какие то логи нашёл.................Jan 1 00:00:39 syslog: active route 239.255.255.250 changed source from 10.59.1.58 to 10.59.6.61
Jan 1 00:00:39 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.6.61
Jan 1 00:00:39 syslog: active route 239.255.255.250 changed source from 10.59.6.61 to 10.59.7.103
Jan 1 00:00:39 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.7.103
Jan 1 00:00:39 syslog: active route 239.255.255.250 changed source from 10.59.7.103 to 10.59.2.29
Jan 1 00:00:39 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.2.29
Jan 1 00:00:39 syslog: active route 239.255.255.250 changed source from 10.59.2.29 to 10.59.1.204
Jan 1 00:00:39 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.1.204
Jan 1 00:00:39 syslog: active route 239.255.255.250 changed source from 10.59.1.204 to 10.59.7.100
Jan 1 00:00:39 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.7.100
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.7.100 to 10.59.7.70
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.7.70
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.7.70 to 10.59.6.92
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.6.92
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.6.92 to 10.59.5.202
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.5.202
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.5.202 to 10.59.3.118
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.3.118
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.3.118 to 10.59.0.204
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.0.204
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.0.204 to 10.59.6.251
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.6.251
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.6.251 to 10.59.7.53
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.7.53
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.7.53 to 10.59.4.235
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.4.235
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.4.235 to 10.59.5.76
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.5.76
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.5.76 to 10.59.0.137
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.0.137
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.0.137 to 10.59.2.34
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.2.34
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.2.34 to 10.59.3.23
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.3.23
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.3.23 to 10.59.4.112
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.4.112
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.4.112 to 10.59.2.127
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.2.127
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.2.127 to 10.59.4.216
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.4.216
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.4.216 to 10.59.6.151
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.6.151
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.6.151 to 10.59.7.187
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.7.187
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.7.187 to 10.59.0.49
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.0.49
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.0.49 to 10.59.2.133
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.2.133
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.2.133 to 10.59.4.138
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.4.138
Jan 1 00:00:40 syslog: active route 239.255.255.250 changed source from 10.59.4.138 to 10.59.2.245
Jan 1 00:00:40 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.2.245
Jan 1 00:00:40 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:40 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:41 syslog: active route 239.192.152.143 changed source from 192.168.1.52 to 10.59.2.163
Jan 1 00:00:41 syslog: route 239.192.152.143 on upstream #0 activated with 10.59.2.163
Jan 1 00:00:42 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:44 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:44 syslog: route 233.33.210.53 on upstream #0 activated with 10.219.148.106
Jan 1 00:00:47 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:48 syslog: active route 239.192.152.143 changed source from 10.59.2.163 to 192.168.1.64
Jan 1 00:00:48 syslog: route 239.192.152.143 on upstream #0 activated with 192.168.1.64
Jan 1 00:00:48 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:50 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:51 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:53 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:53 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:53 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:54 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:00:57 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:00 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:03 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:03 miniupnpd[201]: [truncated] m
Jan 1 00:01:04 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:06 syslog: IP header has unsupp len (0 bytes). Skip.
Jan 1 00:01:06 syslog: IP header has unsupp len (0 bytes). Skip.
Jan 1 00:01:07 syslog: active route 239.192.152.143 changed source from 192.168.1.64 to 10.59.6.227
Jan 1 00:01:07 syslog: route 239.192.152.143 on upstream #0 activated with 10.59.6.227
Jan 1 00:01:07 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:09 syslog: active route 239.255.255.250 changed source from 10.59.2.245 to 192.168.1.1
Jan 1 00:01:09 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Jan 1 00:01:10 syslog: active route 239.255.255.250 changed source from 192.168.1.1 to 10.59.7.205
Jan 1 00:01:10 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.7.205
Jan 1 00:01:10 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:11 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:11 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:11 syslog: active route 239.255.255.250 changed source from 10.59.7.205 to 10.59.7.75
Jan 1 00:01:11 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.7.75
Jan 1 00:01:11 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:13 syslog: IP header has unsupp len (44 bytes). Skip.
Jan 1 00:01:19 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:19 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:19 syslog: active route 239.255.255.250 changed source from 10.59.7.75 to 10.59.5.95
Jan 1 00:01:19 syslog: route 239.255.255.250 on upstream #0 activated with 10.59.5.95
Jan 1 00:01:22 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:22 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:24 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:24 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:24 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:25 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:25 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:27 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:27 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:27 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:28 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:28 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:30 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:30 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:30 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:31 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:31 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:32 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:32 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:32 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:33 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:33 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:34 miniupnpd[201]: Can't find in which sub network the client is
Jan 1 00:01:34 miniupnpd[201]: Can't find in which sub network the client is
utes for iface eth1
незнаю, то или не то

В этом логе нет упоминаний о разрывах. Он на какой прошивке снят?

_________________
Полезные настройки

эти логи ещё с билайн прошивки 1.0.1.0