faq обучение настройка
Текущее время: Ср июн 25, 2025 01:21

Часовой пояс: UTC + 3 часа




Начать новую тему Ответить на тему  [ Сообщений: 1689 ]  На страницу Пред.  1 ... 10, 11, 12, 13, 14, 15, 16 ... 113  След.
Автор Сообщение
СообщениеДобавлено: Вс апр 28, 2013 02:27 
Не в сети

Зарегистрирован: Чт мар 28, 2013 22:00
Сообщений: 206
1.3.6 тоже кажется самая стабильная прошивка. На нее бы прикрутили smb и новые мопеды и хватит :)

_________________
Debugged program was unable to process exception.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вс апр 28, 2013 07:01 
Не в сети

Зарегистрирован: Сб окт 18, 2008 05:06
Сообщений: 129
что я не понял.как сделать такую схему (адсл модем дхцп роутер)->(дир620д1 вайфай).чтото не вкурил можно такое сделать?и в чём разница в дхцп между relay и выключено.relay будет брать с роутера дхцп и выключено тоже роутер дхцп раздаёт.поправте если не прав


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вс апр 28, 2013 11:48 
Не в сети

Зарегистрирован: Пн ноя 05, 2012 08:52
Сообщений: 273
Откуда: Нижний Новгород
Пробовал 1.3.10 с мин настройками.
Т.Е. подключение прова Билайн - L2TP и пароль на вафлю.
Ни каких вирт.серверов не забивал, ни каких ограничений и даже без АЙпиТВ.
Т.Е. стандартные настройки. Подключён только 1 комп по проводу.
Проработал 19:43 и завис сам по себе.(тупо при серфинге инита без каких либо закачек).
Сброс по питалову помог восстановить инит. Проработал почти 2-е суток опять завис.
Сброс в завод и новая настройка. проработал 12:32 и завис при подключении по вафле ноута НР (думал ноут может чего).
Сброс\настройка\ ноут Асус по вафле через 10 минут висяк.
Сброс\настройка\ провод комп + смарт + ноут Асус, висяк через 3 дня.
Откатил на 1.3.6 работает уже 2,5 недели без висяков. Вешал на него 2 компа по шнуру, 2 ноута по вафле, смарт, планшет - даже при одновременном их использовании пашет без проблем.
Похоже 1.3.6 самая стабильная прошивка.

_________________
Beeline (L2TP)
ZYXEL Keenetic - V1.00[BFW.4.4]D0
Dir 620 H/W D1 F/W Wive_WR-300NU-RT3352-2T2R-USB.5.2.6.RU.04082015
Все прошивки Dir 620 H/W D1 F/W https://yadi.sk/d/IacDuaOuixVoK


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вс апр 28, 2013 12:11 
Не в сети

Зарегистрирован: Чт мар 28, 2013 22:00
Сообщений: 206
Выходит проблема в L2TP подключении. Я не использую L2TP, прошивка 1.3.10, аптайм 4 недели, не зависает.
Так же ADSL модем-> через WAN ->раздает WiFi. Так же стабильно. Видимо не такая сильная нагрузка на WAN, а когда L2TP, т.е нагрузка сильная то роутер умирает.

gulin176 писал(а):
что я не понял.как сделать такую схему (адсл модем дхцп роутер)->(дир620д1 вайфай).чтото не вкурил можно такое сделать?и в чём разница в дхцп между relay и выключено.relay будет брать с роутера дхцп и выключено тоже роутер дхцп раздаёт.поправте если не прав

1. ADSL модем в порт WAN.
2. В настройках WAN добавить соединение с интерфейсом WAN и динамическим IP (если так раздает провайдер) если нет то IP статический там же.
3. Настройка Wi-FI как обычно
DHCP трогать не нужно, там адреса например 192.168.0.2-192.168.0.254 галку DNS Relay снять.

_________________
Debugged program was unable to process exception.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вс апр 28, 2013 18:16 
Не в сети

