faq обучение настройка
Текущее время: Ср дек 11, 2019 05:57

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




Начать новую тему Ответить на тему  [ Сообщений: 484 ]  На страницу Пред.  1 ... 9, 10, 11, 12, 13, 14, 15 ... 33  След.
Автор Сообщение
СообщениеДобавлено: Вт мар 10, 2015 10:11 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Пн ноя 10, 2014 11:44
Сообщений: 1048
Откуда: Ryazan
Доброго дня! В выходные пробовали воспроизвести проблему на 2.5.31. Трое суток роутер был нагружен торрентами в 1000 соединений и к нему было по беспроводной сети подключено два устройства. За все это время ни одно из устройств ни разу не отключилось.
Встает вопрос - что вы настраиваете на роутере, каким типом соединения пользуетесь, как сильно нагружаете роутер(хотя нагрузить сильнее роутер в домашних условиях врядли представляется возможным)?

_________________
-Полезные настройки
-FAQ по разделу
-FAQ по роутерам на сайте
Телефон технической поддержки: 8-800-700-5465
Наша почта: support@dlink.ru
Группа в Telegram: https://t.me/dlink_ru


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вс мар 15, 2015 15:36 
Не в сети

Зарегистрирован: Пт сен 23, 2005 00:52
Сообщений: 112
Откуда: Moscow
Поработал недельку на присланной по почте версии 20150303_1823_DIR_825_2.5.35 - все ОК, Transmission нормально подключается к трекерам, все классно. Но вылезла проблема с L2TP: роутер рвет соединения примерно каждые 5-6 минут. В логах это выглядит совершенно невинно и без видимых причин, т.е. работал работал, а потом вдруг, например:

Код:
Mar 15 11:20:55 l2tpd[8656]: call_close: Call 45887 to 192.168.0.200 disconnected
Mar 15 11:20:55 pppd[8662]: Modem hangup
Mar 15 11:20:55 pppd[8662]: Connect time 6.1 minutes.
Mar 15 11:20:55 pppd[8662]: Sent 4235529100 bytes, received 1203661 bytes.
Mar 15 11:20:55 pppd[8662]: Connection terminated.
Mar 15 11:20:55 l2tpd[8656]: call_close: Call 45887 to 192.168.0.200 disconnected
Mar 15 11:20:56 pppd[8662]: Connection terminated.
Mar 15 11:20:56 pppd[8662]: Hangup (SIGHUP)
Mar 15 11:20:56 pppd[8662]: Terminating on signal 15
Mar 15 11:20:56 pppd[8662]: Exit.


Изредка работает дольше - минут 10-20, один раз за неделю даже полтора часа работал и не рвал, но в основном - именно то время, которое в логе выше указано.
При этом, судя по всему, соединение разрывается по инициативе роутера совершенно неожиданно и принудительно: по провайдерским логам оно после этого разрыва еще 3 минуты висит, пока не сработает таймаут на неполучение ответа по lcp echo. Включение keep alive в настройках содинения ни на что не влияет.
Сейчас откатился на 2.5.33.
Если информации для диагностики проблемы недостаточно - готов что-нибудь отдебажить и проверить дополнительно, скажите только что и как.

ps: Заодно про другое спрошу. DLNA не может отсканировать целиком подключенный ЖД и отдает с него наружу буквально пару папок (остальные просто не видны в списки на клиентских устройствах). В логах следующее:
Код:
Jan  1 03:00:39 kernel: do_page_fault() #2: sending SIGSEGV to minidlnad for invalid read access from
Jan  1 03:00:39 kernel: 6774e4d8 (epc == 2abef934, ra == 2abef874)

Может это что-то типичное и понятно, на что он ругается? Типа диск плохой и т.п.? В каком направлении копать? Актуально и на 2.5.33 и на 2.5.35.

pps: Ну и совсем попутно еще мелкий вопросик - не планируется сделать функционал универсального VPN клиента? Сейчас, я так понимаю, VPN-туннель одновременно может быть только один. Было бы классно иметь возможность в разделе WAN создавать дополнительные туннели, ходящие по имеющемуся подключения к интернету. Чтобы на работу по pptp ходить спокойно. :-) Или, может, такое можно руками из консоли сделать? Тоже устроило бы...

Спасибо!


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

Зарегистрирован: Вс фев 01, 2015 01:40
Сообщений: 76
Цитата:
Встает вопрос - что вы настраиваете на роутере, каким типом соединения пользуетесь, как сильно нагружаете роутер(хотя нагрузить сильнее роутер в домашних условиях врядли представляется возможным)?

Вот так настроено всё:
Скрытый текст: показать
Изображение
Изображение
Изображение
Изображение
Изображение
Изображение
Изображение
Изображение
Изображение

Station Keep Alive – было 0, выставил 5 секунд, если я правильно понял смысл параметра. Лог попозже приложу, чтобы время прошло. Пока только 1 реальный отвал/1 отвал у андроида в журнале почти после самого перезапуска роутера. До этого активно терялся айфон судя по журналу, на деле вроде бы не отваливался.
UPnP IGD – отключено
Редирект – включено
DDNS – включено, обновляется
IGMP – отключено
SIP – отключено
RTSP – включено
Проброс PPPoE – отключено
Управление потоком – включено
5 ггц оставил включенным
Вокруг 30-35 точек 2.4 ггц постоянно.
Убрал UPnP IGD и после этого компы в эпохе империй начали видеть друг друга.
Ещё бывает так что по локалке с ноута на комп не сразу пускает – пишет, что недоступен.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн мар 16, 2015 16:38 
Не в сети

Зарегистрирован: Пт сен 23, 2005 00:52
Сообщений: 112
Откуда: Moscow
В продолжение верхнего предпоследнего поста - не все так просто. :-) 2.5.33 поработала сутки и тоже рвать l2tp начала. Буду экспериментировать с настройками. А может и провайдер виноват, потому что в дебаг логе:

Код:
Mar 16 14:40:17 l2tpd[7135]: checkServerActive:150 ##Server is not active!
Mar 16 14:40:17 l2tpd[7135]: call_close: Call 54299 to 192.168.0.200 disconnected
Mar 16 14:40:17 l2tpd[7135]: call_close: call disconnect.sh-3!!
Mar 16 14:40:17 l2tpd[7135]: lac_hangup : No such call 4377272 to hang up.
Mar 16 14:40:17 l2tpd[7135]: No such tunnel 4375256 to hang up.
Mar 16 14:40:17 pppd[7143]: calltimeout:do it
Mar 16 14:40:17 pppd[7143]: Modem hangup


Т.е. какой-то непонятный сервер неактивен.... Явно не VPN-сервер, потому что с тем все ОК - параллельно посылал на него пинг, идет без сбоев.
Буду еще дебажить, может пойму сам. :-) Но любой подсказе буду рад.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пн мар 16, 2015 23:24 
Не в сети

