faq обучение настройка
Текущее время: Вс июл 06, 2025 10:53

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




Начать новую тему Ответить на тему  [ Сообщений: 5 ] 
Автор Сообщение
 Заголовок сообщения: Расшифровка логов роутеров
СообщениеДобавлено: Пн янв 28, 2013 17:36 
Не в сети

Зарегистрирован: Пн янв 28, 2013 16:25
Сообщений: 26
Добрый день.
в последнее время от абонентов поступает много жалоб на роутеры длинк. Модели dir-615 k2, dir-615 m, dir-300nru b7,dir-632
везде не забываем обновлять прошивки после обновления сброс.
В связи с этим есть несколько вопросов

1. Jan 1 00:01:57 kernel: Priletela cmd=0x89f3 - это dir-632 1.4.0
2. Jan 1 00:00:06 update_ipfilters: error in params -
Jan 1 02:05:48 igmpproxy[235]: The VIF Ix 65535 is out of range (0-32). Table insert failed.
Jan 1 02:06:07 igmpproxy[235]: The VIF Ix 65535 is out of range (0-32). Table insert failed.
Jan 1 02:06:40 igmpproxy[235]: The VIF Ix 65535 is out of range (0-32). Table insert failed.
Jan 1 02:06:57 igmpproxy[235]: The VIF Ix 65535 is out of range (0-32). Table insert failed.
Jan 1 02:07:26 igmpproxy[235]: The VIF Ix 65535 is out of range (0-32). Table insert failed.
Jan 1 02:07:55 igmpproxy[235]: The VIF Ix 65535 is out of range (0-32). Table insert failed.
Jan 1 02:08:11 igmpproxy[235]: The VIF Ix 65535 is out of range (0-32). Table insert failed.
это dir-615 m 1.05 помоему
3. Jan 28 15:06:59 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:00 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:00 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:01 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:03 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:05 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:05 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:06 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:08 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:08 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:09 syslog: impossible code point at /home/builder/10354/output/build/igmpx-igmpx/igmpx/route.c:igmpx_route_process_expires:386
Jan 28 15:07:10 kernel: ccmp_decap: Error: Big jump in pn number. TID=7, from 0 4c32 to 0 4c7d. Frame seq=0xf00a
Это тот же dir-632 только обновленный до 1.4.1

Что значат эти странные сообщения в логах ?


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: Расшифровка логов роутеров
СообщениеДобавлено: Вт янв 29, 2013 08:41 
Не в сети

Зарегистрирован: Пн апр 09, 2012 11:34
Сообщений: 54
Тоже хотел бы знать ответы на вопросы автора. Последние ревизии DIR-615 k1, k2, m и dir-300 NRU b7, dir-300 C1; не очень хорошо себя проявили в сетях местных провайдеров в независимости от типов подключений. Прошивки аналогично меняли до самый свежих с учетом сброса настроек до заводских.
И ещё вопрос, имеется ли где то информация о пропускной способности(производительности) этих устройств Lan-Wan при типах подключений Static ip, Dynamic ip, PPPoE, L2TP, PPtP?
Ранее такая таблица была для старых ревизий и моделей роутеров, сейчас для новых устройств её нет, а хотелось бы.


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: Расшифровка логов роутеров
СообщениеДобавлено: Вт янв 29, 2013 12:01 
Не в сети