Зарегистрирован: Сб окт 18, 2008 05:06
Сообщений: 129
Инсульт вам лишь бы писать или как.я написал чётко дир620 находится после роутера.что и на роутере дхцп и на точке доступа дхцп будет.о каких ип провайдера речь ведёте.устройство получается чисто локальное оно за роутером!!!адсл в порт ван ну мне такие прописные истину не надо модемов и роутеров у меня было куча


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вс апр 28, 2013 19:26 
Не в сети

Зарегистрирован: Чт мар 28, 2013 22:00
Сообщений: 206
gulin176 писал(а):
..много букв...

Ничего не разобрать из написанного, буквы вроде знакомые, но..

з.ы. У меня ADSL->ZyXEL Keenetic->DIR620

_________________
Debugged program was unable to process exception.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн апр 29, 2013 08:51 
Не в сети

Зарегистрирован: Сб окт 18, 2008 05:06
Сообщений: 129
модераторы прошу помощи в моей проблеме описанной чуть выше


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн апр 29, 2013 09:42 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Ср окт 17, 2012 10:02
Сообщений: 2921
Откуда: D-Link, Ryazan
gulin176,
1 способ: Настроить соединение на DSL модеме (обычно PPPoE). Убедиться, что есть доступ в интернет на компьютере, подключенном к нему напрямую. На Wi-Fi роутере настроить беспроводную сеть и затем отключить DHCP-сервер в настройках LAN. Кабель от модема необходимо подключить к LAN порту роутера.

2 способ: Настроить модем в режиме Bridge со своими параметрами VPI, VCI. Подключить кабель от модема в WAN порт роутера, а LAN порт к компьютеру. На роутере настроить соединение (обычно PPPoE).

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


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн апр 29, 2013 10:41 
Не в сети

Зарегистрирован: Сб окт 18, 2008 05:06
Сообщений: 129
Alexey Vitko спасибо так всё и делал кроме того что кабель втыкал в wan а не в lan.настроил уже вторым способом переставлять пока не буду,хотя первый способ предпочтительнее.необходим торрент однако пишет вот такое
Попытка соединения не удалась
Firefox не может установить соединение с сервером 192.168.1.1:9091. в логе ничего подозрительного


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн апр 29, 2013 13:12 
Не в сети

Зарегистрирован: Ср апр 03, 2013 14:46
Сообщений: 8
keyhos писал(а):
к решению проблемы около месяца шел и к админам также обращался, помощи особой не дождался а решение проблем с зависами внимательно настраивай все функции маршрутизатора, админы не помогут т.к. прошива рабочая а глюки и прочее уже от вашего оборудования и они не могут проверять свои маршрутизаторы используя ваш набор, короче решение проблем это внимательное отношение к мелочам при настройке.


Мелочи? А на кой тогда продавать маршрутизатор если он виснет от устройств которыми пользуется покупатель. "Наборов" не так уж и много, чтобы сия немаленькая компания пренебрегала ими при проверке своего изделия. Опять пишите не по теме.

p.s. Маршрутизатор не вис 2 недели.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн апр 29, 2013 13:35 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Ср окт 17, 2012 10:02
Сообщений: 2921
Откуда: D-Link, Ryazan
gulin176 писал(а):
Alexey Vitko спасибо так всё и делал кроме того что кабель втыкал в wan а не в lan.настроил уже вторым способом переставлять пока не буду,хотя первый способ предпочтительнее.необходим торрент однако пишет вот такое
Попытка соединения не удалась
Firefox не может установить соединение с сервером 192.168.1.1:9091. в логе ничего подозрительного

Это при попытке входа на страницу Transmission? Если да, то вопрос: флешка определилась? Сам клиент включен?

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


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн апр 29, 2013 17:29 
Не в сети

Зарегистрирован: Сб окт 18, 2008 05:06
Сообщений: 129
диск видит это ВД 1тб с внешним питанием.файловый браузер на вебстранице морды видит файлы на диске.трансмиссин конечно включен


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн апр 29, 2013 19:16 
Не в сети