Зарегистрирован: Вс фев 01, 2015 01:40
Сообщений: 76
Вот лог за последние 20 часов. Там в конце отключил 5ггц.
Скрытый текст: показать
Jan 1 00:00:06 syslogd started: BusyBox v1.19.2
Jan 1 00:00:06 kernel: DWC_otg: Init: Port Power? op_state=1
Jan 1 00:00:06 kernel: DWC_otg: Init: Power Port (0)
Jan 1 00:00:06 kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
Jan 1 00:00:06 kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan 1 00:00:06 kernel: usb usb3: Product: DWC OTG Controller
Jan 1 00:00:06 kernel: usb usb3: Manufacturer: Linux 2.6.30.9 dwc_otg_hcd
Jan 1 00:00:06 kernel: usb usb3: SerialNumber: logicmodule
Jan 1 00:00:06 kernel: usb usb3: configuration #1 chosen from 1 choice
Jan 1 00:00:06 kernel: hub 3-0:1.0: USB hub found
Jan 1 00:00:06 kernel: hub 3-0:1.0: 1 port detected
Jan 1 00:00:06 kernel: ----enable irq-----
Jan 1 00:00:06 kernel: [S1] dwc_otg_driver, lmdriver=803b3f40
Jan 1 00:00:06 kernel: Netfilter messages via NETLINK v0.30.
Jan 1 00:00:06 kernel: nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
Jan 1 00:00:06 kernel: ctnetlink v0.93: registering with nfnetlink.
Jan 1 00:00:06 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:06 kernel: arp_tables: (C) 2002 David S. Miller
Jan 1 00:00:06 kernel: TCP cubic registered
Jan 1 00:00:06 kernel: NET: Registered protocol family 17
Jan 1 00:00:06 kernel: Bridge firewalling registered
Jan 1 00:00:06 kernel: Ebtables v2.0 registered
Jan 1 00:00:06 kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Jan 1 00:00:06 kernel: All bugs added by David S. Miller <davem@redhat.com>
Jan 1 00:00:06 kernel: Netlink[Kernel] create socket for igmp ok.
Jan 1 00:00:06 kernel: Realtek FastPath:v1.03
Jan 1 00:00:06 kernel: nlmon: nlmon_init entry
Jan 1 00:00:06 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Jan 1 00:00:06 kernel: Freeing unused kernel memory: 112k freed
Jan 1 00:00:06 kernel: gpiom: module license 'Proprietary' taints kernel.
Jan 1 00:00:06 kernel: Disabling lock debugging due to kernel taint
Jan 1 00:00:06 kernel: gpiom: module starting ...
Jan 1 00:00:06 kernel: gpiom: using profile DIR_825.
Jan 1 00:00:06 kernel: gpiom: button support enabled.
Jan 1 00:00:06 kernel: gpiom: led support enabled.
Jan 1 00:00:06 kernel: IRQ 32/gpiom: IRQF_DISABLED is not guaranteed on shared IRQs
Jan 1 00:00:06 kernel: NET: Registered protocol family 10
Jan 1 00:00:06 kernel: lo: Disabled Privacy Extensions
Jan 1 00:00:06 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:06 kernel: sit: Unknown symbol xfrm4_tunnel_register
Jan 1 00:00:06 kernel: sit: Unknown symbol xfrm4_tunnel_deregister
Jan 1 00:00:06 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 00:00:06 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 00:00:06 kernel: fuse init (API version 7.11)
Jan 1 00:00:06 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Jan 1 00:00:06 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Jan 1 00:00:06 kernel: [PHY_ConfigMACWithParaFile][MACPHY_REG]
Jan 1 00:00:06 kernel: **********************************
Jan 1 00:00:06 kernel: ** NOTE!! RTL8192D INTERNAL PA! **
Jan 1 00:00:06 kernel: **********************************
Jan 1 00:00:06 kernel: [phy_RF6052_Config_ParaFile][radio_a_intPA]
Jan 1 00:00:06 kernel: Wan link is up!
Jan 1 00:00:06 kernel: message received before monitor task is initialized kerSysSendtoNlMonTask
Jan 1 00:00:06 kernel: [phy_RF6052_Config_ParaFile][radio_b_intPA]
Jan 1 00:00:06 kernel: ===> Load_92D_Firmware
Jan 1 00:00:06 kernel: Firmware check 8005(0)
Jan 1 00:00:06 kernel: [Load_92D_Firmware][rtl8192dfw_n]
Jan 1 00:00:06 kernel: <=== Load_92D_Firmware
Jan 1 00:00:06 kernel: >> IQK_92D_5G_n
Jan 1 00:00:06 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Jan 1 00:00:06 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Jan 1 00:00:06 kernel: [PHY_ConfigMACWithParaFile][MACPHY_REG_92C]
Jan 1 00:00:06 kernel: ===> Load_92C_Firmware
Jan 1 00:00:06 kernel: <=== Load_92C_Firmware
Jan 1 00:00:06 kernel: monitor task is initialized pid= 955
Jan 1 00:00:07 kernel: Wan link is down
Jan 1 00:00:08 kernel: ===== dlink minChan=36=====
Jan 1 00:00:08 kernel: Wan link is up!
Jan 1 00:00:08 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Jan 1 00:00:08 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Jan 1 00:00:08 kernel: wlan1: WPA2-AES PSK authentication in progress...
Jan 1 00:00:08 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Jan 1 00:00:08 kernel: wlan1: Open and authenticated
Jan 1 00:00:08 kernel: device eth0.2 entered promiscuous mode
Jan 1 00:00:08 kernel: device eth0 entered promiscuous mode
Jan 1 00:00:08 dnsmasq[1070]: warning: interface br0 does not currently exist
Jan 1 00:00:08 kernel: device wlan1 entered promiscuous mode
Jan 1 00:00:08 kernel: device wlan0 entered promiscuous mode
Jan 1 00:00:08 kernel: rtk_update_netif_vlan 15513 dp->portnum=5 vid=2
Jan 1 00:00:08 kernel: rtk_update_netif_vlan 15513 dp->portnum=1 vid=1
Jan 1 00:00:08 kernel: br0: port 3(wlan0) entering learning state
Jan 1 00:00:08 kernel: br0: port 2(wlan1) entering learning state
Jan 1 00:00:08 kernel: br0: port 1(eth0.2) entering learning state
Jan 1 00:00:09 kernel: Wan link is down
Jan 1 00:00:11 kernel: Wan link is up!
Jan 1 00:00:13 udhcpc[1136]: UDHCP start..
Jan 1 00:00:13 udhcpc[1136]: udhcp client (v0.9.8) started (iface: eth1, connect: 5)
Jan 1 00:00:13 dms_reset_uptime[1131]: enter key eth1_5
Jan 1 00:00:13 dms_reset_uptime[1131]: unable to remove file /tmp/stat.eth1_5
Jan 1 00:00:13 udhcpc[1136]: Sending discover...
Jan 1 00:00:13 udhcpc[1136]: Lease of 10.220.160.225 obtained, lease time 3600
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:13 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:14 INADYN[1183]: INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
Jan 1 03:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:14 l2tpd[1256]: This binary does not support kernel L2TP.
Jan 1 03:00:14 l2tpd[1257]: daemonize(1091)
Jan 1 03:00:14 l2tpd[1257]: l2tpd version 0.69 started on Dlink-Router PID:1257
Jan 1 03:00:14 l2tpd[1257]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
Jan 1 03:00:14 l2tpd[1257]: Forked by Scott Balmos and David Stipp, (C) 2001
Jan 1 03:00:14 l2tpd[1257]: Inherited by Jeff McAdams, (C) 2002
Jan 1 03:00:14 l2tpd[1257]: Listening on IP address 0.0.0.0, port 1701
Jan 1 03:00:16 l2tpd[1257]: Connecting to host tp.internet.beeline.ru, port 1701
Jan 1 03:00:17 l2tpd[1257]: handle_avps: dont know how to handle atribute 46.
Jan 1 03:00:17 l2tpd[1257]: Connection established to 85.21.0.162, 1701. Local: 47738, Remote: 1220.
Jan 1 03:00:17 l2tpd[1257]: Calling on tunnel 47738
Jan 1 03:00:17 l2tpd[1257]: Call established with 85.21.0.162, Local: 37475, Remote: 17208, Serial: 1
Jan 1 03:00:17 l2tpd[1257]: control_finish(999):To generate CDN to store. +++++
Jan 1 03:00:17 l2tpd[1257]: control_finish(1005):c->ourcid(37475),c->cid(17208),c->qcid(-1),c->serno(1). +++++
Jan 1 03:00:17 pppd[1263]: entering dlock, dfd = -1
Jan 1 03:00:17 pppd[1263]: dlock: locked
Jan 1 03:00:17 pppd[1263]: pppd 2.4.4 started by admin, uid 0
Jan 1 03:00:17 pppd[1263]: Using interface ppp0
Jan 1 03:00:17 pppd[1263]: Connect: ppp0 <--> /dev/ttyp0
Jan 1 03:00:18 kernel: br0: port 3(wlan0) entering forwarding state
Jan 1 03:00:18 kernel: br0: port 2(wlan1) entering forwarding state
Jan 1 03:00:18 kernel: br0: port 1(eth0.2) entering forwarding state
Jan 1 03:00:20 pppd[1263]: CHAP authentication succeeded: CHAP authentication success, unit 2131
Jan 1 03:00:20 pppd[1263]: CHAP authentication succeeded
Jan 1 03:00:20 pppd[1263]: local IP address 93.81.74.42
Jan 1 03:00:20 pppd[1263]: remote IP address 93.81.64.1
Jan 1 03:00:20 pppd[1263]: primary DNS address 85.21.192.5
Jan 1 03:00:20 pppd[1263]: secondary DNS address 213.234.192.7
Jan 1 03:00:24 dnsmasq[1120]: script process exited with status 1
Jan 1 03:00:29 wget_to_file[1131]: unable to connect: Operation now in progress (150)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:30 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:31 INADYN[1312]: INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
Jan 1 03:00:32 INADYN[1312]: I:INADYN: IP address for alias '.dlinkddns.com' needs update to '93.81.74.42'
Jan 1 03:00:32 INADYN[1312]: I:INADYN: Alias '.dlinkddns.com' to IP '93.81.74.42' updated successful.
Mar 16 01:27:34 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 01:27:34 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 01:27:34 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 01:27:34 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 01:27:36 kernel: wlan1: Open and authenticated
Mar 16 01:27:38 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 01:27:38 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 01:27:38 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 01:27:38 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 01:27:38 kernel: wlan1: Open and authenticated
Mar 16 01:27:39 dnsmasq[1300]: script process exited with status 1
Mar 16 01:27:39 dnsmasq[1300]: script process exited with status 1
Mar 16 01:27:41 pppd[1263]: System time change detected.
Mar 16 01:29:24 morda[1401]: user admin is logged in with administrator privileges to the ip ::ffff:192.168.0.43
Mar 16 01:36:29 kernel: wlan1: A wireless client is disassociated - 9C:B7:0D:A1:68:15
Mar 16 01:43:32 kernel: wlan1: A wireless client is deauthenticated - 84:00:D2:C8:E3:FE
Mar 16 01:53:42 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 01:53:42 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 01:53:42 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 01:53:42 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 01:53:42 kernel: wlan1: Open and authenticated
Mar 16 01:57:03 udhcpc[1159]: Entering renew state
Mar 16 01:57:03 udhcpc[1159]: Sending renew...
Mar 16 01:57:03 udhcpc[1159]: Lease of 10.220.160.225 obtained, lease time 604800
Mar 16 02:18:23 morda[1626]: user admin is logged in with administrator privileges to the ip ::ffff:192.168.0.43
Mar 16 04:50:25 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 04:50:25 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 04:50:25 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 04:50:25 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 04:50:25 kernel: wlan1: Open and authenticated
Mar 16 05:27:18 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 05:27:59 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 05:27:59 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 05:27:59 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 05:27:59 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 05:27:59 kernel: wlan1: Open and authenticated
Mar 16 06:07:19 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 06:07:19 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 55)
Mar 16 06:23:14 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 06:23:14 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 57)
Mar 16 06:27:24 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 06:27:45 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 06:27:45 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 06:27:45 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 06:27:45 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 06:27:45 kernel: wlan1: Open and authenticated
Mar 16 06:39:09 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 06:39:09 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 59)
Mar 16 07:13:45 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 07:13:45 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 07:13:45 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 07:13:45 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 07:13:45 kernel: wlan1: Open and authenticated
Mar 16 07:20:31 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 07:20:31 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 66)
Mar 16 07:41:40 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 07:41:40 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 69)
Mar 16 08:03:35 dnsmasq[1300]: script process exited with status 1
Mar 16 08:08:03 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 08:08:03 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 73)
Mar 16 08:27:35 kernel: wlan1: A STA is rejected by 802.1x daemon - 7C:D1:C3:42:58:90
Mar 16 09:35:07 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 09:35:07 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 89)
Mar 16 09:43:47 morda[2314]: user admin is logged in with administrator privileges to the ip ::ffff:192.168.0.43
Mar 16 10:21:59 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 10:21:59 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 97)
Mar 16 11:05:03 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 11:05:03 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 11:05:03 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 11:05:03 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 11:05:03 kernel: wlan1: Open and authenticated
Mar 16 11:27:50 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 11:28:47 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 11:28:47 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 11:28:47 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 11:28:47 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 11:28:47 kernel: wlan1: Open and authenticated
Mar 16 13:28:01 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 13:28:22 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 13:28:22 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 13:28:22 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 13:28:22 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 13:28:22 kernel: wlan1: Open and authenticated
Mar 16 13:31:41 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 13:31:41 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 133)
Mar 16 15:49:17 INADYN[1312]: INADYN:IP: Error 0x83 in recv()
Mar 16 15:49:17 INADYN[1312]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 16 15:49:17 INADYN[1312]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 158)
Mar 16 16:28:14 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 16:28:25 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 16:28:25 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 16:28:25 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 16:28:25 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 16:28:25 kernel: wlan1: Open and authenticated
Mar 16 16:36:39 kernel: wlan1: A wireless client is deauthenticated - 84:00:D2:C8:E3:FE
Mar 16 16:36:45 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 16:36:45 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 16:36:45 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 16:36:45 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 16:36:46 kernel: wlan1: Open and authenticated
Mar 16 16:45:52 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 16:45:52 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 168)
Mar 16 16:51:40 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 16:51:40 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 168)
Mar 16 17:28:20 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 17:48:04 INADYN[1312]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 16 17:48:04 INADYN[1312]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 178)
Mar 16 18:02:39 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 18:02:39 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 18:02:39 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 18:02:39 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 18:02:39 kernel: wlan1: Open and authenticated
Mar 16 18:02:44 kernel: wlan1: A wireless client is disassociated - 7C:D1:C3:42:58:90
Mar 16 18:08:19 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 18:08:19 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 18:08:19 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 18:08:19 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 18:08:19 kernel: wlan1: Open and authenticated
Mar 16 19:30:00 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 19:30:00 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 19:30:00 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 19:30:00 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 19:30:00 kernel: wlan1: Open and authenticated
Mar 16 21:28:32 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 21:40:36 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 21:40:36 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 21:40:36 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 21:40:36 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 21:40:36 kernel: wlan1: Open and authenticated
Mar 16 22:28:38 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 16 22:28:49 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 22:28:49 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 22:28:49 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 22:28:49 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 16 22:28:49 kernel: wlan1: Open and authenticated
Mar 16 22:37:21 morda[3651]: user admin is logged in with administrator privileges to the ip ::ffff:192.168.0.43
Mar 16 22:37:35 kernel: br0: port 2(wlan1) entering disabled state
Mar 16 22:37:35 kernel: br0: port 3(wlan0) entering disabled state
Mar 16 22:37:36 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Mar 16 22:37:37 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Mar 16 22:37:37 kernel: [PHY_ConfigMACWithParaFile][MACPHY_REG]
Mar 16 22:37:37 kernel: **********************************
Mar 16 22:37:37 kernel: ** NOTE!! RTL8192D INTERNAL PA! **
Mar 16 22:37:37 kernel: **********************************
Mar 16 22:37:37 kernel: [phy_RF6052_Config_ParaFile][radio_a_intPA]
Mar 16 22:37:37 kernel: [phy_RF6052_Config_ParaFile][radio_b_intPA]
Mar 16 22:37:37 kernel: ===> Load_92D_Firmware
Mar 16 22:37:37 kernel: Firmware check 48004(0)
Mar 16 22:37:37 kernel: [Load_92D_Firmware][rtl8192dfw_n]
Mar 16 22:37:37 kernel: <=== Load_92D_Firmware
Mar 16 22:37:37 kernel: br0: port 3(wlan0) entering learning state
Mar 16 22:37:37 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Mar 16 22:37:38 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Mar 16 22:37:38 kernel: [PHY_ConfigMACWithParaFile][MACPHY_REG_92C]
Mar 16 22:37:38 kernel: ===> Load_92C_Firmware
Mar 16 22:37:38 kernel: <=== Load_92C_Firmware
Mar 16 22:37:38 kernel: br0: port 2(wlan1) entering learning state
Mar 16 22:37:38 kernel: br0: port 2(wlan1) entering disabled state
Mar 16 22:37:38 kernel: br0: port 3(wlan0) entering disabled state
Mar 16 22:37:38 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Mar 16 22:37:39 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Mar 16 22:37:39 kernel: [PHY_ConfigMACWithParaFile][MACPHY_REG_92C]
Mar 16 22:37:39 kernel: ===> Load_92C_Firmware
Mar 16 22:37:39 kernel: <=== Load_92C_Firmware
Mar 16 22:37:39 kernel: br0: port 2(wlan1) entering learning state
Mar 16 22:37:39 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 22:37:39 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 22:37:39 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 22:37:39 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 22:37:39 kernel: wlan1: Open and authenticated
Mar 16 22:37:49 kernel: br0: port 2(wlan1) entering forwarding state
Mar 16 22:37:59 kernel: br0: port 2(wlan1) entering disabled state
Mar 16 22:37:59 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Mar 16 22:38:00 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Mar 16 22:38:00 kernel: [PHY_ConfigMACWithParaFile][MACPHY_REG_92C]
Mar 16 22:38:00 kernel: ===> Load_92C_Firmware
Mar 16 22:38:00 kernel: <=== Load_92C_Firmware
Mar 16 22:38:00 kernel: br0: port 2(wlan1) entering learning state
Mar 16 22:38:01 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 22:38:01 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 22:38:01 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 22:38:01 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 22:38:01 kernel: wlan1: Open and authenticated
Mar 16 22:38:10 kernel: br0: port 2(wlan1) entering forwarding state
Mar 16 22:38:12 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 22:38:12 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 22:38:12 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 22:38:12 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 22:38:12 kernel: wlan1: Open and authenticated
Mar 16 22:38:28 kernel: wlan1: A wireless client is disassociated - 7C:D1:C3:42:58:90
Mar 16 22:38:40 kernel: br0: port 2(wlan1) entering disabled state
Mar 16 22:38:40 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Mar 16 22:38:41 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Mar 16 22:38:41 kernel: [PHY_ConfigMACWithParaFile][MACPHY_REG_92C]
Mar 16 22:38:41 kernel: ===> Load_92C_Firmware
Mar 16 22:38:41 kernel: <=== Load_92C_Firmware
Mar 16 22:38:41 kernel: br0: port 2(wlan1) entering learning state
Mar 16 22:38:41 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 22:38:41 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 22:38:41 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 22:38:41 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 16 22:38:41 kernel: wlan1: Open and authenticated
Mar 16 22:38:51 kernel: br0: port 2(wlan1) entering forwarding state
Mar 16 22:41:51 kernel: wlan1: Delete MC entry not found!
Mar 16 22:41:51 kernel: wlan1: Delete MC entry not found!
Mar 16 22:44:23 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 22:44:23 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 22:44:23 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 22:44:23 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 22:44:23 kernel: wlan1: Open and authenticated
Mar 16 22:44:37 kernel: wlan1: A wireless client is disassociated - 7C:D1:C3:42:58:90
Mar 16 22:54:07 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 22:54:07 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 16 22:54:07 kernel: wlan1: WPA2-AES PSK authentication in progress...
Mar 16 22:54:07 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 16 22:54:08 kernel: wlan1: Open and authenticated
Mar 16 22:54:23 kernel: wlan1: A wireless client is disassociated - 7C:D1:C3:42:58:90

