faq обучение настройка
Текущее время: Вт апр 23, 2024 14:01

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




Начать новую тему Ответить на тему  [ Сообщений: 3071 ]  На страницу Пред.  1 ... 57, 58, 59, 60, 61, 62, 63 ... 205  След.
Автор Сообщение
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 10:25 
Не в сети

Зарегистрирован: Пн окт 08, 2012 17:56
Сообщений: 16
В-общем у меня нормально встала только прошивка: 1516_DIR_615K1_1.0.9_sdk-master, которую убрали с сервера. Устраивает всё!
На этом мучить железку заканчиваю. :)

_________________
Изображение


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 12:19 
Не в сети

Зарегистрирован: Вт окт 09, 2012 14:22
Сообщений: 25
OleginNK писал(а):
Прошился прошивкой 1.0.10,провайдер Дом.ру,ДНС ща везде автоматом стоят,ни раз за 3 дня лагов не было,скорость интернета на вайфай в районе 50(как заявлено провайдером),в общем впервые доволен стал аппаратом :D .Шился через ie10 в Win8.

почему же у меня скорость режит по воздуху?


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 13:03 
Не в сети

Зарегистрирован: Вс сен 16, 2012 11:31
Сообщений: 7
Странно почему то, когда выключаешь и включаешь маршрутизатор соединение есть, но не на один сайт не заходит, хотя и пингует нормально. Решается проблема перезагрузкой соединения(не самого маршрутизатора,с ней та же фигня)


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 14:56 
Не в сети

Зарегистрирован: Ср окт 31, 2012 16:08
Сообщений: 5
У меня и на 9 и на 10 прошивке тоже самое, только приходится входить внастройки IpTV и сохранять. Далее все работает до следующей перезагрузки.


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 17:13 
Не в сети

Зарегистрирован: Пн авг 06, 2012 08:24
Сообщений: 7
Rain4ik писал(а):
Skyiva писал(а):
Прошился на 1.0.10, как обрыв по WI-FI при загрузке через торрент был, так и остался...

Я поставил ограничение скорости торрент клиенту - 8000кб/сек, иначе происходит такой обрыв. Если качаете по WI-FI, возможно, нужно поставить еще меньше.

Дело в том, что обрыв идет даже при замере скорости соединения, т.е роутер при пиковых нагрузках на вх. соединение просто вылетает, на прошивке 1.0 такого не было, но скорость зато резало в разы. Ограничение торрент клиенту поставить конечно можно, но проще через провод подключиться , да и это это как бы не решает проблемы.


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 18:58 
Не в сети

Зарегистрирован: Ср ноя 03, 2010 03:36
Сообщений: 194
Откуда: Тверь
Прошивка 1.0.10, провайдер Мегаполис телеком (PPPOE) - интернет завелся. Тестируем. На прошивках 1.0.5-1.0.9 интернета не было.

_________________
У вас недостаточно прав для просмотра данной подписи


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 19:55 
Не в сети

Зарегистрирован: Пн окт 08, 2012 18:05
Сообщений: 13
у кого заработала прошивка 1.0.10 на провайдере Тис-Диалог Калининград?


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Вс ноя 04, 2012 21:30 
Не в сети

Зарегистрирован: Чт июн 21, 2012 23:41
Сообщений: 89
Откуда: Калининград
Wolfie писал(а):
у кого заработала прошивка 1.0.10 на провайдере Тис-Диалог Калининград?

У меня работает. Было пару глюков : винда7 показывала что интернет есть , роутер тоже , а пинг что с винды что с роутера на 8.8.8.8 нет.
помогает перезагрузка.


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Пн ноя 05, 2012 10:28 
Не в сети