Зарегистрирован: Вт апр 09, 2013 21:30
Сообщений: 20
Dima_80 писал(а):
keyhos писал(а):
к решению проблемы около месяца шел и к админам также обращался, помощи особой не дождался а решение проблем с зависами внимательно настраивай все функции маршрутизатора, админы не помогут т.к. прошива рабочая а глюки и прочее уже от вашего оборудования и они не могут проверять свои маршрутизаторы используя ваш набор, короче решение проблем это внимательное отношение к мелочам при настройке.


Мелочи? А на кой тогда продавать маршрутизатор если он виснет от устройств которыми пользуется покупатель. "Наборов" не так уж и много, чтобы сия немаленькая компания пренебрегала ими при проверке своего изделия. Опять пишите не по теме.

p.s. Маршрутизатор не вис 2 недели.

вариантов настройки просто куча, около сотни могу лично показать, каждая настройка устройства будет отличатся от предыдущей, причем существенно. производитель не может учесть эту сотни конфигов сразу поэтому прошивка 311 по счету тось 311 исправлений уже внесены а в России всегда была проблема с прочтением инструкции, сперва настраиваем сами а потом если не пошло то инструкция или форум, причем уверен что к инструкции даже одним глазом не обращался, не к инструкции устройства а вообще основы сети и т.д


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вт апр 30, 2013 05:59 
Не в сети