Теперь отваливается айфон (мак на 7С) и андроид (мак на 84). Но андроид реже стал отпадать фактически (то есть у меня вайбер отпадал после пробуждения и значок wifi пропадал и появлялся. И в расходе батареи тоже было видно пропуски в работе wi-fi). Если быть точным, то за сегодня отвалов реальных на андроиде не было. Да и на ноуте тоже. Но теперь сама по себе (как показалось) возникла проблема – по wi-fi упала скорость до 3-4 мбит (проверял на ноуте) :shock: Раньше упиралось в драйвер адаптера ноутбука. Обновил – скорость стала 70-80 мбит вместо 40-50. И вот где-то дня 3 уже точно как эти несчастные 3-4 мбит, потому что качали сериал на 180-300 кб/с. Подумали, что просто сидер такой. Прогнал в спидтесте сейчас и реально 3-4 мбит/с. Настройки те же. Только отключил 5 ггц сейчас.
UPD: перезапустил роутер и стало опять ~90 мбит/с. Что это было...

Цитата:
может пойму сам.

Будем вдвоем. Больше никто что-то из владельцев не пишет.


Последний раз редактировалось Bratken Вт мар 17, 2015 03:31, всего редактировалось 1 раз.

Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Вт мар 17, 2015 00:45 
Не в сети