Зарегистрирован: Пн янв 28, 2013 16:25
Сообщений: 26
Вот свежий лог роутера dir-300 nru b7
Приехал на место помотрел сам
подвисший dhcp и компьютер клиента и мой компьютер не получают айпи адреса как по вайфай так и вручную.
прописал в ручную, зашел на роутер, прописал ntp, кстати непонятно почему оно по умолчанию выключено, изменил время аренды dhcp и период обновления ключа шифрования на 12 мин. так как на dir-632 при времени аренды 1440 минут на роутере на клиенте время аренды стояло все равно 1 час, нажал на кнопку сохранить и перезагрузить и о чудо - заработало
логи прилагаю
Jan 1 00:00:11 syslogd started: BusyBox v1.19.2
Jan 1 00:00:11 resident: init lan
Jan 1 00:00:11 resident: start ipoe
Jan 1 00:00:11 start_ip: begin (br0 -> br0)
Jan 1 00:00:11 resident: start ipoe (v717915328) on br0
Jan 1 00:00:12 resident: init wan
Jan 1 00:00:12 kernel: [17179582.556000] AP SETKEYS DONE - WPA2, AuthMode(7)=WPA2PSK, WepStatus(6)=AES, GroupWepStatus(6)=AES
Jan 1 00:00:12 kernel: [17179582.556000]
Jan 1 00:00:12 kernel: [17179582.560000] Rcv Wcid(1) AddBAReq
Jan 1 00:00:12 kernel: [17179582.564000] Start Seq = 00000000
Jan 1 00:00:12 kernel: [17179582.568000] eth2.5: Setting MAC address to 90 94 e4 37 b2 e5.
Jan 1 00:00:12 resident: start ipoe
Jan 1 00:00:12 start_ip: begin (eth2.5 -> eth2.5_1)
Jan 1 00:00:12 resident: start ipoe (v717605132) on eth2.5
Jan 1 00:00:12 event: send event "ipoe down"
Jan 1 00:00:12 update_ddns: start
Jan 1 00:00:12 telnet-start: begin...
Jan 1 00:00:12 telnet-start: running on 23 port
Jan 1 00:00:12 telnet-start: succes!
Jan 1 00:00:12 resident: Out init_device
Jan 1 00:00:12 resident: record = action:up;iface:br0;contag:0;ipaddr:192.168.0.1;netmask:255.255.255.0;gateway:;dns1:;dns2:;
Jan 1 00:00:12 resident: phys_iface br0
Jan 1 00:00:12 test: ip_type = (null)
Jan 1 00:00:12 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:12 resident: phys_iface
Jan 1 00:00:12 resident: resident_ipoe_handler - 1
Jan 1 00:00:12 resident: resident_ipoe_handler - 3, name: br0
Jan 1 00:00:12 resident: resident_ipoe_handler - l2:br0, l3:br0, tun:, ip_type:0
Jan 1 00:00:12 resident: resident_ipoe_handler - ipv4
Jan 1 00:00:12 resident: start ip_is_up on iface br0
Jan 1 00:00:12 resident: ip_is_up for link br0
Jan 1 00:00:12 resident: start dhcp+dns on br0
Jan 1 00:00:12 upnp: start - begin
Jan 1 00:00:12 upnp: upnp disable - exit
Jan 1 00:00:12 dnsmasq[783]: started, version 2.63 cachesize 512
Jan 1 00:00:12 dnsmasq[783]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
Jan 1 00:00:12 dnsmasq-dhcp[783]: DHCP, IP range 192.168.0.2 -- 192.168.0.254, lease time 12m
Jan 1 00:00:12 dnsmasq[783]: read /tmp/hosts - 2 addresses
Jan 1 00:00:12 dnsmasq-dhcp[783]: read /etc/ethers - 0 addresses
Jan 1 00:00:12 resident: record = action:down;iface:eth2.5;contag:1;
Jan 1 00:00:12 resident: phys_iface eth2.5
Jan 1 00:00:12 test: ip_type = (null)
Jan 1 00:00:12 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:12 resident: phys_iface
Jan 1 00:00:12 resident: resident_ipoe_handler - 2
Jan 1 00:00:12 resident: resident_ipoe_handler - 3, name: eth2.5_1
Jan 1 00:00:12 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:, ip_type:0
Jan 1 00:00:12 resident: ip_is_down on eth2.5_1
Jan 1 00:00:12 event: send event "ipoe up"
Jan 1 00:00:12 resident: record = action:up;iface:eth2.5;contag:1;ipaddr:192.168.9.157 ;netmask:255.255.255.0 ;gateway:192.168.9.1 ;dns1:10.10.20.1;dns2:8.8.8.8;
Jan 1 00:00:12 resident: phys_iface eth2.5
Jan 1 00:00:12 test: ip_type = (null)
Jan 1 00:00:12 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:12 resident: phys_iface
Jan 1 00:00:12 resident: resident_ipoe_handler - 2
Jan 1 00:00:12 resident: resident_ipoe_handler - 3, name: eth2.5_1
Jan 1 00:00:12 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:, ip_type:0
Jan 1 00:00:12 resident: resident_ipoe_handler - ipv4
Jan 1 00:00:12 resident: start ip_is_up on iface eth2.5_1
Jan 1 00:00:12 resident: ip_is_up for link eth2.5_1
Jan 1 00:00:12 set_dhcp_routes: set routes for iface eth2.5
Jan 1 00:00:13 kernel: [17179583.284000] AP SETKEYS DONE - WPA2, AuthMode(7)=WPA2PSK, WepStatus(6)=AES, GroupWepStatus(6)=AES
Jan 1 00:00:13 kernel: [17179583.284000]
Jan 1 00:00:13 resident: update dns
Jan 1 00:00:13 dnsmasq[783]: read /tmp/hosts - 2 addresses
Jan 1 00:00:13 dnsmasq-dhcp[783]: read /etc/ethers - 0 addresses
Jan 1 00:00:13 dnsmasq[783]: using nameserver 8.8.8.8#53
Jan 1 00:00:13 dnsmasq[783]: using nameserver 10.10.20.1#53
Jan 1 00:00:13 resident: update rip
Jan 1 00:00:13 resident: update igmpx
Jan 1 00:00:13 resident: stop igmpx
Jan 1 00:00:13 kernel: [17179583.476000] MulticastFilterTableInsertEntry: already in Members list.
Jan 1 00:00:13 iface: this is eth2.5
Jan 1 00:00:13 resident: igmpx eth2.5
Jan 1 00:00:13 syslog: Loading liblogger v2.0.2
Jan 1 00:00:13 syslog: upstream ifaces: eth2.5
Jan 1 00:00:13 syslog: downstream ifaces: br0
Jan 1 00:00:13 syslog: hews interval = 120.0 sec
Jan 1 00:00:13 syslog: doublet join enabled
Jan 1 00:00:13 syslog: Using old argv style
Jan 1 00:00:13 syslog: daemonizing ...
Jan 1 00:00:13 syslog: kernel multicast version is 305 (v3.05 ?)
Jan 1 00:00:13 syslog: kernel mroute inited
Jan 1 00:00:13 syslog: proxy prepared
Jan 1 00:00:13 kernel: [17179583.632000] eth2.5: dev_set_allmulti(master, 1)
Jan 1 00:00:13 syslog: vifi #0 added for eth2.5
Jan 1 00:00:13 syslog: vifi #1 added for br0
Jan 1 00:00:13 syslog: valid VIF's configured: upstreams=1, downstreams=1. Ok.
Jan 1 00:00:13 resident: update igmpx compiled
Jan 1 00:00:13 resident: update ntpclient
Jan 1 02:00:14 kernel: [17179584.456000] MulticastFilterTableInsertEntry: already in Members list.
Jan 1 02:00:14 kernel: [17179584.460000] MulticastFilterTableInsertEntry: already in Members list.
Jan 1 02:00:14 kernel: [17179584.464000] MulticastFilterTableInsertEntry: already in Members list.
Jan 1 02:00:14 kernel: [17179584.468000] MulticastFilterTableInsertEntry: already in Members list.
Jan 1 02:00:16 kernel: [17179586.416000] MulticastFilterTableInsertEntry: already in Members list.
Jan 1 02:00:16 kernel: [17179586.420000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:00 kernel: [17179596.728000] br0: topology change detected, propagating
Jan 28 18:38:00 kernel: [17179596.732000] br0: port 5(ra0) entering forwarding state
Jan 28 18:38:00 kernel: [17179596.736000] br0: topology change detected, propagating
Jan 28 18:38:00 kernel: [17179596.740000] br0: port 4(eth2.1) entering forwarding state
Jan 28 18:38:00 kernel: [17179596.744000] br0: topology change detected, propagating
Jan 28 18:38:00 kernel: [17179596.748000] br0: port 3(eth2.2) entering forwarding state
Jan 28 18:38:00 kernel: [17179596.752000] br0: topology change detected, propagating
Jan 28 18:38:00 kernel: [17179596.756000] br0: port 2(eth2.3) entering forwarding state
Jan 28 18:38:00 kernel: [17179596.760000] br0: topology change detected, propagating
Jan 28 18:38:00 kernel: [17179596.764000] br0: port 1(eth2.4) entering forwarding state
Jan 28 18:38:05 dnsmasq-dhcp[783]: DHCPDISCOVER(br0) 20:68:9d:0c:8d:e0
Jan 28 18:38:05 dnsmasq-dhcp[783]: DHCPOFFER(br0) 192.168.0.224 20:68:9d:0c:8d:e0
Jan 28 18:38:05 dnsmasq-dhcp[783]: DHCPREQUEST(br0) 192.168.0.224 20:68:9d:0c:8d:e0
Jan 28 18:38:05 dnsmasq-dhcp[783]: DHCPACK(br0) 192.168.0.224 20:68:9d:0c:8d:e0 spark_pc
Jan 28 18:38:05 syslog: added membership for 239.255.255.250 on upstream #0 192.168.9.157
Jan 28 18:38:05 syslog: added new route 239.255.255.250: 192.168.9.157 -> 192.168.0.1
Jan 28 18:38:05 kernel: [17179601.328000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:05 kernel: [17179601.332000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:05 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.0.224
Jan 28 18:38:06 syslog: active route 239.255.255.250 changed source from 192.168.0.224 to 192.168.0.2
Jan 28 18:38:06 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.0.2
Jan 28 18:38:08 kernel: [17179604.216000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:08 kernel: [17179604.220000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:08 kernel: [17179604.224000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:08 kernel: [17179604.276000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:08 kernel: [17179604.280000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:09 kernel: [17179605.252000] MulticastFilterTableInsertEntry: already in Members list.
Jan 28 18:38:17 dnsmasq-dhcp[783]: DHCPDISCOVER(br0) 00:aa:70:9c:20:c4
Jan 28 18:38:17 dnsmasq-dhcp[783]: DHCPOFFER(br0) 192.168.0.4 00:aa:70:9c:20:c4
Jan 28 18:38:17 dnsmasq-dhcp[783]: DHCPREQUEST(br0) 192.168.0.4 00:aa:70:9c:20:c4
Jan 28 18:38:17 dnsmasq-dhcp[783]: DHCPACK(br0) 192.168.0.4 00:aa:70:9c:20:c4 android_465e821debd08e4e
Jan 28 18:38:20 kernel: [17179616.024000] Rcv Wcid(2) AddBAReq
Jan 28 18:38:20 kernel: [17179616.028000] Start Seq = 00000000
Jan 28 18:38:23 kernel: [17179619.644000] 20, flush one!
Jan 28 18:38:25 syslog: active route 239.255.255.250 changed source from 192.168.0.2 to 192.168.0.4
Jan 28 18:38:25 syslog: route 239.255.255.250 on upstream #0 activated with 192.168.0.4
Jan 28 18:39:00 kernel: [17179656.132000] b3, flush one!
Jan 28 18:39:00 kernel: [17179656.244000] b9, flush one!
Jan 28 18:41:35 kernel: [17179811.216000] 77a, flush one!
Jan 28 18:41:35 kernel: [17179811.716000] 77d, flush one!


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: Расшифровка логов роутеров
СообщениеДобавлено: Вт апр 01, 2014 14:16 
Не в сети

Зарегистрирован: Вт апр 01, 2014 13:32
Сообщений: 1
Добрый день.
Видимо похожая ситуация
(Dir-632, прошивка 2.0.2):

Jan 1 00:00:13 syslogd started: BusyBox v1.19.2
Jan 1 00:00:13 resident: init lan
Jan 1 00:00:13 resident: start ipoe
Jan 1 00:00:13 start_ip: begin (br0 -> br0)
Jan 1 00:00:13 resident: start ipoe (v718800224) on br0
Jan 1 00:00:13 update_ipfilters: error in params
Jan 1 00:00:14 resident: init wan
Jan 1 00:00:14 kernel: cmd=4
Jan 1 00:00:14 kernel: ag7240_ring_free Freeing at 0x81ab5000
Jan 1 00:00:14 kernel: ag7240_ring_free Freeing at 0x81877000
Jan 1 00:00:15 kernel: ag7240_ring_alloc Allocated 1280 at 0x81b47000
Jan 1 00:00:15 kernel: ag7240_ring_alloc Allocated 4032 at 0x81877000
Jan 1 00:00:15 kernel: Setting PHY...
Jan 1 00:00:15 resident: start ipoe
Jan 1 00:00:15 start_ip: begin (wan1 -> wan1_3)
Jan 1 00:00:15 resident: start ipoe (v717877316) on wan1
Jan 1 00:00:15 telnet-start: begin...
Jan 1 00:00:15 telnet-start: running on 23 port
Jan 1 00:00:15 telnet-start: succes!
Jan 1 00:00:15 printserver-start: begin...
Jan 1 00:00:15 printserver-start: success!
Jan 1 00:00:15 start_sysusers: init ...
Jan 1 00:00:15 start_sysusers: conf not NULL ...
Jan 1 00:00:15 kernel: cmd=2
Jan 1 00:00:15 kernel: cmd=10
Jan 1 00:00:15 kernel: GPIO resident_pid=747
Jan 1 00:00:15 resident: record = action:up;iface:br0;contag:0;ipaddr:10.0.0.1;netmask:255.0.0.0;gateway:;dns1:;dns2:;
Jan 1 00:00:15 resident: phys_iface br0
Jan 1 00:00:15 test: ip_type = (null)
Jan 1 00:00:15 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:15 resident: phys_iface
Jan 1 00:00:15 resident: resident_ipoe_handler - 1
Jan 1 00:00:15 resident: resident_ipoe_handler - 3, name: br0
Jan 1 00:00:15 kernel: Port Status c000004
Jan 1 00:00:15 kernel: ar7240-ehci ar7240-ehci.0: ATH EHCI
Jan 1 00:00:15 kernel: ar7240-ehci ar7240-ehci.0: new USB bus registered, assigned bus number 1
Jan 1 00:00:15 kernel: ar7240-ehci ar7240-ehci.0: irq 3, io mem 0x1b000000
Jan 1 00:00:15 kernel: hcc_params addr 0xbb000108 val 0x6 hcs_params addr 0xbb000104 val 0x10011
Jan 1 00:00:15 kernel: ar7240-ehci ar7240-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Jan 1 00:00:15 kernel: hub 1-0:1.0: USB hub found
Jan 1 00:00:15 kernel: hub 1-0:1.0: 1 port detected
Jan 1 00:00:15 resident: resident_ipoe_handler - l2:br0, l3:br0, tun:, ip_type:0
Jan 1 00:00:15 resident: resident_ipoe_handler - ipv4
Jan 1 00:00:15 resident: start ip_is_up on iface br0
Jan 1 00:00:15 resident: ip_is_up for link br0
Jan 1 00:00:15 kernel: br0: port 2(eth0.1) entering learning state
Jan 1 00:00:15 kernel: br0: port 1(ath0) entering learning state
Jan 1 00:00:15 kernel: br0: topology change detected, propagating
Jan 1 00:00:15 kernel: br0: port 2(eth0.1) entering forwarding state
Jan 1 00:00:15 kernel: br0: topology change detected, propagating
Jan 1 00:00:15 kernel: br0: port 1(ath0) entering forwarding state
Jan 1 00:00:15 resident: start dhcp+dns on br0
Jan 1 00:00:15 kernel: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (ar7240_ohci)block sizes: ed 64 td 64
Jan 1 00:00:15 dnsmasq[861]: started, version 2.63 cachesize 512
Jan 1 00:00:15 dnsmasq[861]: 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:15 dnsmasq-dhcp[861]: DHCP, IP range 10.0.0.2 -- 10.255.255.254, lease time 6h
Jan 1 00:00:15 dnsmasq[861]: read /tmp/hosts - 2 addresses
Jan 1 00:00:15 dnsmasq-dhcp[861]: read /etc/ethers - 0 addresses
Jan 1 00:00:15 triggerPingRespond: OK
Jan 1 00:00:15 resident: record = action:up;iface:wan1;contag:3;ipaddr:192.168.92.183;netmask:255.255.255.0;gateway:192.168.92.1;dns1:192.168.100.205;dns2:192.168.100.243;
Jan 1 00:00:15 resident: phys_iface wan1
Jan 1 00:00:15 test: ip_type = (null)
Jan 1 00:00:15 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 00:00:15 resident: phys_iface
Jan 1 00:00:15 resident: resident_ipoe_handler - 2
Jan 1 00:00:15 resident: resident_ipoe_handler - 3, name: wan1_3
Jan 1 00:00:15 resident: resident_ipoe_handler - l2:wan1, l3:wan1_3, tun:wan1_2, ip_type:0
Jan 1 00:00:15 resident: resident_ipoe_handler - ipv4
Jan 1 00:00:15 resident: start ip_is_up on iface wan1_3
Jan 1 00:00:15 resident: ip_is_up for link wan1_3
Jan 1 00:00:15 set_dhcp_routes: set routes for iface wan1
Jan 1 00:00:15 kernel: cmd=3
Jan 1 00:00:15 kernel: AG7240: enet unit:1 phy:0 is up...Mii 100Mbps full duplex
Jan 1 00:00:15 kernel: AG7240: done cfg2 0x7215 ifctl 0x0 miictrl
Jan 1 00:00:15 apply_route: command = ip ro a 192.168.0.0/16 via 192.168.92.1
Jan 1 00:00:15 apply_route: command = ip ro a 82.138.2.0/27 via 192.168.92.1
Jan 1 00:00:15 resident: update dns
Jan 1 00:00:15 dnsmasq[861]: read /tmp/hosts - 2 addresses
Jan 1 00:00:15 dnsmasq-dhcp[861]: read /etc/ethers - 0 addresses
Jan 1 00:00:15 dnsmasq[861]: using nameserver 172.16.100.106#53
Jan 1 00:00:15 resident: update rip
Jan 1 00:00:15 resident: update igmpx
Jan 1 00:00:15 resident: stop igmpx
Jan 1 00:00:15 resident: igmpx *..l*..^L
Jan 1 00:00:16 syslog: Loading liblogger v2.0.2
Jan 1 00:00:16 syslog: upstream ifaces: *..l*..^L
Jan 1 00:00:16 syslog: downstream ifaces: br0
Jan 1 00:00:16 syslog: hews interval = 120.0 sec
Jan 1 00:00:16 syslog: doublet join enabled
Jan 1 00:00:16 syslog: Using old argv style
Jan 1 00:00:16 syslog: daemonizing ...
Jan 1 00:00:16 syslog: kernel multicast version is 305 (v3.05 ?)
Jan 1 00:00:16 syslog: kernel mroute inited
Jan 1 00:00:16 syslog: proxy prepared
Jan 1 00:00:16 syslog: ioctl: get iface index: *..l*..^L: 19(No such device)
Jan 1 00:00:16 syslog: vifi #0 added for br0
Jan 1 00:00:16 syslog: valid VIF's configured: upstreams=0, downstreams=1. Bad.
Jan 1 00:00:16 resident: update igmpx compiled
Jan 1 00:00:16 resident: update ntpclient
Jan 1 00:00:16 update_ntpclient: server string: ntpd -t -p pool.ntp.org&
Jan 1 04:00:16 start_pppd: tunnel: ifaces/wan1/services/wan1_3/tunnels/wan1_2/
Jan 1 04:00:16 resident: start pppd on wan1_2
Jan 1 04:00:16 resident: stop pppd on wan1_2
Jan 1 04:00:16 kernel: cmd=4
Jan 1 04:00:16 kernel: cmd=4
Jan 1 04:00:16 resident: set lock on wan1_2, with "/var/lock/wan1_2.lock"
Jan 1 04:00:16 resident: stopped link(contype:pptp, iface:wan1_2)
Jan 1 04:00:18 dnsmasq[861]: vendor id = "MSFT 5.0"
Jan 1 04:00:18 dnsmasq-dhcp[861]: DHCPREQUEST(br0) 10.0.0.103 60:a4:4c:a7:27:bc
Jan 1 04:00:18 dnsmasq-dhcp[861]: DHCPACK(br0) 10.0.0.103 60:a4:4c:a7:27:bc Serv1
Jan 1 04:00:20 dnsmasq[861]: vendor id = "MSFT 5.0"
Jan 1 04:00:20 dnsmasq-dhcp[861]: DHCPREQUEST(br0) 10.0.0.102 bc:ae:c5:41:81:ad
Jan 1 04:00:20 dnsmasq-dhcp[861]: DHCPACK(br0) 10.0.0.102 bc:ae:c5:41:81:ad VetKabinet
Jan 1 04:00:20 dnsmasq[861]: vendor id = "MSFT 5.0"
Jan 1 04:00:20 dnsmasq-dhcp[861]: DHCPREQUEST(br0) 10.0.0.100 94:de:80:ab:d7:b6
Jan 1 04:00:20 dnsmasq-dhcp[861]: DHCPACK(br0) 10.0.0.100 94:de:80:ab:d7:b6 PointOfSale
Jan 1 04:00:24 dnsmasq[861]: vendor id = "MSFT 5.0"
Jan 1 04:00:24 dnsmasq-dhcp[861]: DHCPINFORM(br0) 10.0.0.100 94:de:80:ab:d7:b6
Jan 1 04:00:24 dnsmasq-dhcp[861]: DHCPACK(br0) 10.0.0.100 94:de:80:ab:d7:b6 PointOfSale
Jan 1 04:00:25 dnsmasq[861]: vendor id = "MSFT 5.0"
Jan 1 04:00:25 dnsmasq-dhcp[861]: DHCPINFORM(br0) 10.0.0.103 60:a4:4c:a7:27:bc
Jan 1 04:00:25 dnsmasq-dhcp[861]: DHCPACK(br0) 10.0.0.103 60:a4:4c:a7:27:bc Serv1
Jan 1 04:00:39 dnsmasq[861]: vendor id = "MSFT 5.0"
Jan 1 04:00:39 dnsmasq-dhcp[861]: DHCPINFORM(br0) 10.0.0.102 bc:ae:c5:41:81:ad
Jan 1 04:00:39 dnsmasq-dhcp[861]: DHCPACK(br0) 10.0.0.102 bc:ae:c5:41:81:ad VetKabinet
Jan 1 04:01:15 hostapd: ath0: STA f4:6d:04:8b:85:d1 IEEE 802.11: associated
Jan 1 04:01:15 hostapd: ath0: STA f4:6d:04:8b:85:d1 WPA: pairwise key handshake completed (RSN)
Jan 1 04:01:16 get_host_ip: error in getaddrinfo: Name or service not known
Jan 1 04:01:16 pptp[902]: Plugin /usr/lib/pppd/pptp.so loaded.
Jan 1 04:01:16 pptp[902]: PPTP plugin version 0.8.3 compiled against pppd 2.4.4
Jan 1 04:01:16 pptp[903]: pppd 2.4.4 started by admin, uid 0
Jan 1 04:01:16 pptp[903]: Check server vpn.rednet.su
Jan 1 04:01:16 pptp[903]: route_add: have route to host on this dev wan1
Jan 1 04:01:16 pptp[904]: IP: 192.168.100.104
Jan 1 04:01:16 pptp[904]: control connection
Jan 1 04:01:16 pptp[904]: unix_sock
Jan 1 04:01:16 pptp[905]: Sent control packet type is 1 'Start-Control-Connection-Request'
Jan 1 04:01:16 pptp[905]: Received Start Control Connection Reply
Jan 1 04:01:16 pptp[905]: Client connection established.
Jan 1 04:01:17 pptp[905]: Sent control packet type is 7 'Outgoing-Call-Request'
Jan 1 04:01:17 pptp[905]: Received Outgoing Call Reply.
Jan 1 04:01:17 pptp[905]: Outgoing call established (call ID 1, peer's call ID 53783).
Jan 1 04:01:17 pptp[903]: Using interface ppp0
Jan 1 04:01:17 pptp[903]: Connect: ppp0 <--> pptp (vpn.rednet.su)
Jan 1 04:01:19 triggerPingRespond: OK
Jan 1 04:01:19 dnsmasq[861]: exiting on receipt of SIGTERM
Jan 1 04:01:20 pptp[903]: CHAP authentication succeeded
Jan 1 04:01:20 pptp[903]: local IP address 10.168.21.130
Jan 1 04:01:20 pptp[903]: remote IP address 172.16.100.104
Jan 1 04:01:20 pptp[903]: primary DNS address 172.16.100.104
Jan 1 04:01:22 dnsmasq[917]: started, version 2.63 cachesize 512
Jan 1 04:01:22 dnsmasq[917]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack
Jan 1 04:01:22 dnsmasq-dhcp[917]: DHCP, IP range 10.0.0.2 -- 10.255.255.254, lease time 6h
Jan 1 04:01:22 dnsmasq[917]: read /tmp/hosts - 2 addresses
Jan 1 04:01:22 dnsmasq-dhcp[917]: read /etc/ethers - 0 addresses
Jan 1 04:01:22 dnsmasq[917]: using nameserver 192.168.100.243#53
Jan 1 04:01:22 dnsmasq[917]: using nameserver 192.168.100.205#53
Jan 1 04:01:22 resident_phy_link_handler: record = phy:0;status:1
Jan 1 04:01:22 resident_phy_link_handler: phy - 0, status - 1
Jan 1 04:01:22 resident_ppp_handler: record = action:up;iface:ppp0;link:wan1_2;ipaddr:10.168.21.130;netmask:255.255.255.255;gateway:172.16.100.104;dns1:172.16.100.104;
Jan 1 04:01:22 resident: resident_ipoe_handler - Set default type: ipv4
Jan 1 04:01:22 resident: resident_ppp_handler - l2:wan1, l3:wan1_3, tun:wan1_2
Jan 1 04:01:22 kernel: cmd=3
Jan 1 04:01:22 apply_route: command = ip ro a 192.168.0.0/16 via 192.168.92.1
Jan 1 04:01:22 apply_route: command = ip ro a 82.138.2.0/27 via 192.168.92.1
Jan 1 04:01:22 resident: update dns
Jan 1 04:01:22 dnsmasq[917]: read /tmp/hosts - 2 addresses
Jan 1 04:01:22 dnsmasq-dhcp[917]: read /etc/ethers - 0 addresses
Jan 1 04:01:22 dnsmasq[917]: using nameserver 172.16.100.104#53
Jan 1 04:01:22 resident: update rip
Jan 1 04:01:22 resident: update ntpclient
Jan 1 04:01:22 update_ntpclient: server string: ntpd -t -p pool.ntp.org&
Jan 1 04:01:22 triggerPingRespond: OK
Jan 1 04:01:22 dnsmasq[917]: exiting on receipt of SIGTERM
Jan 1 04:01:25 dnsmasq[945]: started, version 2.63 cachesize 512
Jan 1 04:01:25 dnsmasq[945]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack
Jan 1 04:01:25 dnsmasq-dhcp[945]: DHCP, IP range 10.0.0.2 -- 10.255.255.254, lease time 6h
Jan 1 04:01:25 dnsmasq[945]: read /tmp/hosts - 2 addresses
Jan 1 04:01:25 dnsmasq-dhcp[945]: read /etc/ethers - 0 addresses
Jan 1 04:01:25 dnsmasq[945]: using nameserver 172.16.100.104#53
Jan 1 04:01:26 dnsmasq[945]: vendor id = "MSFT 5.0"
Jan 1 04:01:26 dnsmasq-dhcp[945]: DHCPINFORM(br0) 10.0.0.103 60:a4:4c:a7:27:bc
Jan 1 04:01:26 dnsmasq-dhcp[945]: DHCPACK(br0) 10.0.0.103 60:a4:4c:a7:27:bc Serv1
Jan 1 04:01:27 pptp[905]: Echo Request received.
Jan 1 04:01:27 pptp[905]: Sent control packet type is 6 'Echo-Reply'

(тут настроил ntp)

Apr 1 14:52:24 dnsmasq[945]: vendor id = "MSFT 5.0"
Apr 1 14:52:24 dnsmasq-dhcp[945]: DHCPREQUEST(br0) 10.29.211.108 f4:6d:04:8b:85:d1
Apr 1 14:52:24 dnsmasq-dhcp[945]: DHCPACK(br0) 10.29.211.108 f4:6d:04:8b:85:d1 cherepanov
Apr 1 14:52:26 hostapd: ath0: STA f4:6d:04:8b:85:d1 WPA: group key handshake completed (RSN)
Apr 1 14:52:31 pptp[905]: Echo Request received.
Apr 1 14:52:31 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:52:34 pptp[903]: System time change detected.
Apr 1 14:52:35 dnsmasq[945]: vendor id = "MSFT 5.0"
Apr 1 14:52:35 dnsmasq-dhcp[945]: DHCPINFORM(br0) 10.0.0.100 94:de:80:ab:d7:b6
Apr 1 14:52:35 dnsmasq-dhcp[945]: DHCPACK(br0) 10.0.0.100 94:de:80:ab:d7:b6 PointOfSale
Apr 1 14:52:41 pptp[905]: Echo Request received.
Apr 1 14:52:41 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:52:50 dnsmasq[945]: vendor id = "MSFT 5.0"
Apr 1 14:52:50 dnsmasq-dhcp[945]: DHCPINFORM(br0) 10.0.0.102 bc:ae:c5:41:81:ad
Apr 1 14:52:50 dnsmasq-dhcp[945]: DHCPACK(br0) 10.0.0.102 bc:ae:c5:41:81:ad VetKabinet
Apr 1 14:52:51 pptp[905]: Echo Request received.
Apr 1 14:52:51 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:53:01 pptp[905]: Echo Request received.
Apr 1 14:53:01 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:53:11 pptp[905]: Echo Request received.
Apr 1 14:53:11 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:53:21 pptp[905]: Echo Request received.
Apr 1 14:53:21 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:53:31 pptp[905]: Echo Request received.
Apr 1 14:53:31 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:53:41 pptp[905]: Echo Request received.
Apr 1 14:53:41 pptp[905]: Sent control packet type is 6 'Echo-Reply'
Apr 1 14:53:51 pptp[905]: Echo Request received.
Apr 1 14:53:51 pptp[905]: no more Echo Reply/Request packets will be reported.
Apr 1 14:53:53 dnsmasq[945]: vendor id = "MSFT 5.0"
Apr 1 14:53:53 dnsmasq-dhcp[945]: DHCPINFORM(br0) 10.0.0.102 bc:ae:c5:41:81:ad
Apr 1 14:53:53 dnsmasq-dhcp[945]: DHCPACK(br0) 10.0.0.102 bc:ae:c5:41:81:ad VetKabinet
Apr 1 14:58:26 kernel: ccmp_decap: Error: Big jump in pn number. TID=7, from 0 5 to 0 4a0. Frame seq=0x3000
Apr 1 14:58:26 kernel: ccmp_decap: The MIC is OK. Still use this frame and update PN.
Apr 1 14:58:26 hostapd: ath0: STA f4:6d:04:8b:85:d1 WPA: group key handshake completed (RSN)
Apr 1 15:01:24 kernel: Priletela cmd=0x89f3
Apr 1 15:01:27 kernel: Priletela cmd=0x89f3
Apr 1 15:01:30 kernel: Priletela cmd=0x89f3
Apr 1 15:03:55 dnsmasq[945]: vendor id = "MSFT 5.0"
Apr 1 15:03:55 dnsmasq-dhcp[945]: DHCPINFORM(br0) 10.0.0.102 bc:ae:c5:41:81:ad
Apr 1 15:03:55 dnsmasq-dhcp[945]: DHCPACK(br0) 10.0.0.102 bc:ae:c5:41:81:ad VetKabinet
Apr 1 15:04:29 hostapd: ath0: STA f4:6d:04:8b:85:d1 IEEE 802.11: deauthenticated due to local deauth request
Apr 1 15:04:29 hostapd: ath0: STA f4:6d:04:8b:85:d1 IEEE 802.11: disassociated

(после этого WiFi отваливается и устройства перестают его видеть вообще)

Apr 1 15:09:27 dnsmasq[945]: vendor id = "MSFT 5.0"
Apr 1 15:09:27 dnsmasq-dhcp[945]: DHCPINFORM(br0) 10.0.0.103 60:a4:4c:a7:27:bc
Apr 1 15:09:27 dnsmasq-dhcp[945]: DHCPACK(br0) 10.0.0.103 60:a4:4c:a7:27:bc Serv1
Apr 1 15:11:28 kernel: Priletela cmd=0x89f3
Apr 1 15:11:31 kernel: Priletela cmd=0x89f3

Не подскажете что это может значить?


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: Расшифровка логов роутеров
СообщениеДобавлено: Вт апр 01, 2014 17:12 
Не в сети

Зарегистрирован: Пн янв 28, 2013 16:25
Сообщений: 26
по поводу 615-ых порешали давным давно обновлением прошивки, на ревизии м начиная с прошивки 2.0.13 разрабы исправили актуальную для меня проблему по необновляющемуся айпи адресу, на к2 на 19-ой прошивке не работает айпитв на вайфае офисный 632 пришлось перешить под дд-врт, пробовал 1.4.1 и 1.4.3 2.0.0 не успел проблема с отваливанием вайфая ушла, 2.0.0 обкатал дома в ней та же проблема с необновлением айпи но к сожалению дд-врт плющит от мультикаста


Вернуться наверх
 Профиль  
 
Показать сообщения за:  Сортировать по:  
Начать новую тему Ответить на тему  [ Сообщений: 5 ] 

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


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

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


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

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