Зарегистрирован: Сб окт 18, 2008 05:06
Сообщений: 129
поддержка посмотрите что не пашет трансмишн.очень надо.прошивка 1.3.11.лог прилагаю посмотрите может что интересное есть.в конце лога видно как выключал включал торрент однако ничего.в самбе какой логин пароль?
Скрытый текст: показать
5:30:21 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:31:06 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:31:30 kernel: [23882.422000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:31:35 kernel: [23887.411000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:31:44 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:31:45 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:31:47 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:31:51 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:32:34 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:33:08 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:33:36 kernel: [24008.897000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:33:37 kernel: [24009.885000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:33:50 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:33:58 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 05:33:58 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 05:34:30 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:35:11 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:35:39 kernel: [24131.872000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:35:41 kernel: [24133.360000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:35:43 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 05:35:45 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:35:48 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 05:36:21 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:36:56 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:37:36 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:37:48 kernel: [24260.348000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:37:49 kernel: [24261.835000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:38:09 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:38:46 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:39:28 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:39:51 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 05:39:51 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 05:39:52 kernel: [24384.821000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:39:53 kernel: [24385.809000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:40:08 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:40:40 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:41:21 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:41:55 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:41:56 kernel: [24508.296000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:41:58 kernel: [24510.284000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:42:37 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:43:15 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:43:48 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:43:58 kernel: [24630.771000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:43:58 kernel: [24630.772000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:44:00 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 05:44:00 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 05:44:02 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 05:44:03 kernel: [24635.746000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:44:11 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 05:44:22 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:44:57 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:45:28 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:46:04 kernel: [24756.733000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:46:05 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:46:05 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 05:46:05 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 05:46:10 kernel: [24762.221000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:46:47 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:47:27 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:48:03 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:48:09 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 05:48:10 kernel: [24882.208000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:48:15 kernel: [24887.196000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:48:36 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:49:08 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:49:45 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:50:16 kernel: [25008.683000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:50:18 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:50:21 kernel: [25013.670000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:50:25 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 05:50:48 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:51:19 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:51:53 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:52:18 kernel: [25130.658000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:52:19 kernel: [25131.146000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:52:22 kernel: [25134.132000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:52:22 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 05:52:22 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 05:52:23 kernel: [25135.120000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:52:30 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:53:14 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:53:57 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:54:03 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 05:54:03 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 05:54:27 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 05:54:30 kernel: [25262.607000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:54:32 kernel: [25264.095000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:54:37 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 05:54:40 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:55:22 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:56:04 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:56:29 kernel: [25381.083000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:56:29 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 05:56:29 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 05:56:32 kernel: [25384.569000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:56:36 kernel: [25388.057000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:56:39 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:57:19 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:57:53 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:58:32 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:58:34 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 05:58:38 kernel: [25510.044000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:58:39 kernel: [25511.532000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:58:40 kernel: [25512.520000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 05:58:44 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 05:59:07 miniupnpd[905]: Failed to get ip address for interface
Apr 30 05:59:41 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:00:19 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:00:20 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:00:22 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:00:26 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:00:34 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:00:38 kernel: [25630.506000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:00:39 kernel: [25630.994000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:00:39 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 06:00:39 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 06:00:47 kernel: [25639.481000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:00:50 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:01:34 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:02:12 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:02:44 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:02:52 kernel: [25764.468000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:03:16 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:03:55 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:04:05 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 06:04:05 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 06:04:33 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:04:48 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 06:04:49 kernel: [25881.456000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:04:53 kernel: [25884.943000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:04:54 kernel: [25885.931000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:04:57 kernel: [25889.419000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:05:10 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:05:51 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:06:28 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:06:55 kernel: [26006.906000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:07:01 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:07:01 kernel: [26012.894000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:07:36 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:08:13 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:08:48 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:08:59 kernel: [26130.881000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:09:01 kernel: [26133.369000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:09:02 kernel: [26134.357000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:09:03 kernel: [26135.345000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:09:32 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:10:17 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:11:00 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:11:08 kernel: [26259.832000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:11:14 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 06:11:44 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:12:26 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:13:06 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:13:10 kernel: [26382.319000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:13:10 kernel: [26382.320000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:13:12 kernel: [26384.294000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:13:14 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 06:13:14 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 06:13:37 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:14:07 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 06:14:07 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 06:14:18 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:14:59 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:15:00 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:01 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:15:14 kernel: [26505.781000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:15:18 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 06:15:19 kernel: [26511.270000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:15:20 kernel: [26511.757000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:15:21 kernel: [26512.745000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:15:29 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 06:15:33 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:16:16 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:16:56 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:16:57 syslog: IP header has unsupp len (52 bytes). Skip.
Apr 30 06:17:18 kernel: [26630.232000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:17:19 kernel: [26631.220000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:17:19 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 06:17:19 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 06:17:21 kernel: [26633.207000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:17:35 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:18:17 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:19:02 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:19:23 kernel: [26755.194000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:19:24 kernel: [26756.182000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:19:27 kernel: [26758.669000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:19:28 kernel: [26760.157000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:19:45 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:20:22 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:20:56 syslog: expected IP (24305 bytes) more then received 38. Skip.
Apr 30 06:20:56 syslog: expected IP (24305 bytes) more then received 26. Skip.
Apr 30 06:20:56 syslog: expected IP (24305 bytes) more then received 366. Skip.
Apr 30 06:20:56 syslog: expected IP (24305 bytes) more then received 78. Skip.
Apr 30 06:20:56 syslog: expected IP (24305 bytes) more then received 210. Skip.
Apr 30 06:20:56 syslog: expected IP (24305 bytes) more then received 39. Skip.
Apr 30 06:21:05 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:21:26 syslog: expected IP (24305 bytes) more then received 26. Skip.
Apr 30 06:21:30 kernel: [26881.644000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:21:30 kernel: [26881.645000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:21:31 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 06:21:35 kernel: [26886.620000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:21:38 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:21:39 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 06:21:45 syslog: expected IP (24305 bytes) more then received 26. Skip.
Apr 30 06:22:20 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:23:02 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:23:11 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 06:23:11 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 06:23:34 kernel: [27005.607000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:23:34 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 06:23:34 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 06:23:37 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:23:38 kernel: [27009.595000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:23:39 kernel: [27010.583000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:24:15 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:24:49 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:25:25 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:25:39 kernel: [27130.570000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:25:43 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 06:25:44 kernel: [27135.558000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:25:45 kernel: [27136.546000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:25:49 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 06:25:59 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:26:35 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:27:19 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:27:49 kernel: [27260.533000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:27:49 kernel: [27261.021000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:27:58 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:28:42 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:29:26 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:29:52 kernel: [27384.007000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:29:56 kernel: [27387.494000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:30:06 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:30:38 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:31:14 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:31:55 syslog: added membership for 239.255.255.250 on upstream #0 94.241.251.206
Apr 30 06:31:55 syslog: added new route 239.255.255.250: 94.241.251.206 -> 192.168.1.1
Apr 30 06:31:55 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:31:57 kernel: [27508.482000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:32:00 kernel: [27511.469000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:32:27 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:33:11 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:33:55 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:33:58 kernel: [27629.957000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:34:01 kernel: [27632.944000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:34:08 syslog: route 224.0.1.60: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 06:34:08 syslog: added membership for 224.0.1.60 on upstream #0 94.241.251.206
Apr 30 06:34:08 syslog: added new route 224.0.1.60: 94.241.251.206 -> 192.168.1.1
Apr 30 06:34:12 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 06:34:12 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 06:34:29 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:35:08 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:35:45 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:36:08 kernel: [27759.431000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:36:09 kernel: [27760.919000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:36:10 kernel: [27761.407000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:36:14 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.1.1
Apr 30 06:36:14 kernel: [27765.895000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:36:15 kernel: [27766.383000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:36:15 kernel: [27766.871000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:36:27 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:37:07 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:37:39 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:38:16 kernel: [27887.359000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:38:16 kernel: [27887.360000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:38:16 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:38:17 kernel: [27888.334000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:38:21 kernel: [27892.321000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:38:48 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:39:22 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:40:03 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:40:16 kernel: [28007.308000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:40:16 kernel: [28007.309000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:40:19 kernel: [28010.284000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:40:23 kernel: [28014.771000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:40:25 syslog: route 239.255.255.250: all (1 item(s)) down VIF(s) NOT reported. Delete expired route.
Apr 30 06:40:26 kernel: [28017.758000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:40:41 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:41:12 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:41:50 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:42:27 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:42:36 kernel: [28147.245000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:43:09 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:43:54 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:44:15 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 06:44:15 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
Apr 30 06:44:33 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:44:35 kernel: [28266.232000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:44:36 kernel: [28267.220000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:45:09 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:45:42 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:46:18 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:46:43 kernel: [28394.707000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:46:49 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:47:28 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:48:01 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:48:43 kernel: [28514.694000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:48:45 kernel: [28516.182000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:48:45 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:48:49 kernel: [28520.170000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:49:24 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:50:06 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:50:48 kernel: [28639.657000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:50:51 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:50:55 kernel: [28646.644000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:51:23 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:52:02 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:52:46 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:52:54 stop_transmission: kill transmission
Apr 30 06:52:54 start_transmission: check transmission dir
Apr 30 06:52:54 start_transmission: set params
Apr 30 06:53:00 kernel: [28771.131000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:53:00 kernel: [28771.619000] MulticastFilterTableInsertEntry: already in Members list.
Apr 30 06:53:22 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:54:03 miniupnpd[905]: Failed to get ip address for interface
Apr 30 06:54:17 dnsmasq-dhcp[1010]: DHCPINFORM(br0) 192.168.1.90 00:26:82:bb:52:ec
Apr 30 06:54:17 dnsmasq-dhcp[1010]: DHCPACK(br0) 192.168.1.90 00:26:82:bb:52:ec alex-PC
014.174000] MulticastFilterTableInsertEntry: already in Members list.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вт апр 30, 2013 12:41 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Ср окт 17, 2012 10:02
Сообщений: 2921
Откуда: D-Link, Ryazan
gulin176, пароль на самбу задается в разделе Система - Пользователи. Для трансмишна попробуйте другой браузер.

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


Вернуться наверх
 Профиль  
 
Показать сообщения за:  Сортировать по:  
Начать новую тему Ответить на тему  [ Сообщений: 1689 ]  На страницу Пред.  1 ... 10, 11, 12, 13, 14, 15, 16 ... 113  След.

Часовой пояс: UTC + 3 часа


Кто сейчас на форуме

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 420


Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете добавлять вложения

Найти:
Перейти:  
Создано на основе phpBB® Forum Software © phpBB Group
Русская поддержка phpBB