Зарегистрирован: Пт сен 23, 2005 00:52
Сообщений: 112
Откуда: Moscow
Раз не пишут - значит у них все классно. :-)

По своей проблеме, на случай если кому пригодится: "checkServerActive:150 ##Server is not active!" в логах - это он все-таки отваливается по причине неответа сервером на Hello сообщения l2tp. Выкроил сегодня чуток времени и быстренько отдизасмил код /bin/l2tpd - оно там легко находится. Возможно, сервер у провайдера глючил и не отвечал на эти hello (хотя по стандарту должен), а может и сам клиент такой... Он про себя говорит l2tpd version 0.69 с копирайтами соответствующих авторов, но судя по дизасму тех кусков, что я смотрел, код сильно другой и это, видать, какой-то суровый форк. Полез на tsd.dlink.com.tw посмотреть - а там не то что этого l2tpd, но и вообще прошивки роутера ревизии D нету. :-( Господа из Длинка, плиз, попросите при случае HQ - пусть выложат хоть что-нибудь...
Сейчас вот уже полдня все нормально работает на 2.5.35 - буду дальше смотреть и экспериментировать.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Пт мар 20, 2015 23:37 
Не в сети

Зарегистрирован: Пт сен 23, 2005 00:52
Сообщений: 112
Откуда: Moscow
После занимательного дебага методом тыка выяснил причины отвала DLNA. Причиной этой является полная длина пути до каждого файла, который он сканирует и с которым работает. Там, судя по всему, буфер ограниченной длины (очевидно на 128 байтов без учета служебных) и в итоге пути длиннее 124 байт вызывают падение сканирующего процесса с ошибкой, указанной несколькими сообщениями выше. Соответственно, если названия файлов/каталогов на русском, то каждая буква занимает уже 2 байта и тогда итоговый путь совсем короткий получается.... И если свои собственные файлы переименовать еще можно (хотя я вот сейчас не представляю как мне адекватно переименовать папку "Союзмульфильм" и видео внутри нее с названиями в именах файлов), но, например, торренты уже затруднительно - там обычно папка торрента, внутри еще подпапки какие-нибудь, да и имена файлов обычно длиннющие... В общем допустимую длину пути надо увеличивать точно. В баг-трекере проекта даже похожая проблема висит уже давно: http://sourceforge.net/p/minidlna/bugs/50/ - возможно, достаточно как там рекомендуется просто поменять опцию в файлике перед компиляцией, выделив побольше буфер под путь файла.
Будет здорово, если поправите в следующей прошивке. И поделитесь ей, пожалуйста, сразу же - буду очень признателен. :-)


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Ср мар 25, 2015 23:45 
Не в сети

Зарегистрирован: Сб мар 29, 2014 12:29
Сообщений: 3
А каким способом можно прошивку 2.5.35 получить?


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Чт мар 26, 2015 01:39 
Не в сети