Зарегистрирован: Чт ноя 01, 2012 18:17
Сообщений: 6
Подскажите пожалуйста какая прошивка лучше для PPTP, интернет отключается, роутер нужно перезагружать раз в сутки((


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Пн ноя 05, 2012 10:39 
Не в сети

Зарегистрирован: Вт авг 28, 2012 11:44
Сообщений: 17
Ув. сотрудники D-LINK, подскажите, пожалуйста, какие настройки беспроводной сети лучше для нормальной работы IPTV по воздуху?


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Пн ноя 05, 2012 14:11 
Не в сети

Зарегистрирован: Чт июн 21, 2012 23:41
Сообщений: 89
Откуда: Калининград
после недельной безупречной работы DIR-615K1 начались сюрпризы. после ночи роутер приходится перезагружать, хотя, сам роутер показывает что pppoe соединение активно, но интернета нет. Ниже прикладываю логи для сравнения НОРМАЛЬНОЙ и АВАРИЙНОЙ работы роутера:

Нормальная работа :
Скрытый текст: показать
Jan 1 00:00:14 syslogd started: BusyBox v1.19.2
Jan 1 00:00:14 resident: init lan
Jan 1 00:00:14 resident: start ipoe
Jan 1 00:00:14 start_ip: begin (br0 -> br0)
Jan 1 00:00:14 resident: start ipoe (v2139560600) on br0
Jan 1 00:00:14 kernel: Synthesized TLB modify handler fastpath (31 instructions).
Jan 1 00:00:14 kernel: PID hash table entries: 128 (order: 7, 512 bytes)
Jan 1 00:00:14 kernel: CPU: BCM53572 rev 1 at 300 MHz
Jan 1 00:00:14 kernel: Using 150.000 MHz high precision timer.
Jan 1 00:00:14 kernel: Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 00:00:14 kernel: Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jan 1 00:00:14 kernel: Memory: 29672k/32768k available (2023k kernel code, 3096k reserved, 444k data, 184k init, 0k highmem)
Jan 1 00:00:14 kernel: Mount-cache hash table entries: 512
Jan 1 00:00:14 kernel: NET: Registered protocol family 16
Jan 1 00:00:14 kernel: PCI: no core
Jan 1 00:00:15 resident: init wan
Jan 1 00:00:15 resident: start ipoe
Jan 1 00:00:15 start_ip: begin (wan1 -> wan1_1)
Jan 1 00:00:15 resident: start ipoe (v2) on wan1
Jan 1 00:00:15 resident: start pppd on wan1_2
Jan 1 00:00:15 resident: stop pppd on wan1_2
Jan 1 00:00:15 event: send event "ipoe down"
Jan 1 00:00:15 resident: set lock on wan1_2, with "/var/lock/wan1_2.lock"
Jan 1 00:00:15 resident: stopped link(contype:ppp, iface:wan1_2)
Jan 1 00:00:16 pppd[212]: Plugin /usr/lib/pppd/rp-pppoe.so loaded.
Jan 1 00:00:16 pppd[215]: pppd 2.4.4 started by admin, uid 0
Jan 1 00:00:16 pppd[215]: PPP session is 2308
Jan 1 00:00:16 pppd[215]: Using interface ppp0
Jan 1 00:00:16 pppd[215]: Connect: ppp0 <--> wan1
Jan 1 00:00:16 pppd[215]: CHAP authentication succeeded: Welcome to TIS Dialog
Jan 1 00:00:16 pppd[215]: CHAP authentication succeeded
Jan 1 00:00:16 pppd[215]: peer from calling number 00:50:C2:7F:C6:9B authorized
Jan 1 00:00:16 pppd[215]: local IP address 31.192.158.30
Jan 1 00:00:16 pppd[215]: remote IP address 83.219.128.0
Jan 1 00:00:16 pppd[215]: primary DNS address 83.219.128.10
Jan 1 00:00:16 pppd[215]: secondary DNS address 83.219.128.14
Jan 1 00:00:19 update_ddns: start
Jan 1 00:00:19 telnet-start: begin...
Jan 1 00:00:19 telnet-start: running on 23 port
Jan 1 00:00:19 telnet-start: succes!
Jan 1 00:00:19 resident: Out init_device
Jan 1 00:00:19 resident: record = action:up;iface:br0;contag:0;ipaddr:100.100.100.254;netmask:255.255.255.0;gateway:;dns1:;dns2:;
Jan 1 00:00:19 resident: phys_iface br0
Jan 1 00:00:19 test: ip_type = (null)
Jan 1 00:00:19 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:19 resident: phys_iface
Jan 1 00:00:19 resident: resident_ipoe_handler - 1
Jan 1 00:00:19 resident: resident_ipoe_handler - 3, name: br0
Jan 1 00:00:19 resident: record = action:down;iface:wan1;contag:1;
Jan 1 00:00:19 resident: phys_iface wan1
Jan 1 00:00:19 test: ip_type = (null)
Jan 1 00:00:19 resident: resident_ipoe_handler - l2:br0, l3:br0, tun:, ip_type:0
Jan 1 00:00:19 resident: resident_ipoe_handler - ipv4
Jan 1 00:00:19 resident: start ip_is_up on iface br0
Jan 1 00:00:19 resident: ip_is_up for link br0
Jan 1 00:00:19 resident: start dhcp+dns on br0
Jan 1 00:00:19 resident_ppp_handler: record = action:up;iface:ppp0;link:wan1_2;ipaddr:31.192.158.30;netmask:255.255.255.255;gateway:83.219.128.0;dns1:83.219.128.10;dns2:83.219.128.14;
Jan 1 00:00:19 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:19 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:19 resident: phys_iface
Jan 1 00:00:19 resident: resident_ipoe_handler - 2
Jan 1 00:00:19 resident: resident_ipoe_handler - 3, name: wan1_1
Jan 1 00:00:19 upnp: start - begin
Jan 1 00:00:19 dnsmasq[257]: started, version cachesize 512
Jan 1 00:00:19 dnsmasq[257]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack
Jan 1 00:00:19 dnsmasq-dhcp[257]: DHCP, IP range 100.100.100.1 -- 100.100.100.253, lease time 23m20s
Jan 1 00:00:19 dnsmasq[257]: read /tmp/hosts - 2 addresses
Jan 1 00:00:19 dnsmasq-dhcp[257]: read /etc/ethers - 3 addresses
Jan 1 00:00:19 syslog: SNet version started
Jan 1 00:00:19 miniupnpd[259]: HTTP listening on port 54248
Jan 1 00:00:19 miniupnpd[259]: Listening for NAT-PMP traffic on port 5351
Jan 1 00:00:19 resident: resident_ppp_handler - l2:wan1, l3:wan1_2, tun:
Jan 1 00:00:19 resident: resident_ipoe_handler - l2:wan1, l3:wan1_1, tun:, ip_type:0
Jan 1 00:00:19 resident: ip_is_down on wan1_1
Jan 1 00:00:19 resident: update dns
Jan 1 00:00:19 resident: update ntpclient
Jan 1 00:00:19 dnsmasq[257]: read /tmp/hosts - 2 addresses
Jan 1 00:00:20 dnsmasq-dhcp[257]: read /etc/ethers - 3 addresses
Jan 1 00:00:20 dnsmasq[257]: using nameserver 83.219.128.14#53
Jan 1 00:00:20 dnsmasq[257]: using nameserver 83.219.128.10#53
Jan 1 04:00:29 kernel: br0: topology change detected, propagating
Jan 1 04:00:29 kernel: br0: port 1(eth1) entering forwarding state
Jan 1 04:00:29 kernel: br0: topology change detected, propagating
Jan 1 04:00:29 kernel: br0: port 2(eth0.1) entering forwarding state
Jan 1 04:00:30 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Jan 1 04:00:30 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[56697]->[74.125.143.106]:[443]
Jan 1 04:00:30 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[56697]-[74.125.143.106]:[443]
Jan 1 04:00:30 kernel: CTF_INFO: assoc tunnel:8145f800 proto:00
Jan 1 04:00:30 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Jan 1 04:00:30 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[56698]->[173.194.69.125]:[5222]
Jan 1 04:00:30 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[56698]-[173.194.69.125]:[5222]
Jan 1 04:00:30 kernel: CTF_INFO: assoc tunnel:8145f800 proto:00
Jan 1 04:00:31 dnsmasq-dhcp[257]: DHCPREQUEST(br0) 100.100.100.1 00:13:d4:b8:50:2e
Jan 1 04:00:31 dnsmasq-dhcp[257]: DHCPACK(br0) 100.100.100.1 00:13:d4:b8:50:2e Andrey
Jan 1 04:00:32 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Jan 1 04:00:32 kernel: Call Trace:
Jan 1 04:00:32 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Jan 1 04:00:32 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Jan 1 04:00:32 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Jan 1 04:00:32 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Jan 1 04:00:32 kernel: Failed to add MFDB entry for 0 81e33000
Jan 1 04:00:32 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Jan 1 04:00:32 kernel: Call Trace:
Jan 1 04:00:32 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Jan 1 04:00:32 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Jan 1 04:00:32 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Jan 1 04:00:32 kernel: Call Trace:
Jan 1 04:00:32 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Jan 1 04:00:32 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Jan 1 04:00:32 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Jan 1 04:00:32 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Jan 1 04:00:32 kernel: Failed to add MFDB entry for 0 81e33000
Jan 1 04:00:32 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Jan 1 04:00:32 kernel: Call Trace:
Jan 1 04:00:32 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Jan 1 04:00:32 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Jan 1 04:00:32 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Jan 1 04:00:32 kernel: Call Trace:
Jan 1 04:00:32 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Jan 1 04:00:32 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Jan 1 04:00:32 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Jan 1 04:00:32 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Jan 1 04:00:32 kernel: Failed to add MFDB entry for 0 81e33000
Jan 1 04:00:35 dnsmasq-dhcp[257]: DHCPINFORM(br0) 100.100.100.1 00:13:d4:b8:50:2e
Jan 1 04:00:35 dnsmasq-dhcp[257]: DHCPACK(br0) 100.100.100.1 00:13:d4:b8:50:2e Andrey
Jan 1 04:00:41 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Jan 1 04:00:41 kernel: CTF_INFO: txif=[ppp0] proto=[17] ip=[100.100.100.1]:[63313]->[94.245.121.253]:[3544]
Jan 1 04:00:41 kernel: _ctf_pppox_assoc_tunnel: found ipc:[17]-[100.100.100.1]:[63313]-[94.245.121.253]:[3544]
Jan 1 04:00:41 kernel: CTF_INFO: assoc tunnel:8145f800 proto:00
Jan 1 04:00:41 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Jan 1 04:00:41 kernel: Call Trace:
Jan 1 04:00:41 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Jan 1 04:00:41 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Jan 1 04:00:41 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Jan 1 04:00:41 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Jan 1 04:00:41 kernel: Failed to add MFDB entry for 0 81e33000
Nov 3 20:16:42 pppd[215]: System time change detected.
Nov 3 20:16:44 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:16:44 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[56701]->[173.194.35.227]:[443]
Nov 3 20:16:44 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[56701]-[173.194.35.227]:[443]
Nov 3 20:16:44 kernel: CTF_INFO: assoc tunnel:8145f800 proto:00
Nov 3 20:16:44 kernel: pppoe_ctf_xmit_validate: pkt len bigger then tunnel's MTU (1518:1508:1500)
Nov 3 20:16:44 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:16:44 kernel: pppoe_ctf_xmit_validate: pkt len bigger then tunnel's MTU (1514:1504:1500)
Nov 3 20:16:44 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:16:48 conf_wan[288]: begin wan_conf
Nov 3 20:16:48 conf_wan[288]: CONFIG_ACTION_READ - start
Nov 3 20:16:49 conf_wan[300]: begin wan_conf
Nov 3 20:16:49 conf_wan[300]: CONFIG_ACTION_READ - start
Nov 3 20:16:50 conf_wan[324]: begin wan_conf
Nov 3 20:16:50 conf_wan[324]: CONFIG_ACTION_READ - start
Nov 3 20:16:50 conf_wan[332]: begin wan_conf
Nov 3 20:16:50 conf_wan[332]: CONFIG_ACTION_READ - start
Nov 3 20:16:51 resident: getting wan port status
Nov 3 20:16:51 conf_wan[335]: begin wan_conf
Nov 3 20:16:51 conf_wan[335]: CONFIG_ACTION_READ - start
Nov 3 20:16:51 conf_wan[342]: begin wan_conf
Nov 3 20:16:51 conf_wan[342]: CONFIG_ACTION_READ - start
Nov 3 20:16:54 conf_wan[346]: begin wan_conf
Nov 3 20:16:54 conf_wan[346]: CONFIG_ACTION_READ - start
Nov 3 20:16:54 resident: getting wan port status
Nov 3 20:16:57 conf_wan[354]: begin wan_conf
Nov 3 20:16:57 conf_wan[354]: CONFIG_ACTION_READ - start
Nov 3 20:16:57 resident: getting wan port status
Nov 3 20:17:00 conf_wan[362]: begin wan_conf
Nov 3 20:17:00 conf_wan[362]: CONFIG_ACTION_READ - start
Nov 3 20:17:00 resident: getting wan port status
Nov 3 20:17:03 conf_wan[370]: begin wan_conf
Nov 3 20:17:03 conf_wan[370]: CONFIG_ACTION_READ - start
Nov 3 20:17:03 resident: getting wan port status
Nov 3 20:17:06 conf_wan[378]: begin wan_conf
Nov 3 20:17:06 conf_wan[378]: CONFIG_ACTION_READ - start
Nov 3 20:17:06 resident: getting wan port status
Nov 3 20:17:09 conf_wan[386]: begin wan_conf
Nov 3 20:17:09 conf_wan[386]: CONFIG_ACTION_READ - start
Nov 3 20:17:10 resident: getting wan port status
Nov 3 20:17:11 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:17:11 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[56742]->[173.194.69.125]:[443]
Nov 3 20:17:11 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[56742]-[173.194.69.125]:[443]
Nov 3 20:17:11 kernel: CTF_INFO: assoc tunnel:8145f800 proto:00
Nov 3 20:17:13 conf_wan[394]: begin wan_conf
Nov 3 20:17:13 conf_wan[394]: CONFIG_ACTION_READ - start
Nov 3 20:17:13 resident: getting wan port status
Nov 3 20:17:13 dnsmasq-dhcp[257]: DHCPREQUEST(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 3 20:17:13 dnsmasq-dhcp[257]: DHCPACK(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 3 20:17:16 conf_wan[402]: begin wan_conf
Nov 3 20:17:16 conf_wan[402]: CONFIG_ACTION_READ - start
Nov 3 20:17:16 resident: getting wan port status
Nov 3 20:17:19 conf_wan[410]: begin wan_conf
Nov 3 20:17:19 conf_wan[410]: CONFIG_ACTION_READ - start
Nov 3 20:17:19 resident: getting wan port status
Nov 3 20:17:22 conf_wan[418]: begin wan_conf
Nov 3 20:17:22 conf_wan[418]: CONFIG_ACTION_READ - start
Nov 3 20:17:22 resident: getting wan port status
Nov 3 20:17:25 conf_wan[426]: begin wan_conf
Nov 3 20:17:25 conf_wan[426]: CONFIG_ACTION_READ - start
Nov 3 20:17:25 resident: getting wan port status
Nov 3 20:17:28 conf_wan[434]: begin wan_conf
Nov 3 20:17:28 conf_wan[434]: CONFIG_ACTION_READ - start
Nov 3 20:17:28 resident: getting wan port status
Nov 3 20:17:31 conf_wan[442]: begin wan_conf
Nov 3 20:17:31 conf_wan[442]: CONFIG_ACTION_READ - start
Nov 3 20:17:31 resident: getting wan port status
Nov 3 20:17:35 conf_wan[450]: begin wan_conf
Nov 3 20:17:35 conf_wan[450]: CONFIG_ACTION_READ - start
Nov 3 20:17:35 resident: getting wan port status
Nov 3 20:17:38 conf_wan[458]: begin wan_conf
Nov 3 20:17:38 conf_wan[458]: CONFIG_ACTION_READ - start
Nov 3 20:17:38 resident: getting wan port status
Nov 3 20:17:41 conf_wan[466]: begin wan_conf
Nov 3 20:17:41 conf_wan[466]: CONFIG_ACTION_READ - start
Nov 3 20:17:41 resident: getting wan port status
Nov 3 20:17:44 conf_wan[474]: begin wan_conf
Nov 3 20:17:44 conf_wan[474]: CONFIG_ACTION_READ - start
Nov 3 20:17:44 resident: getting wan port status
Nov 3 20:17:47 conf_wan[482]: begin wan_conf
Nov 3 20:17:47 conf_wan[482]: CONFIG_ACTION_READ - start
Nov 3 20:17:47 resident: getting wan port status
Nov 3 20:17:50 conf_wan[490]: begin wan_conf
Nov 3 20:17:50 conf_wan[490]: CONFIG_ACTION_READ - start
Nov 3 20:17:50 resident: getting wan port status
Nov 3 20:17:53 conf_wan[498]: begin wan_conf
Nov 3 20:17:53 conf_wan[498]: CONFIG_ACTION_READ - start
Nov 3 20:17:53 resident: getting wan port status
Nov 3 20:17:57 conf_wan[506]: begin wan_conf
Nov 3 20:17:57 conf_wan[506]: CONFIG_ACTION_READ - start
Nov 3 20:17:57 resident: getting wan port status
Nov 3 20:18:00 conf_wan[514]: begin wan_conf
Nov 3 20:18:00 conf_wan[514]: CONFIG_ACTION_READ - start
Nov 3 20:18:00 resident: getting wan port status
Nov 3 20:18:03 conf_wan[522]: begin wan_conf
Nov 3 20:18:03 conf_wan[522]: CONFIG_ACTION_READ - start
Nov 3 20:18:03 resident: getting wan port status
Nov 3 20:18:06 conf_wan[530]: begin wan_conf
Nov 3 20:18:06 conf_wan[530]: CONFIG_ACTION_READ - start
Nov 3 20:18:06 resident: getting wan port status
Nov 3 20:18:11 conf_wan[538]: begin wan_conf
Nov 3 20:18:11 conf_wan[538]: CONFIG_ACTION_READ - start
Nov 3 20:18:11 conf_wan[544]: begin wan_conf
Nov 3 20:18:11 conf_wan[544]: CONFIG_ACTION_READ - start
Nov 3 20:18:12 conf_wan[549]: begin wan_conf
Nov 3 20:18:12 conf_wan[549]: CONFIG_ACTION_READ - start
Nov 3 20:18:12 conf_wan[552]: begin wan_conf
Nov 3 20:18:12 conf_wan[552]: CONFIG_ACTION_READ - start
Nov 3 20:18:13 conf_wan[556]: begin wan_conf
Nov 3 20:18:13 conf_wan[556]: CONFIG_ACTION_READ - start


Аварийная работа 1 :
Скрытый текст: показать
3 kernel: printk: 114 messages suppressed.
Nov 3 20:07:03 kernel: ip_forward(): Argh! Destination lost!
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[87.121.243.100]:[9623]->[31.192.130.213]:[62112]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[ppp0] proto=[17] ip=[100.100.100.1]:[62112]->[78.162.6.237]:[18410]
Nov 3 20:07:03 kernel: _ctf_pppox_assoc_tunnel: found ipc:[17]-[100.100.100.1]:[62112]-[78.162.6.237]:[18410]
Nov 3 20:07:03 kernel: CTF_INFO: assoc tunnel:81a60800 proto:00
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[ppp0] proto=[17] ip=[100.100.100.1]:[62112]->[178.206.173.39]:[6881]
Nov 3 20:07:03 kernel: _ctf_pppox_assoc_tunnel: found ipc:[17]-[100.100.100.1]:[62112]-[178.206.173.39]:[6881]
Nov 3 20:07:03 kernel: CTF_INFO: assoc tunnel:81a60800 proto:00
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[178.164.195.129]:[33570]->[31.192.130.213]:[62112]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[95.221.51.56]:[59336]->[31.192.130.213]:[62112]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[178.204.151.77]:[6881]->[31.192.130.213]:[62112]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[84.112.183.102]:[6881]->[31.192.130.213]:[62112]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[84.2.9.51]:[6881]->[31.192.130.213]:[62112]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[6] ip=[212.1.118.22]:[32048]->[31.192.130.213]:[55737]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[108.173.181.69]:[11373]->[31.192.130.213]:[62112]
Nov 3 20:07:03 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:03 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[82.209.160.162]:[18700]->[31.192.130.213]:[62112]
Nov 3 20:07:04 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:04 kernel: CTF_INFO: txif=[eth0] proto=[17] ip=[109.14.245.197]:[49470]->[31.192.130.213]:[62112]
Nov 3 20:07:04 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:04 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[62112]->[109.111.148.194]:[4760]
Nov 3 20:07:04 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[62112]-[109.111.148.194]:[4760]
Nov 3 20:07:04 kernel: CTF_INFO: assoc tunnel:81a60800 proto:00
Nov 3 20:07:04 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:04 kernel: CTF_INFO: txif=[eth0] proto=[6] ip=[109.111.148.194]:[4760]->[31.192.130.213]:[62112]
Nov 3 20:07:04 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 3 20:07:04 kernel: CTF_INFO: txif=[eth0] proto=[6] ip=[212.1.118.22]:[32048]->[31.192.130.213]:[55737]
Nov 3 20:07:04 pppd[1108]: LCP terminated by peer
Nov 3 20:07:04 pppd[1108]: Connect time 776.9 minutes.
Nov 3 20:07:04 pppd[1108]: Sent 596302793 bytes, received 14355730 bytes.
Nov 3 20:07:04 pppd[1108]: Down ppp with status (0)0
Nov 3 20:07:04 event: ppp_down - do event
Nov 3 20:07:04 resident_ppp_handler: record = action:down;iface:ppp0;link:wan1_2;status:0;
Nov 3 20:07:04 resident: resident_ipoe_handler - Set default type: ipv4
Nov 3 20:07:04 resident: resident_ppp_handler - l2:wan1, l3:wan1_2, tun:
Nov 3 20:07:04 ppp_handler: ppp state 0
Nov 3 20:07:04 ppp_handler: Restart pppd
Nov 3 20:07:04 resident: start pppd on wan1_2
Nov 3 20:07:04 resident: stop pppd on wan1_2
Nov 3 20:07:04 resident: set lock on wan1_2, with "/var/lock/wan1_2.lock"
Nov 3 20:07:04 pppd[1108]: Terminating on signal 15
Nov 3 20:07:04 pppd[1108]: lcp_close: unit:0, reason: "User request" (status: 5, state: 5, was_ip_down: 1)
Nov 3 20:07:04 resident: stopped link(contype:ppp, iface:wan1_2)
Nov 3 20:07:04 pppd[1292]: Plugin /usr/lib/pppd/rp-pppoe.so loaded.
Nov 3 20:07:04 pppd[1295]: pppd 2.4.4 started by admin, uid 0
Nov 3 20:07:04 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:04 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:04 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:04 pppd[1295]: PPP session is 13100
Nov 3 20:07:04 pppd[1295]: Couldn't allocate PPP unit 0 as it is already in use
Nov 3 20:07:04 pppd[1295]: Using interface ppp1
Nov 3 20:07:04 pppd[1295]: Connect: ppp1 <--> wan1
Nov 3 20:07:04 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:04 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:04 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:04 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:04 pppd[1295]: CHAP authentication succeeded: Welcome to TIS Dialog
Nov 3 20:07:04 pppd[1295]: CHAP authentication succeeded
Nov 3 20:07:04 pppd[1295]: peer from calling number 00:50:C2:7F:C6:95 authorized
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 pppd[1295]: local IP address 109.111.137.71
Nov 3 20:07:05 pppd[1295]: remote IP address 83.219.128.0
Nov 3 20:07:05 pppd[1295]: primary DNS address 83.219.128.10
Nov 3 20:07:05 pppd[1295]: secondary DNS address 83.219.128.14
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 resident_ppp_handler: record = action:up;iface:ppp1;link:wan1_2;ipaddr:109.111.137.71;netmask:255.255.255.255;gateway:83.219.128.0;dns1:83.219.128.10;dns2:83.219.128.14;
Nov 3 20:07:05 resident: resident_ipoe_handler - Set default type: ipv4
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:05 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:06 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:06 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:06 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:06 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:06 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:06 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:06 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:07 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:07 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:07 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 3 20:07:07 resident: resident_ppp_handler - l2:wan1, l3:wan1_2, tun:
Nov 3 20:07:07 pppd[1108]: Connection terminated.
Nov 3 20:07:07 resident: update dns
Nov 3 20:07:07 dnsmasq[252]: read /tmp/hosts - 2 addresses
Nov 3 20:07:07 dnsmasq-dhcp[252]: read /etc/ethers - 3 addresses
Nov 3 20:07:07 resident: update ntpclient
Nov 3 20:07:07 pppd[1108]: Sent PADT
Nov 3 20:07:07 dnsmasq[252]: using nameserver 83.219.128.14#53
Nov 3 20:07:07 dnsmasq[252]: using nameserver 83.219.128.10#53
Nov 3 20:07:07 pppd[1108]: Modem hangup
Nov 3 20:07:07 pppd[1108]: lcp_close: unit:0, reason: "" (status: 16, state: 0, was_ip_down: 1)
Nov 3 20:07:07 pppd[1108]: Exit.(16)
Nov 3 20:07:12 dnsmasq-dhcp[252]: DHCPREQUEST(br0) 100.100.100.1 00:13:d4:b8:50:2e
Nov 3 20:07:12 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.1 00:13:d4:b8:50:2e Andrey
Nov 3 20:07:13 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Nov 3 20:07:13 kernel: Call Trace:
Nov 3 20:07:13 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Nov 3 20:07:13 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Nov 3 20:07:13 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Nov 3 20:07:13 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Nov 3 20:07:13 kernel: Failed to add MFDB entry for 0 81e33000
Nov 3 20:09:11 dnsmasq-dhcp[252]: DHCPINFORM(br0) 100.100.100.1 00:13:d4:b8:50:2e
Nov 3 20:09:11 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.1 00:13:d4:b8:50:2e Andrey
Nov 3 20:12:23 conf_wan[1353]: begin wan_conf
Nov 3 20:12:23 conf_wan[1353]: CONFIG_ACTION_READ - start
Nov 3 20:12:25 conf_wan[1378]: begin wan_conf
Nov 3 20:12:25 conf_wan[1378]: CONFIG_ACTION_READ - start
Nov 3 20:12:25 conf_wan[1381]: begin wan_conf
Nov 3 20:12:25 conf_wan[1381]: CONFIG_ACTION_READ - start
Nov 3 20:12:33 conf_wan[1385]: begin wan_conf
Nov 3 20:12:33 conf_wan[1385]: CONFIG_ACTION_READ - start
Nov 3 20:12:33 conf_wan[1394]: begin wan_conf
Nov 3 20:12:33 conf_wan[1394]: CONFIG_ACTION_READ - start
Nov 3 20:12:34 conf_wan[1421]: begin wan_conf
Nov 3 20:12:34 conf_wan[1421]: CONFIG_ACTION_READ - start
Nov 3 20:12:35 conf_wan[1432]: begin wan_conf
Nov 3 20:12:35 conf_wan[1432]: CONFIG_ACTION_READ - start
Nov 3 20:12:35 conf_wan[1449]: begin wan_conf
Nov 3 20:12:35 conf_wan[1449]: CONFIG_ACTION_READ - start
Nov 3 20:12:35 resident: getting wan port status
Nov 3 20:12:35 conf_wan[1457]: begin wan_conf
Nov 3 20:12:35 conf_wan[1457]: CONFIG_ACTION_READ - start
Nov 3 20:12:40 conf_wan[1465]: begin wan_conf
Nov 3 20:12:40 conf_wan[1465]: CONFIG_ACTION_READ - start
Nov 3 20:12:40 conf_wan[1471]: begin wan_conf
Nov 3 20:12:40 conf_wan[1471]: CONFIG_ACTION_READ - start
Nov 3 20:12:40 conf_wan[1475]: begin wan_conf
Nov 3 20:12:40 conf_wan[1475]: CONFIG_ACTION_READ - start
Nov 3 20:12:40 conf_wan[1480]: begin wan_conf
Nov 3 20:12:40 conf_wan[1480]: CONFIG_ACTION_READ - start
Nov 3 20:12:42 conf_wan[1484]: begin wan_conf
Nov 3 20:12:42 conf_wan[1484]: CONFIG_ACTION_READ - start
nd ipc:[6]-[100.100.100.1]:[55716]-[109.161.116.127]:[59990]

Аварийная работа 2 :
Скрытый текст: показать
.1]:[64028]->[88.212.196.122]:[80]
Nov 5 04:49:27 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64028]-[88.212.196.122]:[80]
Nov 5 04:49:27 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:49:28 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:49:28 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64029]->[88.212.196.122]:[80]
Nov 5 04:49:28 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64029]-[88.212.196.122]:[80]
Nov 5 04:49:28 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:49:29 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:49:29 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64030]->[87.240.142.228]:[80]
Nov 5 04:49:29 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64030]-[87.240.142.228]:[80]
Nov 5 04:49:29 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:49:29 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:49:29 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64031]->[87.240.142.228]:[80]
Nov 5 04:49:29 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64031]-[87.240.142.228]:[80]
Nov 5 04:49:29 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:49:32 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 04:50:29 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:50:29 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64032]->[87.240.134.165]:[80]
Nov 5 04:50:29 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64032]-[87.240.134.165]:[80]
Nov 5 04:50:29 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:50:43 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:50:43 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64033]->[87.240.179.39]:[80]
Nov 5 04:50:43 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64033]-[87.240.179.39]:[80]
Nov 5 04:50:43 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:51:36 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:51:36 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64034]->[87.240.131.102]:[80]
Nov 5 04:51:36 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64034]-[87.240.131.102]:[80]
Nov 5 04:51:36 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:51:48 kernel: pppoe_ctf_xmit_validate: pkt len bigger then tunnel's MTU (1518:1508:1500)
Nov 5 04:51:48 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 5 04:53:23 dnsmasq-dhcp[252]: DHCPREQUEST(br0) 100.100.100.1 00:13:d4:b8:50:2e
Nov 5 04:53:23 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.1 00:13:d4:b8:50:2e Andrey
Nov 5 04:53:23 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Nov 5 04:53:23 kernel: Call Trace:
Nov 5 04:53:23 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Nov 5 04:53:23 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Nov 5 04:53:23 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Nov 5 04:53:23 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Nov 5 04:53:23 kernel: Failed to add MFDB entry for 0 81e33000
Nov 5 04:54:24 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:24 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64036]->[88.212.196.105]:[80]
Nov 5 04:54:24 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64036]-[88.212.196.105]:[80]
Nov 5 04:54:24 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:26 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:26 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64037]->[88.212.196.105]:[80]
Nov 5 04:54:26 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64037]-[88.212.196.105]:[80]
Nov 5 04:54:26 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:26 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:26 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64038]->[87.240.155.232]:[80]
Nov 5 04:54:26 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64038]-[87.240.155.232]:[80]
Nov 5 04:54:26 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:27 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:27 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64039]->[87.240.134.55]:[80]
Nov 5 04:54:27 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64039]-[87.240.134.55]:[80]
Nov 5 04:54:27 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:29 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:29 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64040]->[88.212.196.105]:[80]
Nov 5 04:54:29 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64040]-[88.212.196.105]:[80]
Nov 5 04:54:29 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:32 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:32 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64041]->[88.212.196.105]:[80]
Nov 5 04:54:32 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64041]-[88.212.196.105]:[80]
Nov 5 04:54:32 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:32 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:32 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64042]->[87.240.129.108]:[80]
Nov 5 04:54:32 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64042]-[87.240.129.108]:[80]
Nov 5 04:54:32 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:36 kernel: pppoe_ctf_xmit_validate: pkt len bigger then tunnel's MTU (1518:1508:1500)
Nov 5 04:54:36 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 5 04:54:37 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:37 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64044]->[87.240.129.108]:[80]
Nov 5 04:54:37 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64044]-[87.240.129.108]:[80]
Nov 5 04:54:37 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:38 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:38 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64045]->[88.212.196.105]:[80]
Nov 5 04:54:38 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64045]-[88.212.196.105]:[80]
Nov 5 04:54:38 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:45 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:45 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64046]->[74.125.232.63]:[80]
Nov 5 04:54:45 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64046]-[74.125.232.63]:[80]
Nov 5 04:54:45 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:45 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:45 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64047]->[74.125.232.63]:[80]
Nov 5 04:54:45 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64047]-[74.125.232.63]:[80]
Nov 5 04:54:45 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:45 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:45 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64048]->[74.125.232.63]:[443]
Nov 5 04:54:45 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64048]-[74.125.232.63]:[443]
Nov 5 04:54:45 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:45 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:54:45 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64049]->[173.194.35.239]:[443]
Nov 5 04:54:45 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64049]-[173.194.35.239]:[443]
Nov 5 04:54:45 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:54:45 kernel: pppoe_ctf_xmit_validate: pkt len bigger then tunnel's MTU (1518:1508:1500)
Nov 5 04:54:45 kernel: ctf_pppoe_xmit: _ctf_pppoe_xmit_validate faild, go to slow path
Nov 5 04:55:35 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:55:35 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64050]->[74.125.232.63]:[80]
Nov 5 04:55:35 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64050]-[74.125.232.63]:[80]
Nov 5 04:55:35 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:55:35 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:55:35 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64051]->[173.194.35.239]:[443]
Nov 5 04:55:35 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64051]-[173.194.35.239]:[443]
Nov 5 04:55:35 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:55:48 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:55:48 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64052]->[87.240.131.103]:[80]
Nov 5 04:55:48 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64052]-[87.240.131.103]:[80]
Nov 5 04:55:48 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:55:58 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:55:58 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64053]->[87.240.143.243]:[443]
Nov 5 04:55:58 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64053]-[87.240.143.243]:[443]
Nov 5 04:55:58 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:55:59 kernel: CTF_INFO: ip_conntrack_ipct_add: Adding ipc entry:
Nov 5 04:55:59 kernel: CTF_INFO: txif=[ppp0] proto=[6] ip=[100.100.100.1]:[64054]->[88.212.196.122]:[80]
Nov 5 04:55:59 kernel: _ctf_pppox_assoc_tunnel: found ipc:[6]-[100.100.100.1]:[64054]-[88.212.196.122]:[80]
Nov 5 04:55:59 kernel: CTF_INFO: assoc tunnel:818af600 proto:00
Nov 5 04:56:54 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Nov 5 04:56:54 kernel: Call Trace:
Nov 5 04:56:54 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Nov 5 04:56:54 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Nov 5 04:56:54 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Nov 5 04:56:54 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Nov 5 04:56:54 kernel: Failed to add MFDB entry for 0 81e33000
Nov 5 04:56:54 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Nov 5 04:56:54 kernel: Call Trace:
Nov 5 04:56:54 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Nov 5 04:56:54 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Nov 5 04:56:54 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Nov 5 04:56:54 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Nov 5 04:56:54 kernel: Failed to add MFDB entry for 0 81e33000
Nov 5 04:57:12 kernel: Link status change phy 3
Nov 5 04:57:12 resident_phy_link_handler: phy - 3, status - 0
Nov 5 04:57:14 kernel: Link status change phy 3
Nov 5 04:57:14 resident_phy_link_handler: phy - 3, status - 1
Nov 5 05:04:41 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 05:19:49 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 05:34:58 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 06:05:09 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 06:05:09 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: channel 6 used by exiting BSSs
Nov 5 06:20:10 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 06:35:13 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 06:50:14 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 07:04:04 pppd[215]: LCP terminated by peer
Nov 5 07:04:04 pppd[215]: Connect time 440.0 minutes.
Nov 5 07:04:04 pppd[215]: Sent 46827206 bytes, received 132491290 bytes.
Nov 5 07:04:04 pppd[215]: Down ppp with status (0)0
Nov 5 07:04:04 event: ppp_down - do event
Nov 5 07:04:04 resident_ppp_handler: record = action:down;iface:ppp0;link:wan1_2;status:0;
Nov 5 07:04:04 resident: resident_ipoe_handler - Set default type: ipv4
Nov 5 07:04:04 resident: resident_ppp_handler - l2:wan1, l3:wan1_2, tun:
Nov 5 07:04:04 ppp_handler: ppp state 0
Nov 5 07:04:04 ppp_handler: Restart pppd
Nov 5 07:04:04 resident: start pppd on wan1_2
Nov 5 07:04:04 resident: stop pppd on wan1_2
Nov 5 07:04:04 resident: set lock on wan1_2, with "/var/lock/wan1_2.lock"
Nov 5 07:04:04 pppd[215]: Terminating on signal 15
Nov 5 07:04:04 pppd[215]: lcp_close: unit:0, reason: "User request" (status: 5, state: 5, was_ip_down: 1)
Nov 5 07:04:05 pppd[513]: PPP session is 14559
Nov 5 07:04:05 pppd[513]: Couldn't allocate PPP unit 0 as it is already in use
Nov 5 07:04:05 pppd[513]: Using interface ppp1
Nov 5 07:04:05 pppd[513]: Connect: ppp1 <--> wan1
Nov 5 07:04:05 pppd[513]: CHAP authentication succeeded: Welcome to TIS Dialog
Nov 5 07:04:05 pppd[513]: CHAP authentication succeeded
Nov 5 07:04:05 pppd[513]: peer from calling number 00:50:C2:7F:C6:9B authorized
Nov 5 07:04:05 pppd[513]: local IP address 31.192.137.150
Nov 5 07:04:05 pppd[513]: remote IP address 83.219.128.0
Nov 5 07:04:05 pppd[513]: primary DNS address 83.219.128.10
Nov 5 07:04:05 pppd[513]: secondary DNS address 83.219.128.14
Nov 5 07:04:05 resident_ppp_handler: record = action:up;iface:ppp1;link:wan1_2;ipaddr:31.192.137.150;netmask:255.255.255.255;gateway:83.219.128.0;dns1:83.219.128.10;dns2:83.219.128.14;
Nov 5 07:04:05 resident: resident_ipoe_handler - Set default type: ipv4
Nov 5 07:04:07 pppd[215]: Connection terminated.
Nov 5 07:04:07 pppd[215]: Sent PADT
Nov 5 07:04:07 pppd[215]: Modem hangup
Nov 5 07:04:07 pppd[215]: lcp_close: unit:0, reason: "" (status: 16, state: 0, was_ip_down: 1)
Nov 5 07:04:07 pppd[215]: Exit.(16)
Nov 5 07:04:07 resident: resident_ppp_handler - l2:wan1, l3:wan1_2, tun:
Nov 5 07:04:07 resident: update dns
Nov 5 07:04:07 dnsmasq[252]: read /tmp/hosts - 2 addresses
Nov 5 07:04:07 dnsmasq-dhcp[252]: read /etc/ethers - 3 addresses
Nov 5 07:04:07 dnsmasq[252]: using nameserver 83.219.128.14#53
Nov 5 07:04:07 dnsmasq[252]: using nameserver 83.219.128.10#53
Nov 5 07:04:07 resident: update ntpclient
Nov 5 07:05:16 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 07:20:18 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 07:35:21 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 07:50:23 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 07:50:23 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: channel 6 used by exiting BSSs
Nov 5 08:05:25 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 08:20:27 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 08:35:29 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 08:50:31 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 09:05:33 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 09:20:35 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 09:35:37 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 09:50:39 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 10:05:41 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 10:20:44 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 10:35:46 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 10:50:48 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 10:55:32 kernel: pppoe_ctf_rcv_classify: *** FAIL. no such session.
Nov 5 10:55:32 kernel: sid=2930 smac=0:50:c2:7f:c6:9b
Nov 5 10:55:33 kernel: pppoe_ctf_rcv_classify: *** FAIL. no such session.
Nov 5 10:55:33 kernel: sid=2930 smac=0:50:c2:7f:c6:9b
Nov 5 10:55:33 kernel: pppoe_ctf_rcv_classify: *** FAIL. no such session.
Nov 5 10:55:33 kernel: sid=2930 smac=0:50:c2:7f:c6:9b
Nov 5 11:05:50 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 11:20:52 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 11:35:54 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 11:50:56 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 12:21:00 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 12:36:02 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 12:50:53 kernel: Link status change phy 2
Nov 5 12:50:53 resident_phy_link_handler: phy - 2, status - 1
Nov 5 12:50:55 dnsmasq-dhcp[252]: DHCPDISCOVER(br0) 00:0a:d8:01:a8:ea
Nov 5 12:50:55 dnsmasq-dhcp[252]: DHCPOFFER(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 12:50:55 dnsmasq-dhcp[252]: DHCPREQUEST(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 12:50:55 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 12:51:04 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 13:02:35 dnsmasq-dhcp[252]: DHCPREQUEST(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 13:02:35 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 13:06:06 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 6 used by exiting BSSs
Nov 5 13:12:07 kernel: pppoe_ctf_rcv_classify: *** FAIL. no such session.
Nov 5 13:12:07 kernel: sid=e309 smac=0:50:c2:7f:c6:9b
Nov 5 13:12:37 kernel: pppoe_ctf_rcv_classify: *** FAIL. no such session.
Nov 5 13:12:37 kernel: sid=e309 smac=0:50:c2:7f:c6:9b
Nov 5 13:14:15 dnsmasq-dhcp[252]: DHCPREQUEST(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 13:14:15 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 13:21:08 kernel: COEX: downgraded chanspec 0x2e0b to 0x2b0d: channel 11 used by exiting BSSs
Nov 5 13:25:28 kernel: Link status change phy 3
Nov 5 13:25:28 resident_phy_link_handler: phy - 3, status - 0
Nov 5 13:25:31 kernel: Link status change phy 3
Nov 5 13:25:31 resident_phy_link_handler: phy - 3, status - 1
Nov 5 13:25:40 dnsmasq-dhcp[252]: DHCPDISCOVER(br0) 00:13:d4:b8:50:2e
Nov 5 13:25:40 dnsmasq-dhcp[252]: DHCPOFFER(br0) 100.100.100.1 00:13:d4:b8:50:2e
Nov 5 13:25:40 dnsmasq-dhcp[252]: DHCPREQUEST(br0) 100.100.100.1 00:13:d4:b8:50:2e
Nov 5 13:25:40 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.1 00:13:d4:b8:50:2e Andrey
Nov 5 13:25:41 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Nov 5 13:25:41 kernel: Call Trace:
Nov 5 13:25:41 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Nov 5 13:25:41 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Nov 5 13:25:41 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Nov 5 13:25:41 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Nov 5 13:25:41 kernel: Failed to add MFDB entry for 0 81e33000
Nov 5 13:25:49 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Nov 5 13:25:49 kernel: Call Trace:
Nov 5 13:25:49 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Nov 5 13:25:49 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Nov 5 13:25:49 kernel: [<c00b6808>] igsc_sdb_member_add+0x284/0x3d0 [igs]
Nov 5 13:25:49 kernel: [<c00b5724>] igsc_stats_get+0x238/0x268 [igs]
Nov 5 13:25:49 kernel: Failed to add MFDB entry for 0 81e33000
Nov 5 13:25:49 kernel: dlink: emfc_mfdb_membership_add: mgrp_ip is zero, stack:
Nov 5 13:25:49 kernel: Call Trace:
Nov 5 13:25:49 kernel: [<8000f2ac>] dump_stack+0x8/0x34
Nov 5 13:25:49 kernel: [<c00af0e8>] emfc_mfdb_membership_add+0xc4/0x264 [emf]
Nov 5 13:25:55 dnsmasq-dhcp[252]: DHCPREQUEST(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 13:25:55 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.3 00:0a:d8:01:a8:ea
Nov 5 13:26:01 dnsmasq-dhcp[252]: DHCPINFORM(br0) 100.100.100.1 00:13:d4:b8:50:2e
Nov 5 13:26:01 dnsmasq-dhcp[252]: DHCPACK(br0) 100.100.100.1 00:13:d4:b8:50:2e Andrey
Nov 5 13:27:57 conf_wan[625]: begin wan_conf
Nov 5 13:27:57 conf_wan[625]: CONFIG_ACTION_READ - start
Nov 5 13:27:59 conf_wan[650]: begin wan_conf
Nov 5 13:27:59 conf_wan[650]: CONFIG_ACTION_READ - start
Nov 5 13:27:59 conf_wan[653]: begin wan_conf
Nov 5 13:27:59 conf_wan[653]: CONFIG_ACTION_READ - start
Nov 5 13:28:17 conf_wan[657]: begin wan_conf
Nov 5 13:28:17 conf_wan[657]: CONFIG_ACTION_READ - start
Nov 5 13:28:17 conf_wan[668]: begin wan_conf
Nov 5 13:28:17 conf_wan[668]: CONFIG_ACTION_READ - start
Nov 5 13:28:18 conf_wan[693]: begin wan_conf
Nov 5 13:28:18 conf_wan[693]: CONFIG_ACTION_READ - start
Nov 5 13:28:19 conf_wan[711]: begin wan_conf
Nov 5 13:28:19 conf_wan[711]: CONFIG_ACTION_READ - start
Nov 5 13:28:19 conf_wan[718]: begin wan_conf
Nov 5 13:28:19 conf_wan[718]: CONFIG_ACTION_READ - start
Nov 5 13:28:19 resident: getting wan port status
Nov 5 13:28:19 conf_wan[726]: begin wan_conf
Nov 5 13:28:19 conf_wan[726]: CONFIG_ACTION_READ - start
Nov 5 13:28:23 conf_wan[730]: begin wan_conf
Nov 5 13:28:23 conf_wan[730]: CONFIG_ACTION_READ - start
Nov 5 13:28:23 resident: getting wan port status
Nov 5 13:28:26 conf_wan[738]: begin wan_conf
Nov 5 13:28:26 conf_wan[738]: CONFIG_ACTION_READ - start
Nov 5 13:28:26 resident: getting wan port status
Nov 5 13:28:33 conf_wan[747]: begin wan_conf
Nov 5 13:28:33 conf_wan[747]: CONFIG_ACTION_READ - start
Nov 5 13:28:34 conf_wan[755]: begin wan_conf
Nov 5 13:28:34 conf_wan[755]: CONFIG_ACTION_READ - start
Nov 5 13:28:34 conf_wan[759]: begin wan_conf
Nov 5 13:28:34 conf_wan[759]: CONFIG_ACTION_READ - start
Nov 5 13:28:34 conf_wan[764]: begin wan_conf
Nov 5 13:28:34 conf_wan[764]: CONFIG_ACTION_READ - start
Nov 5 13:28:39 conf_wan[768]: begin wan_conf
Nov 5 13:28:39 conf_wan[768]: CONFIG_ACTION_READ - start
: assoc tunnel:818af600 proto:00


думаю про откат на 1.0.5


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Пн ноя 05, 2012 15:10 
Не в сети

Зарегистрирован: Пт июл 13, 2012 11:02
Сообщений: 52
В целом работает, но иногда в роутере наступает какое-то пограничное состояние, при котором на 15 мегабитах вылетает вот такая картинка:
Изображение
При этом интернет мягко говоря странный, подтупливает и на 15-ку точно не тянет.
После ребута дира, показывает все как обычно:
Изображение


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Пн ноя 05, 2012 16:18 
Не в сети

Зарегистрирован: Вт апр 07, 2009 13:39
Сообщений: 12
На 10-ой версии через 24 часа не подымается PPPoE. Помогает или изменение ЛЮБОЙ кофигурации, неважно где именно, либо просто перезагрузка. Очень сильно бесит этот факт. На 9-ой версии все работало более чем стабильно.


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Пн ноя 05, 2012 18:14 
Не в сети

Зарегистрирован: Пн окт 08, 2012 17:56
Сообщений: 16
У меня на 15 Мегабитах такая картина:

Изображение

При этом приём и отдача одинакова, составляет 1,9 Мегабайта в секунду. На отдачу походу глюк самого интернетометра.
Слава Богу работает всё стабильно, инет не отваливается и не виснет, мучил сутками с нагрузкой торрентами.
PPTP+динамический IP

_________________
Изображение


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-615 Rev K1
СообщениеДобавлено: Пн ноя 05, 2012 18:25 
Не в сети

Зарегистрирован: Чт ноя 01, 2012 18:17
Сообщений: 6
а какая прошивка стоит?


Вернуться наверх
 Профиль  
 
Показать сообщения за:  Сортировать по:  
Начать новую тему Ответить на тему  [ Сообщений: 3071 ]  На страницу Пред.  1 ... 57, 58, 59, 60, 61, 62, 63 ... 205  След.

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


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

Сейчас этот форум просматривают: Google [Bot] и гости: 71


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

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