Зарегистрирован: Вс фев 01, 2015 01:40
Сообщений: 76
Вот лог за 3 дня на всякий случай. Может что-то интересное увидите. Кстати, да. Переключился на WPA с WPA2 и меньше отвалов в журнале стало или что это, когда associated и disassociated пишет. У меня такой лог за день раньше набегал :D тут конечно ddns опять что-то кочевряжится, но прошивка уже не при чем, насколько я понял.
Скрытый текст: показать
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:09 kernel: error!!add nexthop error! retval (-9)
Mar 23 21:57:11 INADYN[2589]: INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
Mar 23 21:57:15 INADYN[2589]: I:INADYN: IP address for alias '.dlinkddns.com' needs update to '93.81.92.196'
Mar 23 21:57:15 INADYN[2589]: I:INADYN: Alias '.dlinkddns.com' to IP '93.81.92.196' updated successful.
Mar 23 22:04:57 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 23 22:05:38 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 23 22:05:38 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 23 22:05:38 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 23 22:05:38 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 23 22:05:38 kernel: wlan1: Open and authenticated
Mar 23 22:28:41 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 22:28:41 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 6)
Mar 23 22:39:33 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 22:39:33 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 7)
Mar 23 22:45:21 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 22:45:21 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 7)
Mar 23 22:56:16 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 22:56:16 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 8)
Mar 23 23:07:09 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 23:07:09 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 9)
Mar 23 23:23:21 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 23:23:21 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 11)
Mar 23 23:34:36 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 23:34:36 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 12)
Mar 23 23:41:39 INADYN[2589]: INADYN:IP: Error 0x83 in recv()
Mar 23 23:41:39 INADYN[2589]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 23 23:41:39 INADYN[2589]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 12)
Mar 23 23:47:27 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 23 23:47:27 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 12)
Mar 24 00:33:54 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 00:33:54 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 20)
Mar 24 01:00:12 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 01:00:12 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 24)
Mar 24 01:05:08 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 24 01:05:08 kernel: wlan1: A STA is rejected by 802.1x daemon - 9C:B7:0D:A1:68:15
Mar 24 01:05:49 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 01:05:49 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 01:05:49 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 01:05:49 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 01:05:49 kernel: wlan1: Open and authenticated
Mar 24 01:16:28 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 01:16:28 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 26)
Mar 24 02:05:14 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 24 02:05:35 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 02:05:35 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 02:05:35 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 02:05:35 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 02:05:35 kernel: wlan1: Open and authenticated
Mar 24 02:24:55 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 02:24:55 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 38)
Mar 24 02:45:54 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 02:45:54 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 41)
Mar 24 03:03:15 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 03:03:15 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 43)
Mar 24 04:05:23 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 04:05:23 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 54)
Mar 24 04:26:22 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 04:26:22 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 57)
Mar 24 04:37:22 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 04:37:22 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 58)
Mar 24 04:53:27 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 04:53:27 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 60)
Mar 24 04:59:15 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 04:59:15 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 60)
Mar 24 05:05:03 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 05:05:03 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 60)
Mar 24 06:17:54 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 06:17:54 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 73)
Mar 24 06:33:49 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 06:33:49 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 75)
Mar 24 06:39:37 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 06:39:37 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 75)
Mar 24 06:45:25 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 06:45:25 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 75)
Mar 24 06:51:13 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 06:51:13 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 75)
Mar 24 07:25:24 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 24 07:25:24 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 07:25:24 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 07:25:24 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 24 07:25:24 kernel: wlan1: Open and authenticated
Mar 24 07:57:09 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 07:57:09 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 07:57:09 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 07:57:09 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 07:57:09 kernel: wlan1: Open and authenticated
Mar 24 08:30:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 08:30:04 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 08:30:04 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 08:30:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 08:30:04 kernel: wlan1: Open and authenticated
Mar 24 08:50:20 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 24 08:50:20 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 08:50:20 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 08:50:20 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 24 08:50:20 kernel: wlan1: Open and authenticated
Mar 24 09:00:49 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 09:00:49 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 99)
Mar 24 09:10:14 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 09:10:14 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 09:10:14 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 09:10:14 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 09:10:14 kernel: wlan1: Open and authenticated
Mar 24 09:52:46 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 09:52:46 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 108)
Mar 24 09:58:34 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 09:58:34 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 108)
Mar 24 10:29:58 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 10:29:58 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 113)
Mar 24 10:35:46 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 10:35:46 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 113)
Mar 24 10:41:34 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 10:41:34 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 113)
Mar 24 11:48:57 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 11:48:57 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 125)
Mar 24 11:54:45 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 11:54:45 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 125)
Mar 24 13:05:38 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 24 13:06:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 13:06:04 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 13:06:04 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 13:06:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 13:06:04 kernel: wlan1: Open and authenticated
Mar 24 13:37:50 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 13:37:50 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 144)
Mar 24 14:05:44 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 24 14:45:10 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 14:45:10 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 156)
Mar 24 14:50:58 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 14:50:58 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 156)
Mar 24 15:32:22 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 15:32:22 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 163)
Mar 24 15:38:10 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 15:38:10 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 163)
Mar 24 15:43:58 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 15:43:58 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 163)
Mar 24 16:25:39 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 16:25:39 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 170)
Mar 24 16:31:27 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 16:31:27 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 170)
Mar 24 16:51:08 INADYN[2589]: INADYN:IP: Error 0x83 in recv()
Mar 24 16:51:08 INADYN[2589]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 24 16:51:08 INADYN[2589]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 172)
Mar 24 17:01:59 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 17:01:59 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 173)
Mar 24 17:16:33 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 17:16:33 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 17:16:33 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 17:16:33 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 17:16:33 kernel: wlan1: Open and authenticated
Mar 24 17:18:19 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 17:18:19 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 175)
Mar 24 17:19:06 kernel: wlan1: A wireless client is disassociated - 9C:B7:0D:A1:68:15
Mar 24 17:19:06 kernel: wlan1: A wireless client is disassociated - 9C:B7:0D:A1:68:15
Mar 24 18:44:45 INADYN[2589]: INADYN:IP: Error 0x83 in recv()
Mar 24 18:44:45 INADYN[2589]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 24 18:44:45 INADYN[2589]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 190)
Mar 24 18:55:37 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 18:55:37 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 191)
Mar 24 19:06:31 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 19:06:31 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 192)
Mar 24 19:43:07 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 19:43:07 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 198)
Mar 24 19:59:23 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 19:59:23 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 200)
Mar 24 20:20:21 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 20:20:21 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 203)
Mar 24 20:39:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 20:39:04 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 20:39:04 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 20:39:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 24 20:39:04 kernel: wlan1: Open and authenticated
Mar 24 20:51:02 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 24 20:51:02 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 24 20:51:02 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 24 20:51:02 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 24 20:51:02 kernel: wlan1: Open and authenticated
Mar 24 21:01:46 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 21:01:46 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 210)
Mar 24 21:37:57 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 21:37:57 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 216)
Mar 24 21:43:45 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 21:43:45 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 216)
Mar 24 22:20:19 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 22:20:19 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 222)
Mar 24 23:55:25 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 24 23:55:25 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 239)
Mar 25 00:16:10 kernel: wlan1: A wireless client is disassociated - 9C:B7:0D:A1:68:15
Mar 25 00:16:49 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 25 00:16:49 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 00:16:49 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 00:16:49 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 25 00:16:49 kernel: wlan1: Open and authenticated
Mar 25 00:21:52 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 00:21:52 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 243)
Mar 25 00:27:26 kernel: wlan1: A wireless client is disassociated - 9C:B7:0D:A1:68:15
Mar 25 02:47:12 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 02:47:12 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 270)
Mar 25 04:24:32 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 04:24:32 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 288)
Mar 25 04:35:23 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 04:35:23 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 289)
Mar 25 04:41:11 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 04:41:11 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 289)
Mar 25 05:22:57 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 05:22:57 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 296)
Mar 25 05:28:45 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 05:28:45 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 296)
Mar 25 05:44:45 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 05:44:45 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 298)
Mar 25 06:06:17 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 25 06:06:58 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 06:06:58 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 06:06:58 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 06:06:58 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 06:06:58 kernel: wlan1: Open and authenticated
Mar 25 06:16:30 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 06:16:30 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 303)
Mar 25 06:27:57 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 06:27:57 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 304)
Mar 25 06:33:45 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 06:33:45 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 304)
Mar 25 07:05:21 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 07:05:21 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 309)
Mar 25 07:21:17 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 07:21:17 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 311)
Mar 25 07:25:16 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 25 07:25:16 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 07:25:16 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 07:25:16 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 25 07:25:16 kernel: wlan1: Open and authenticated
Mar 25 07:27:05 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 07:27:05 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 311)
Mar 25 07:58:15 kernel: wlan1: A wireless client is disassociated - 9C:B7:0D:A1:68:15
Mar 25 07:59:00 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 25 07:59:00 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 07:59:00 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 07:59:00 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Mar 25 07:59:00 kernel: wlan1: Open and authenticated
Mar 25 08:03:33 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 08:03:33 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 317)
Mar 25 08:09:21 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 08:09:21 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 317)
Mar 25 08:30:23 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 08:30:23 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 320)
Mar 25 09:06:28 kernel: wlan1: A STA is rejected by 802.1x daemon - 7C:D1:C3:42:58:90
Mar 25 09:42:17 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 09:42:17 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 333)
Mar 25 09:53:09 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 09:53:09 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 334)
Mar 25 10:24:25 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 10:24:25 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 339)
Mar 25 11:06:33 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 25 11:06:49 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 11:06:49 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 11:06:49 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 11:06:49 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 11:06:49 kernel: wlan1: Open and authenticated
Mar 25 11:06:50 kernel: wlan1: A wireless client is deauthenticated - 84:00:D2:C8:E3:FE
Mar 25 11:06:52 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 11:06:52 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 11:06:52 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 11:06:52 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 11:06:52 kernel: wlan1: Open and authenticated
Mar 25 11:06:57 kernel: wlan1: A wireless client is deauthenticated - 84:00:D2:C8:E3:FE
Mar 25 11:06:59 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 11:06:59 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 11:06:59 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 11:06:59 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 11:06:59 kernel: wlan1: Open and authenticated
Mar 25 11:11:13 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 11:11:13 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 347)
Mar 25 11:53:27 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 11:53:27 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 354)
Mar 25 12:04:19 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 12:04:19 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 355)
Mar 25 12:15:12 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 12:15:12 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 356)
Mar 25 12:26:07 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 12:26:07 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 357)
Mar 25 12:42:04 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 12:42:04 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 359)
Mar 25 14:26:41 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 14:26:41 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 378)
Mar 25 15:06:42 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 25 15:07:03 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 15:07:03 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 15:07:03 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 15:07:03 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 15:07:05 kernel: wlan1: Open and authenticated
Mar 25 15:32:26 INADYN[2589]: INADYN:IP: Error 0x83 in recv()
Mar 25 15:32:26 INADYN[2589]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 25 15:32:26 INADYN[2589]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 389)
Mar 25 15:43:21 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 15:43:21 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 390)
Mar 25 16:06:48 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 25 16:07:28 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 16:07:28 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 16:07:28 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 16:07:28 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 16:07:28 kernel: wlan1: Open and authenticated
Mar 25 16:29:35 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 16:29:35 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 16:29:35 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 16:29:35 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 16:29:35 kernel: wlan1: Open and authenticated
Mar 25 17:05:33 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 17:05:33 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 405)
Mar 25 17:16:25 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 17:16:25 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 406)
Mar 25 17:22:13 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 17:22:13 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 406)
Mar 25 17:28:01 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 17:28:01 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 406)
Mar 25 18:06:56 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Mar 25 18:19:30 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 25 18:19:30 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 18:19:30 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 18:19:30 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Mar 25 18:19:30 kernel: wlan1: Open and authenticated
Mar 25 18:30:54 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 18:30:54 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 417)
Mar 25 18:36:42 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 18:36:42 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 417)
Mar 25 19:29:14 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 19:29:14 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 426)
Mar 25 19:55:19 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 19:55:19 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 430)
Mar 25 21:17:31 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 21:17:31 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 445)
Mar 25 21:18:17 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 21:18:17 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 25 21:18:17 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 25 21:18:17 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 25 21:18:17 kernel: wlan1: Open and authenticated
Mar 25 22:00:00 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 22:00:00 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 452)
Mar 25 22:05:48 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 22:05:48 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 452)
Mar 25 22:26:46 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 22:26:46 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 455)
Mar 25 22:32:34 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 22:32:34 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 455)
Mar 25 23:07:01 INADYN[2589]: INADYN:IP: Error 0x83 in recv()
Mar 25 23:07:01 INADYN[2589]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 25 23:07:01 INADYN[2589]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 460)
Mar 25 23:12:49 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 23:12:49 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 460)
Mar 25 23:40:11 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 23:40:11 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 464)
Mar 25 23:45:59 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 25 23:45:59 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 464)
Mar 26 00:07:39 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 26 00:07:39 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 467)
Mar 26 00:23:24 udhcpc[1155]: Entering renew state
Mar 26 00:23:24 udhcpc[1155]: Sending renew...
Mar 26 00:23:24 udhcpc[1155]: Lease of 10.220.160.225 obtained, lease time 604800
Mar 26 00:49:41 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 26 00:49:41 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 474)
Mar 26 01:00:34 INADYN[2589]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 26 01:00:34 INADYN[2589]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 475)
Mar 26 01:40:11 morda[5822]: user admin is logged in with administrator privileges to the ip ::ffff:192.168.0.43


Цитата:
После занимательного дебага

Можно поподробнее о том, как и чем? Если не влом =) ну, или ссылкой ткнуть в нос. А то я не в теме, как все это проворачивать (включая заливку файлов на роутер или наоборот). Отвалы wi-fi не так уж критичны. Особенно в свете того, что страдает в 95% случаев только мой андроид, который сам по себе прошивка ещё местами глючная, т.к. кастомная. И это может быть причастным, несмотря на то, что с предыдущим рутером работало нормально. А в остальных случаях я отвалы вижу по журналу, но в работе не ощущается. Так бы тоже ковырнул да раскопал бы чего, может, тоже.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Чт мар 26, 2015 01:55 
Не в сети

Зарегистрирован: Пт сен 23, 2005 00:52
Сообщений: 112
Откуда: Moscow
С DLNA просто экспериментировал - добавлял разные каталоги и смотрел при сканировании которых вылетает. Так и понял, что на длину пути реагирует. На устройство файлы не закачивал (конкретно на этом роутере не ковырял, но обычно это не вполне тривиально - во флеше с записью зачастую область только под конфиги, а образ диска со всеми файлами разворачивается в память из read-only раздела при загрузке), а чтобы посмотреть внутренности l2tp-клиента - не мудрствуя лукаво скопировал его файл под именем лога, который можно скачать через веб-интерфейс, ну и скачал, соответственно. :-)


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Чт мар 26, 2015 12:16 
Не в сети

Зарегистрирован: Сб мар 29, 2014 12:29
Сообщений: 3
По прошествия года работы появилась проблема. Переодически (несколько раз в день) отваливается интернет. Помогает ребут либо ожиданий минут 10. Смена прошивки не влияет на результат.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Чт мар 26, 2015 12:23 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Пн ноя 10, 2014 11:44
Сообщений: 1048
Откуда: Ryazan
manaj писал(а):
По прошествия года работы появилась проблема. Переодически (несколько раз в день) отваливается интернет. Помогает ребут либо ожиданий минут 10. Смена прошивки не влияет на результат.

Тут либо аппаратная проблема роутера, либо что то с интернетом. Попробуйте кабель интернета напрямую к компьютеру подключить.

_________________
-Полезные настройки
-FAQ по разделу
-FAQ по роутерам на сайте
Телефон технической поддержки: 8-800-700-5465
Наша почта: support@dlink.ru
Группа в Telegram: https://t.me/dlink_ru


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Сб мар 28, 2015 17:57 
Не в сети

Зарегистрирован: Вс фев 01, 2015 01:40
Сообщений: 76
Цитата:
не мудрствуя лукаво скопировал его файл под именем лога

А как? У меня получилось только вставить флешку в роутер и сделать cp /bin/l2tpd /mnt/usb1_1. scp нет, tftp нет. Ничего нельзя. Папками копировать не дает. Толку правда от того, что скопировал.
Hosts нашелся в etc (с линуксом раз в год-два сталкиваюсь, не пинайте) и там две строки всего
Код:
127.0.0.1 localhost.localdomain localhost
192.168.0.1 Dlink-Router

Но страшненько так его редактировать :lol:
Надеюсь, что есть прогресс в обновлении прошивки :roll:

Телнет как-то связан с вайфаем? Потому что я отключил телнет и в журнале отвалы прекратились вот эти все associated и т.д. Да и на телефоне вайбер не уходил в оффлайн и сеть беспроводная не переподключалась.
Вот лог за последние 7 часов:
Скрытый текст: показать
Jan 1 00:00:05 syslogd started: BusyBox v1.19.2
Jan 1 00:00:06 kernel: Wan link is down
Jan 1 00:00:07 kernel: device eth0.2 entered promiscuous mode
Jan 1 00:00:07 kernel: device eth0 entered promiscuous mode
Jan 1 00:00:07 kernel: device wlan1 entered promiscuous mode
Jan 1 00:00:07 kernel: device wlan0 entered promiscuous mode
Jan 1 00:00:07 dnsmasq[1092]: warning: interface br0 does not currently exist
Jan 1 00:00:07 kernel: rtk_update_netif_vlan 15513 dp->portnum=5 vid=2
Jan 1 00:00:07 kernel: rtk_update_netif_vlan 15513 dp->portnum=1 vid=1
Jan 1 00:00:07 kernel: br0: port 2(wlan1) entering learning state
Jan 1 00:00:07 kernel: br0: port 1(eth0.2) entering learning state
Jan 1 00:00:09 kernel: Wan link is up!
Jan 1 00:00:11 udhcpc[1162]: UDHCP start..
Jan 1 00:00:11 udhcpc[1162]: udhcp client (v0.9.8) started (iface: eth1, connect: 5)
Jan 1 00:00:11 udhcpc[1162]: Sending discover...
Jan 1 00:00:11 dms_reset_uptime[1157]: enter key eth1_5
Jan 1 00:00:11 dms_reset_uptime[1157]: unable to remove file /tmp/stat.eth1_5
Jan 1 00:00:14 udhcpc[1162]: Lease of 10.220.160.225 obtained, lease time 2707
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 00:00:14 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:15 INADYN[1220]: INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
Jan 1 03:00:15 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Jan 1 03:00:15 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Jan 1 03:00:15 kernel: wlan1: WPA-AES PSK authentication in progress...
Jan 1 03:00:15 kernel: wlan1: A wireless client is associated - 7C:D1:C3:42:58:90
Jan 1 03:00:15 kernel: wlan1: Open and authenticated
Jan 1 03:00:16 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:16 l2tpd[1293]: This binary does not support kernel L2TP.
Jan 1 03:00:16 l2tpd[1294]: daemonize(1091)
Jan 1 03:00:16 l2tpd[1294]: l2tpd version 0.69 started on Dlink-Router PID:1294
Jan 1 03:00:16 l2tpd[1294]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
Jan 1 03:00:16 l2tpd[1294]: Forked by Scott Balmos and David Stipp, (C) 2001
Jan 1 03:00:16 l2tpd[1294]: Inherited by Jeff McAdams, (C) 2002
Jan 1 03:00:16 l2tpd[1294]: Listening on IP address 0.0.0.0, port 1701
Jan 1 03:00:17 kernel: br0: port 2(wlan1) entering forwarding state
Jan 1 03:00:17 kernel: br0: port 1(eth0.2) entering forwarding state
Jan 1 03:00:18 l2tpd[1294]: Connecting to host tp.internet.beeline.ru, port 1701
Jan 1 03:00:18 l2tpd[1294]: handle_avps: dont know how to handle atribute 46.
Jan 1 03:00:18 l2tpd[1294]: Connection established to 85.21.0.75, 1701. Local: 1803, Remote: 56303.
Jan 1 03:00:18 l2tpd[1294]: Calling on tunnel 1803
Jan 1 03:00:19 l2tpd[1294]: Call established with 85.21.0.75, Local: 9298, Remote: 17511, Serial: 1
Jan 1 03:00:19 l2tpd[1294]: control_finish(999):To generate CDN to store. +++++
Jan 1 03:00:19 l2tpd[1294]: control_finish(1005):c->ourcid(9298),c->cid(17511),c->qcid(-1),c->serno(1). +++++
Jan 1 03:00:19 pppd[1306]: entering dlock, dfd = -1
Jan 1 03:00:19 pppd[1306]: dlock: locked
Jan 1 03:00:19 pppd[1306]: pppd 2.4.4 started by admin, uid 0
Jan 1 03:00:19 pppd[1306]: Using interface ppp0
Jan 1 03:00:19 pppd[1306]: Connect: ppp0 <--> /dev/ttyp0
Jan 1 03:00:22 pppd[1306]: CHAP authentication failed: Too many connections
Jan 1 03:00:22 pppd[1306]: CHAP authentication failed
Jan 1 03:00:22 pppd[1306]: Connection terminated.
Jan 1 03:00:22 l2tpd[1294]: handle_avps: dont know how to handle atribute 46.
Jan 1 03:00:22 l2tpd[1294]: control_finish: Connection closed to 85.21.0.75, serial 1 (Authentication failure)
Jan 1 03:00:22 dnsmasq[1146]: script process exited with status 1
Jan 1 03:00:22 pppd[1306]: Connection terminated.
Jan 1 03:00:22 pppd[1306]: send_event_to_daemon
Jan 1 03:00:22 pppd[1306]: set ALREADY
Jan 1 03:00:22 pppd[1306]: Terminating on signal 15
Jan 1 03:00:22 pppd[1306]: Exit.
Jan 1 03:00:26 l2tpd[1294]: control_finish: Connection closed to 85.21.0.75, port 1701 (Tunnel was cleared), Local: 1803, Remote: 56303
Jan 1 03:00:31 wget_to_file[1157]: unable to connect: Operation now in progress (150)
Jan 1 03:00:33 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:33 l2tpd[1381]: This binary does not support kernel L2TP.
Jan 1 03:00:33 l2tpd[1382]: daemonize(1091)
Jan 1 03:00:33 l2tpd[1382]: l2tpd version 0.69 started on Dlink-Router PID:1382
Jan 1 03:00:33 l2tpd[1382]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
Jan 1 03:00:33 l2tpd[1382]: Forked by Scott Balmos and David Stipp, (C) 2001
Jan 1 03:00:33 l2tpd[1382]: Inherited by Jeff McAdams, (C) 2002
Jan 1 03:00:33 l2tpd[1382]: Listening on IP address 0.0.0.0, port 1701
Jan 1 03:00:35 l2tpd[1382]: Connecting to host tp.internet.beeline.ru, port 1701
Jan 1 03:00:36 l2tpd[1382]: Connection established to 85.21.0.255, 1701. Local: 22940, Remote: 3441.
Jan 1 03:00:36 l2tpd[1382]: Calling on tunnel 22940
Jan 1 03:00:36 l2tpd[1382]: Call established with 85.21.0.255, Local: 55642, Remote: 21558, Serial: 1
Jan 1 03:00:36 l2tpd[1382]: control_finish(999):To generate CDN to store. +++++
Jan 1 03:00:36 l2tpd[1382]: control_finish(1005):c->ourcid(55642),c->cid(21558),c->qcid(-1),c->serno(1). +++++
Jan 1 03:00:36 pppd[1388]: entering dlock, dfd = -1
Jan 1 03:00:36 pppd[1388]: dlock: locked
Jan 1 03:00:36 pppd[1388]: pppd 2.4.4 started by admin, uid 0
Jan 1 03:00:36 pppd[1388]: Using interface ppp0
Jan 1 03:00:36 pppd[1388]: Connect: ppp0 <--> /dev/ttyp0
Jan 1 03:00:36 pppd[1388]: CHAP authentication failed: Too many connections
Jan 1 03:00:36 pppd[1388]: CHAP authentication failed
Jan 1 03:00:36 pppd[1388]: Connection terminated.
Jan 1 03:00:36 pppd[1388]: Connection terminated.
Jan 1 03:00:36 pppd[1388]: send_event_to_daemon
Jan 1 03:00:36 pppd[1388]: set ALREADY
Jan 1 03:00:36 l2tpd[1382]: call_close: Call 55642 to 85.21.0.255 disconnected
Jan 1 03:00:36 pppd[1388]: Terminating on signal 15
Jan 1 03:00:36 pppd[1388]: Exit.
Jan 1 03:00:37 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Jan 1 03:00:37 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Jan 1 03:00:37 kernel: wlan1: WPA-AES PSK authentication in progress...
Jan 1 03:00:37 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Jan 1 03:00:37 kernel: wlan1: Open and authenticated
Jan 1 03:00:37 dnsmasq[1146]: script process exited with status 1
Jan 1 03:00:38 l2tpd[1432]: This binary does not support kernel L2TP.
Jan 1 03:00:38 l2tpd[1433]: daemonize(1091)
Jan 1 03:00:38 l2tpd[1433]: l2tpd version 0.69 started on Dlink-Router PID:1433
Jan 1 03:00:38 l2tpd[1433]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
Jan 1 03:00:38 l2tpd[1433]: Forked by Scott Balmos and David Stipp, (C) 2001
Jan 1 03:00:38 l2tpd[1433]: Inherited by Jeff McAdams, (C) 2002
Jan 1 03:00:38 l2tpd[1433]: Listening on IP address 0.0.0.0, port 1701
Jan 1 03:00:40 l2tpd[1433]: Connecting to host tp.internet.beeline.ru, port 1701
Jan 1 03:00:41 l2tpd[1433]: handle_avps: dont know how to handle atribute 46.
Jan 1 03:00:41 l2tpd[1433]: Connection established to 85.21.0.75, 1701. Local: 46076, Remote: 56349.
Jan 1 03:00:41 l2tpd[1433]: Calling on tunnel 46076
Jan 1 03:00:41 l2tpd[1433]: Call established with 85.21.0.75, Local: 37184, Remote: 47058, Serial: 1
Jan 1 03:00:41 l2tpd[1433]: control_finish(999):To generate CDN to store. +++++
Jan 1 03:00:41 l2tpd[1433]: control_finish(1005):c->ourcid(37184),c->cid(47058),c->qcid(-1),c->serno(1). +++++
Jan 1 03:00:41 pppd[1439]: entering dlock, dfd = -1
Jan 1 03:00:41 pppd[1439]: dlock: locked
Jan 1 03:00:41 pppd[1439]: pppd 2.4.4 started by admin, uid 0
Jan 1 03:00:41 pppd[1439]: Using interface ppp0
Jan 1 03:00:41 pppd[1439]: Connect: ppp0 <--> /dev/ttyp0
Jan 1 03:00:41 pppd[1439]: CHAP authentication failed: Too many connections
Jan 1 03:00:41 pppd[1439]: CHAP authentication failed
Jan 1 03:00:41 l2tpd[1433]: handle_avps: dont know how to handle atribute 46.
Jan 1 03:00:41 l2tpd[1433]: control_finish: Connection closed to 85.21.0.75, serial 1 (Authentication failure)
Jan 1 03:00:41 pppd[1439]: Modem hangup
Jan 1 03:00:41 pppd[1439]: Connection terminated.
Jan 1 03:00:41 pppd[1439]: Connection terminated.
Jan 1 03:00:41 pppd[1439]: send_event_to_daemon
Jan 1 03:00:41 pppd[1439]: set ALREADY
Jan 1 03:00:41 pppd[1439]: Hangup (SIGHUP)
Jan 1 03:00:41 pppd[1439]: Terminating on signal 15
Jan 1 03:00:41 pppd[1439]: Exit.
Jan 1 03:00:45 l2tpd[1517]: This binary does not support kernel L2TP.
Jan 1 03:00:45 l2tpd[1518]: daemonize(1091)
Jan 1 03:00:45 l2tpd[1518]: l2tpd version 0.69 started on Dlink-Router PID:1518
Jan 1 03:00:45 l2tpd[1518]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
Jan 1 03:00:45 l2tpd[1518]: Forked by Scott Balmos and David Stipp, (C) 2001
Jan 1 03:00:45 l2tpd[1518]: Inherited by Jeff McAdams, (C) 2002
Jan 1 03:00:45 l2tpd[1518]: Listening on IP address 0.0.0.0, port 1701
Jan 1 03:00:47 morda[1519]: user admin is logged in with administrator privileges to the ip ::ffff:192.168.0.43
Jan 1 03:00:48 l2tpd[1518]: Connecting to host tp.internet.beeline.ru, port 1701
Jan 1 03:00:50 l2tpd[1518]: handle_avps: dont know how to handle atribute 46.
Jan 1 03:00:50 l2tpd[1518]: Connection established to 85.21.0.95, 1701. Local: 27126, Remote: 8609.
Jan 1 03:00:50 l2tpd[1518]: Calling on tunnel 27126
Jan 1 03:00:51 l2tpd[1518]: Call established with 85.21.0.95, Local: 8721, Remote: 47105, Serial: 1
Jan 1 03:00:51 l2tpd[1518]: control_finish(999):To generate CDN to store. +++++
Jan 1 03:00:51 l2tpd[1518]: control_finish(1005):c->ourcid(8721),c->cid(47105),c->qcid(-1),c->serno(1). +++++
Jan 1 03:00:51 pppd[1534]: entering dlock, dfd = -1
Jan 1 03:00:51 pppd[1534]: dlock: locked
Jan 1 03:00:51 pppd[1534]: pppd 2.4.4 started by admin, uid 0
Jan 1 03:00:51 pppd[1534]: Using interface ppp0
Jan 1 03:00:51 pppd[1534]: Connect: ppp0 <--> /dev/ttyp0
Jan 1 03:00:51 pppd[1534]: CHAP authentication succeeded: CHAP authentication success, unit 10561
Jan 1 03:00:51 pppd[1534]: CHAP authentication succeeded
Jan 1 03:00:51 pppd[1534]: local IP address 128.68.133.184
Jan 1 03:00:51 pppd[1534]: remote IP address 128.68.128.1
Jan 1 03:00:51 pppd[1534]: primary DNS address 85.21.192.5
Jan 1 03:00:51 pppd[1534]: secondary DNS address 213.234.192.7
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:51 kernel: error!!add nexthop error! retval (-9)
Jan 1 03:00:53 INADYN[1582]: INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
Jan 1 03:00:54 INADYN[1582]: I:INADYN: IP address for alias '.dlinkddns.com' needs update to '128.68.133.184'
Jan 1 03:00:54 INADYN[1582]: I:INADYN: Alias '.dlinkddns.com' to IP '128.68.133.184' updated successful.
Mar 31 14:22:03 pppd[1534]: System time change detected.
Mar 31 14:22:15 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 31 14:22:15 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 31 14:22:15 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 31 14:22:15 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 31 14:22:15 kernel: wlan1: Open and authenticated
Mar 31 14:22:16 dnsmasq[1568]: script process exited with status 1
Mar 31 14:31:58 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 14:31:58 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 2)
Mar 31 14:37:46 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 14:37:46 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 2)
Mar 31 14:42:58 udhcpc[1194]: Entering renew state
Mar 31 14:42:58 udhcpc[1194]: Sending renew...
Mar 31 14:42:59 udhcpc[1194]: Lease of 10.220.160.225 obtained, lease time 604800
Mar 31 14:48:51 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 14:48:51 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 3)
Mar 31 14:54:39 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 14:54:39 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 3)
Mar 31 15:25:55 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 15:25:55 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 8)
Mar 31 15:42:11 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 15:42:11 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 10)
Mar 31 17:04:57 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 17:04:57 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 25)
Mar 31 17:15:58 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 17:15:58 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 26)
Mar 31 17:21:46 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 17:21:46 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 26)
Mar 31 17:31:11 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Mar 31 17:31:11 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 31 17:31:11 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 26)
Mar 31 18:02:19 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 18:02:19 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 31)
Mar 31 18:39:44 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 18:39:44 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 37)
Mar 31 18:53:23 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 31 18:53:23 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Mar 31 18:53:23 kernel: wlan1: WPA-AES PSK authentication in progress...
Mar 31 18:53:23 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Mar 31 18:53:23 kernel: wlan1: Open and authenticated
Mar 31 19:16:08 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 19:16:08 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 43)
Mar 31 20:18:01 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 20:18:01 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 54)
Mar 31 20:35:53 morda[2968]: user admin is logged in with administrator privileges to the ip ::ffff:192.168.0.43
Mar 31 20:39:03 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Mar 31 20:39:03 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 57)

Дважды попадается...
Код:
A wireless client is associated - 84:00:D2:C8:E3:FE
BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
kernel: wlan1: WPA-AES PSK authentication in progress...
kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE

...но это перезапуск роутера и перезапуск телефона. Всё. Отвалов нет. Я только галку с телнета убрал.


Вернуться наверх
 Профиль  
 
СообщениеДобавлено: Чт апр 02, 2015 21:14 
Не в сети

Зарегистрирован: Вс фев 01, 2015 01:40
Сообщений: 76
Включил яндекс.DNS для пробы и пошло-поехало по журналу отваливаться:
Скрытый текст: показать
Apr 2 07:19:23 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Apr 2 07:19:23 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Apr 2 07:19:23 kernel: wlan1: WPA-AES PSK authentication in progress...
Apr 2 07:19:23 kernel: wlan1: A wireless client is associated - 9C:B7:0D:A1:68:15
Apr 2 07:19:23 kernel: wlan1: Open and authenticated
Apr 2 07:22:09 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Apr 2 07:22:40 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 07:22:40 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Apr 2 07:22:40 kernel: wlan1: WPA-AES PSK authentication in progress...
Apr 2 07:22:40 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 07:22:40 kernel: wlan1: Open and authenticated
Apr 2 07:26:37 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Apr 2 07:26:37 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 393)
Apr 2 07:32:25 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Apr 2 07:32:25 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 393)
Apr 2 07:37:38 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Apr 2 07:37:38 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Apr 2 07:37:38 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 393)
Apr 2 07:43:26 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Apr 2 07:43:26 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 393)
Apr 2 07:51:52 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Apr 2 07:51:52 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Apr 2 07:51:52 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 393)
Apr 2 07:57:40 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Apr 2 07:57:40 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 393)
Apr 2 08:02:48 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Apr 2 08:02:48 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Apr 2 08:02:48 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 393)
Apr 2 08:08:16 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Apr 2 08:08:16 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Apr 2 08:08:16 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 393)
Apr 2 08:14:04 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Apr 2 08:14:04 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 393)
Apr 2 08:19:52 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Apr 2 08:19:52 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 393)
Apr 2 08:22:15 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Apr 2 08:22:56 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 08:22:56 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Apr 2 08:22:56 kernel: wlan1: WPA-AES PSK authentication in progress...
Apr 2 08:22:56 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 08:22:56 kernel: wlan1: Open and authenticated
Apr 2 08:45:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 08:45:04 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Apr 2 08:45:04 kernel: wlan1: WPA-AES PSK authentication in progress...
Apr 2 08:45:04 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 08:45:04 kernel: wlan1: Open and authenticated
Apr 2 08:47:33 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Apr 2 08:47:33 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Apr 2 08:47:33 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 397)
Apr 2 09:03:06 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Apr 2 09:03:06 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Apr 2 09:03:06 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 399)
Apr 2 09:13:58 INADYN[1582]: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Apr 2 09:13:58 INADYN[1582]: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 400)
Apr 2 09:19:23 INADYN[1582]: INADYN:IP: Error 0x83 in recv()
Apr 2 09:19:23 INADYN[1582]: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Apr 2 09:19:23 INADYN[1582]: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 400)
Apr 2 09:22:18 kernel: wlan1: A STA is rejected by 802.1x daemon - 84:00:D2:C8:E3:FE
Apr 2 09:22:29 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 09:22:29 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Apr 2 09:22:29 kernel: wlan1: WPA-AES PSK authentication in progress...
Apr 2 09:22:29 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 09:22:30 kernel: wlan1: Open and authenticated
Apr 2 09:36:57 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 09:36:57 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Apr 2 09:36:57 kernel: wlan1: WPA-AES PSK authentication in progress...
Apr 2 09:36:57 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 09:36:57 kernel: wlan1: Open and authenticated
Apr 2 09:54:31 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 09:54:31 kernel: BIT(11) of 0xd2c = 1, 0xd2c = 0xcc979975
Apr 2 09:54:31 kernel: wlan1: WPA-AES PSK authentication in progress...
Apr 2 09:54:31 kernel: wlan1: A wireless client is associated - 84:00:D2:C8:E3:FE
Apr 2 09:54:31 kernel: wlan1: Open and authenticated

Какая может быть связь между галочками в опциях и вайфаем? :shock:


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

Зарегистрирован: Пт сен 23, 2005 00:52
Сообщений: 112
Откуда: Moscow
Несколько раз уже столкнулся с неприятным багом - через некоторое время работы (достаточно длительное - недели две или типа того) устройство перестает пропускать через себя трафик SIP. Совсем перестает - телефоны отваливаются (два разных телефона, три разных провайдера) и не могут зарегистрироваться на своих серверах. Соответствующая галочка в настройках, разумеется, стоит. Перезагрузка проблему решает и все само радостно подключается. Соответственно, вопрос - как бы можно было это дело продиагностировать? Я понимаю, что отловить вам самим такой баг будет очень трудно, поэтому скажите, что в консоли запустить и посмотреть в следующий раз, когда с ним столкнусь, чтобы можно было конкретный и четкий багрепорт сделать.
Спасибо!

ps: По DLNA не занимались еще? Свежих сборок прошивок нет?


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

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


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

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


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

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