Not found pid process igmpx ошибка

Добрый день, у меня два месяца уже пропадает интернет, сам включается и выключается, звонил провайдеру все нормально, поменял роутер, и так же сетуация, тут зашел в журнал событий и выдает такой лог, это нормально?
Jan 1 00:00:07 kernel: 867x ver = Q, (0412 ver)=0x63330000, (ver)=0x3200
Jan 1 00:00:07 libshared rtl:start_wifi[41]: begin
Jan 1 00:00:07 start_wifi[41]: start on br= br0
Jan 1 00:00:07 sched_set_task_activity[41]: Cannot open pipe
Jan 1 00:00:07 DMS_NL_API[41]: Rtnetlink answer: Success
Jan 1 00:00:07 DMS_ROUTE_SUCCESS[41]: ADD 239.255.255.250 via (null) dev br0 metr 0 table 254 (configure_config_file)
Jan 1 00:00:07 start_wifi[41]: pin = 73194378
Jan 1 00:00:07 config_ssid_params[41]: begin
Jan 1 00:00:07 config_ssid_params[41]: ifname = wlan0
Jan 1 00:00:07 get_gr_name_by_lan_key[41]: start
Jan 1 00:00:07 get_gr_name_by_lan_key[41]: wlan0: br0
Jan 1 00:00:07 start_wifi[41]: Starting iwcontrol…
Jan 1 00:00:07 kernel: device wlan0 entered promiscuous mode
Jan 1 00:00:08 kernel: Time_elapse(1) = 1150
Jan 1 00:00:08 kernel: Time_elapse@sendtimer = 1150
Jan 1 00:00:10 update_ipfilters[41]: error in params
Jan 1 00:00:10 kernel: Fast path for http trafic Enable
Jan 1 00:00:10 calculate_file_md5sum[41]: Error: can’t open file /tmp/dnsmasq.conf
Jan 1 00:00:10 recheck_dnsmasq[41]: MD5 sums of /tmp/dnsmasq.conf cannot be calculated, restarting DNSMASQ
Jan 1 00:00:10 resident[41]: init wan
Jan 1 00:00:10 get_gr_name_by_l3_key[41]: start
Jan 1 00:00:10 get_gr_name_by_l3_key[41]: br0
Jan 1 00:00:10 get_gr_name_by_l3_key[41]: start
Jan 1 00:00:10 get_gr_name_by_l3_key[41]: br0
Jan 1 00:00:11 pppoe-relay[194]: [truncated] m
Jan 1 00:00:11 dms_srv_httpd_start[41]: start
Jan 1 00:00:13 telnet-start[41]: begin…
Jan 1 00:00:13 telnet-start[41]: running on 23 port
Jan 1 00:00:13 telnet-start[41]: succes!
Jan 1 00:00:13 anweb[203]: Starting…
Jan 1 00:00:13 start_tr069_with_args[41]: start success with new pid 207
Jan 1 00:00:13 recheck_dnsmasq[41]: MD5 sums of /tmp/dnsmasq.conf are equal, not restarting DNSMASQ
Jan 1 00:00:14 link_watcher_start[41]: link watcher start with status -1
Jan 1 00:00:14 resident[41]: Out init_device
Jan 1 00:00:15 resident_mng[40]: RESIDENT WORKER is running.
Jan 1 00:00:15 anweb[203]: anweb sighandler signal = 126
Jan 1 00:00:15 anweb[203]: HTTP main server started on 80,443s port (ports).
Jan 1 00:00:15 anweb[203]: HTTP intercept server started on 81,4445s port (ports).
Jan 1 00:00:15 resident_phy_link_handler[232]: record = phy:4;status:1
Jan 1 00:00:15 resident_phy_link_handler[232]: phy — 4, status — 1
Jan 1 00:00:15 resident_phy_link_handler[231]: record = phy:3;status:0
Jan 1 00:00:15 resident_phy_link_handler[231]: phy — 3, status — 0
Jan 1 00:00:15 dms_link_watch_lock[231]: Semaphore creation error 17 (File exists)
Jan 1 00:00:15 resident_phy_link_handler[230]: record = phy:2;status:0
Jan 1 00:00:15 resident_phy_link_handler[230]: phy — 2, status — 0
Jan 1 00:00:15 dms_link_watch_lock[230]: Semaphore creation error 17 (File exists)
Jan 1 00:00:15 resident_phy_link_handler[229]: record = phy:1;status:0
Jan 1 00:00:15 resident_phy_link_handler[229]: phy — 1, status — 0
Jan 1 00:00:15 dms_link_watch_lock[229]: Semaphore creation error 17 (File exists)
Jan 1 00:00:15 resident_phy_link_handler[232]: Exit
Jan 1 00:00:15 resident_phy_link_handler[231]: Exit
Jan 1 00:00:15 resident_phy_link_handler[230]: Exit
Jan 1 00:00:15 resident_phy_link_handler[229]: Exit
Jan 1 00:00:16 main[216]: reboot_timeout_stop(-1)
Jan 1 00:00:16 main[216]: reboot_timeout_stop(-1)
Jan 1 00:00:16 main[216]: reboot_timeout_stop(-1)
Jan 1 00:00:16 main[216]: reboot_timeout_stop(-1)
Jan 1 00:00:16 main[216]: reboot_timeout_stop(-1)
Jan 1 00:00:16 kernel: br0: port 4(eth0.5) entering forwarding state
Jan 1 00:00:16 kernel: br0: port 3(eth0.4) entering forwarding state
Jan 1 00:00:16 kernel: br0: port 2(eth0.3) entering forwarding state
Jan 1 00:00:16 kernel: br0: port 1(eth0.2) entering forwarding state
Jan 1 00:00:17 save config[298]: saving… at line 176
Jan 1 00:00:17 write[298]: line 1321
Jan 1 00:00:17 save_to_flash[298]: file size is 3469
Jan 1 00:00:17 save config[298]: saving… at line 197
Jan 1 00:00:18 kernel: SachemAccess::reset()
Jan 1 00:00:18 kernel: 8676S ctrlin readback: afe version = 0x 3430
Jan 1 00:00:18 kernel: AFE_ver=0x686
Jan 1 00:00:18 kernel: 8676(>M) + 6256/6257 decide use DDR mode
Jan 1 00:00:18 kernel: xtm_elapse() = 11230
Jan 1 00:00:18 kernel: LD Power down to avoid huge current
Jan 1 00:00:18 kernel: TxIdxTxIdx = 0
Jan 1 00:00:18 kernel: OKnum=512
Jan 1 00:00:18 kernel: DDR phase 0xd OK
Jan 1 00:00:18 kernel: OKnum=36
Jan 1 00:00:18 kernel: OKnum=19
Jan 1 00:00:18 kernel: OKnum=36
Jan 1 00:00:23 kernel: Time_elapse(2) = 16370
Jan 1 00:00:23 kernel: SachemAccess::reset()
Jan 1 00:00:27 kernel: SachemAccess::reset()
Jan 1 00:00:27 kernel: [br_handle_frame_finish 447]tmpOp=2.
Jan 1 00:00:27 kernel: [br_handle_frame_finish 447]tmpOp=1.
Jan 1 00:00:27 kernel: [br_handle_frame_finish 447]tmpOp=2.
Jan 1 00:00:27 kernel: [br_handle_frame_finish 447]tmpOp=1.
Jan 1 00:00:27 kernel: [br_handle_frame_finish 447]tmpOp=1.
Jan 1 00:00:28 kernel: SachemAccess::reset()
Jan 1 00:00:29 kernel: SachemAccess::reset()
Jan 1 00:00:31 kernel: SachemAccess::reset()
Jan 1 00:00:31 kernel: SachemAccess::reset()
Jan 1 00:00:33 kernel: SachemAccess::reset()
Jan 1 00:00:33 kernel: xtm_elapse() = 25870
Jan 1 00:00:33 kernel: LD Power down to avoid huge current
Jan 1 00:00:33 kernel: TxIdxTxIdx = 0
Jan 1 00:00:33 kernel: OKnum=512
Jan 1 00:00:33 kernel: DDR phase 0xd OK
Jan 1 00:00:33 kernel: OKnum=34
Jan 1 00:00:33 kernel: OKnum=21
Jan 1 00:00:33 kernel: OKnum=32
Jan 1 00:00:33 kernel: Final DDR phase auto select 13,forceDdrRxPhaseEdge=-1,forceDdrTxPhaseEdge=-1
Jan 1 00:00:33 kernel: LD Power On at end of DDR autoK
Jan 1 00:00:38 kernel: Time_elapse(3) = 31010
Jan 1 00:00:38 kernel: SachemAccess::reset()
Jan 1 00:00:39 kernel: SachemAccess::reset()
Jan 1 00:01:00 update_ntpclient[457]: start
Jan 1 00:01:00 update_ntpclient[457]: server string: ntpd -S /sbin/ntpevent -p pool.ntp.org&
Jan 1 03:01:09 kernel: ATM OAM F5 initialized.
Jan 1 03:01:09 kernel: ATM OAM F4 initialized.
Jan 1 03:01:09 kernel: Enable 8671G 1 function
Jan 1 03:01:09 kernel: Enable 8671 0 function
Jan 1 03:01:09 kernel: Enable 8672 function
Jan 1 03:01:09 kernel: applying workaround…done
Jan 1 03:01:09 kernel: Upstream Rate : 509 Kbps (line rate : 656)
Jan 1 03:01:09 kernel: Downstream Rate : 511 Kbps (line rate : 716)
Jan 1 03:01:18 resident[504]: resident_adsl_link_handler start!!!
Jan 1 03:01:18 resident[504]: record = type:atm
Jan 1 03:01:18 rlx_modem[504]: create atm start!!!
Jan 1 03:01:18 rlx_modem[504]: atmnum=1
Jan 1 03:01:18 rlx_modem[504]: cmd sarctl pvcnumber 1!!!
Jan 1 03:01:18 kernel: sar_ioctl: called. cmd=0x8a05, arg=7ff4388c
Jan 1 03:01:18 kernel: PVC Number = 1. Set Desc number per VC = 126
Jan 1 03:01:18 rlx_modem[504]: cmd mpoactl add vc0 pvc 8.35 encaps 1 qos ubr:pcr=6000!!!
Jan 1 03:01:18 syslog: Interface «vc0» created sucessfully
Jan 1 03:01:18 syslog: Communicating over ATM 0.8.35, encapsulation: 1
Jan 1 03:01:18 kernel: fixme atm_find_ci in sar_open!
Jan 1 03:01:18 kernel: (itf 0): open 8.35
Jan 1 03:01:18 kernel: create: ch0 (8/35) 6000,0
Jan 1 03:01:18 kernel: ATM OAM F5 initialized.
Jan 1 03:01:18 kernel: ATM OAM F4 initialized.
Jan 1 03:01:18 kernel: Enable 8671G 1 function
Jan 1 03:01:18 kernel: Enable 8671 0 function
Jan 1 03:01:18 kernel: Enable 8672 function
Jan 1 03:01:18 kernel: create: ch0 (8/35) 6000,0
Jan 1 03:01:18 kernel: net_device: 2175891456
Jan 1 03:01:18 kernel: applying workaround…done
Jan 1 03:01:18 syslog: Interface configured
Jan 1 03:01:18 kernel: sar_ioctl: called. cmd=0x8a08, arg=817fbb88
Jan 1 03:01:18 kernel: sar_ioctl: called. cmd=0x8a0f, arg=00415008
Jan 1 03:01:18 kernel: sar_ioctl: SAR_SET_SARHDR called.
Jan 1 03:01:18 kernel: vpi=8, vci = 35
Jan 1 03:01:18 kernel: Set CH 0 PPPoE mode on CKS register
Jan 1 03:01:18 kernel: sar_ioctl: SAR_SET_SARHDR done.
Jan 1 03:01:18 kernel: sar_ioctl: called. cmd=0x8a10, arg=(null)
Jan 1 03:01:18 rlx_modem[504]: mpoactl set vc0 vlan 0 vid 0 vprio 0
Jan 1 03:01:18 rlx_modem[504]: ifconfig vc0 mtu 1500
Jan 1 03:01:19 start_stop_wan_link_on_l2[504]: start with iface: vc0, status: 1
Jan 1 03:01:19 resident[504]: start ipoe
Jan 1 03:01:19 before_start_ip[504]:
Jan 1 03:01:19 start_ip[504]: begin (vc0 -> vc0_1)
Jan 1 03:01:19 resident[504]: start ipoe (v0) on vc0
Jan 1 03:01:19 start_ip[504]: pos = 9
Jan 1 03:01:19 start_stop_wan_link_on_l2[504]: End iface: vc0, status: 1
Jan 1 03:01:19 rlx_modem[504]: create atm start!!!
Jan 1 03:01:19 rlx_modem[504]: atmnum=2
Jan 1 03:01:19 rlx_modem[504]: cmd sarctl pvcnumber 2!!!
Jan 1 03:01:19 kernel: sar_ioctl: called. cmd=0x8a05, arg=7fd41bac
Jan 1 03:01:19 kernel: PVC Number = 2. Set Desc number per VC = 126
Jan 1 03:01:19 rlx_modem[504]: cmd mpoactl add vc1 pvc 0.33 encaps 1 qos ubr:pcr=6000!!!
Jan 1 03:01:19 syslog: Interface «vc1» created sucessfully
Jan 1 03:01:19 syslog: Communicating over ATM 0.0.33, encapsulation: 1
Jan 1 03:01:19 kernel: fixme atm_find_ci in sar_open!
Jan 1 03:01:19 kernel: (itf 0): open 0.33
Jan 1 03:01:19 kernel: create: ch1 (0/33) 6000,0
Jan 1 03:01:19 kernel: ATM OAM F5 initialized.
Jan 1 03:01:19 kernel: ATM OAM F4 initialized.
Jan 1 03:01:20 kernel: Enable 8671G 1 function
Jan 1 03:01:20 kernel: Enable 8671 0 function
Jan 1 03:01:20 kernel: Enable 8672 function
Jan 1 03:01:20 kernel: create: ch0 (8/35) 6000,0
Jan 1 03:01:20 kernel: net_device: 2175891456
Jan 1 03:01:20 kernel: create: ch1 (0/33) 6000,0
Jan 1 03:01:20 kernel: net_device: 2173857792
Jan 1 03:01:20 kernel: applying workaround…done
Jan 1 03:01:20 kernel: sar_ioctl: called. cmd=0x8a0f, arg=00415008
Jan 1 03:01:20 kernel: sar_ioctl: SAR_SET_SARHDR called.
Jan 1 03:01:20 kernel: vpi=0, vci = 33
Jan 1 03:01:20 kernel: Set CH 1 PPPoE mode on CKS register
Jan 1 03:01:20 kernel: sar_ioctl: SAR_SET_SARHDR done.
Jan 1 03:01:20 syslog: Interface configured
Jan 1 03:01:20 kernel: sar_ioctl: called. cmd=0x8a08, arg=817fbb88
Jan 1 03:01:20 kernel: sar_ioctl: called. cmd=0x8a10, arg=(null)
Jan 1 03:01:20 rlx_modem[504]: mpoactl set vc1 vlan 0 vid 0 vprio 0
Jan 1 03:01:20 rlx_modem[504]: ifconfig vc1 mtu 1500
Jan 1 03:01:20 udhcpc[535]: UDHCP start..
Jan 1 03:01:20 udhcpc[535]: udhcp client (v0.9.8) started (iface: vc0, connect: 1)
Jan 1 03:01:20 udhcpc[535]: interface vc0 index 19
Jan 1 03:01:20 udhcpc[535]: interface vc0 hwaddr 1c:5f:2b:5a:9b:f2
Jan 1 03:01:20 udhcpc[535]: interface vc0 mtu is 1500
Jan 1 03:01:20 udhcpc[567]: execle’ing /tmp/udhcpc with name deconfig
Jan 1 03:01:20 event[567]: send event «ipoe down»
Jan 1 03:01:20 resident[216]: record = action:down;iface:vc0;contag:1;
Jan 1 03:01:20 udhcpc[535]: Opening raw socket on ifindex 19
Jan 1 03:01:20 udhcpc[535]: Sending discover…
Jan 1 03:01:20 resident[216]: phys_iface vc0
Jan 1 03:01:20 resident_ipoe_handler[216]: ip_type = <null>
Jan 1 03:01:20 resident[216]: resident_ipoe_handler — Set default type: ipv4
Jan 1 03:01:20 resident[216]: phys_iface vc0
Jan 1 03:01:20 resident[216]: resident_ipoe_handler — 2
Jan 1 03:01:20 resident_ipoe_handler[216]: name: vc0_1
Jan 1 03:01:21 start_stop_wan_link_on_l2[504]: start with iface: vc1, status: 1
Jan 1 03:01:21 start_pppd[504]: start pppd on vc1_1
Jan 1 03:01:21 stop_pppd[504]: stop pppd on vc1_1
Jan 1 03:01:21 resident[504]: set lock on vc1_1, with «/var/lock/vc1_1.lock»
Jan 1 03:01:21 wan_down[504]: name = ppp0
Jan 1 03:01:21 update_wan_firewall[504]: firewall enable
Jan 1 03:01:21 get_gr_name_by_l3_key[504]: start
Jan 1 03:01:21 get_gr_name_by_l3_key[504]: br0
Jan 1 03:01:21 get_gr_index[504]: gr=|0|
Jan 1 03:01:21 DMS_NL_API[504]: Rtnetlink answer: No such process
Jan 1 03:01:21 DMS_ROUTE_ERROR[504]: DEL default via (null) dev (null) metr 0 table 254 (wan_iptables_rules)
Jan 1 03:01:21 rlx_modem[504]: only_bridges routed connectons exist
Jan 1 03:01:21 triggerPingRespond[504]: OK
Jan 1 03:01:21 update_igmpx[504]: begin
Jan 1 03:01:21 get_gr_name_by_l3_key[504]: start
Jan 1 03:01:21 update_igmpx[504]: igmpx cfg: upstream list empty downstream list empty
Jan 1 03:01:21 stop_igmpx[504]: stop igmpx
Jan 1 03:01:21 stop_process_t[504]: not found pid process ‘igmpx’
Jan 1 03:01:21 resident[504]: stopped link(contype:ppp, iface:vc1_1)
Jan 1 03:01:21 after_stop_pppd[504]:
Jan 1 03:01:21 before_start_pppd[504]:
Jan 1 03:01:22 udhcpc[535]: Sending discover…
Jan 1 03:01:23 start_pppd[504]: using old session parameters: 3337:3C:94:D5:01:48:00
Jan 1 03:01:23 pppd[582]: Plugin /usr/lib/pppd/rp-pppoe.so loaded.
Jan 1 03:01:23 pppd[583]: pppd 2.4.4 started by admin, uid 0
Jan 1 03:01:26 start_stop_wan_link_on_l2[504]: End iface: vc1, status: 1
Jan 1 03:01:26 get_gr_name_by_l3_key[504]: start
Jan 1 03:01:26 get_gr_name_by_l3_key[504]: br0
Jan 1 03:01:26 get_gr_name_by_l3_key[504]: start
Jan 1 03:01:26 get_gr_name_by_l3_key[504]: br0
Jan 1 03:01:26 resident[216]: resident_ipoe_handler — l2:vc0, l3:vc0_1, tun:, ip_type:0
Jan 1 03:01:26 resident[216]: ip_is_down on vc0_1
Jan 1 03:01:26 resident_ipoe_handler[216]: is done on iface vc0_1 with action down
Jan 1 03:01:26 resident_ipoe_handler[216]: exit
Jan 1 03:01:26 udhcpc[535]: Sending discover…
Jan 1 03:01:30 pppd[583]: Sent PADT
Jan 1 03:01:30 pppoe-relay[595]: PADO packet from 3c:94:d5:01:4c:d4 on interface vc1 does not have Relay-Session-Id tag
Jan 1 03:01:30 pppoe-relay[595]: PADO packet from 4c:96:14:ab:64:82 on interface vc1 does not have Relay-Session-Id tag
Jan 1 03:01:30 pppoe-relay[595]: PADO packet from 3c:94:d5:01:48:00 on interface vc1 does not have Relay-Session-Id tag
Jan 1 03:01:30 pppoe-relay[595]: PADO packet from 4c:96:14:ab:64:d4 on interface vc1 does not have Relay-Session-Id tag
Jan 1 03:01:30 pppoe-relay[595]: PADS packet from 3c:94:d5:01:4c:d4 on interface vc1 does not have Relay-Session-Id tag
Jan 1 03:01:30 pppd[583]: PPP session is 32871
Jan 1 03:01:30 pppd[583]: Used ACName = «KRDR-BRAS6» in ppp(0)
Jan 1 03:01:30 kernel: Enter _rtl865x_attachMasterNetif (slave : ppp0 master : vc1)
Jan 1 03:01:30 kernel: (_rtl865x_attachMasterNetif) slave_netif : ppp0
Jan 1 03:01:30 kernel: (_rtl865x_attachMasterNetif) master_netif : NULL
Jan 1 03:01:30 kernel: Leave _rtl865x_attachMasterNetif @ 392
Jan 1 03:01:30 kernel: _rtl865x_getVlanFilterDatabaseId(336):the vlan is invalid!!!BUG!!!!
Jan 1 03:01:30 pppd[583]: Using interface ppp0
Jan 1 03:01:30 pppd[583]: Connect: ppp0 <—> vc1
Jan 1 03:01:30 resident_ppp_handler[614]: record = action:acname;iface:ppp0;acname:KRDR-BRAS6;link:vc1_1;
Jan 1 03:01:30 resident_ppp_handler[614]: Set default type: ipv4
Jan 1 03:01:30 resident_ppp_handler[614]: l2:vc1, l3:vc1_1, tun:||
Jan 1 03:01:31 pppd[583]: PAP authentication succeeded
Jan 1 03:01:31 pppd[583]: peer from calling number 3C:94:D5:01:4C:D4 authorized
Jan 1 03:01:31 pppd[583]: local IP address 100.66.185.94
Jan 1 03:01:31 pppd[583]: remote IP address 178.34.128.9
Jan 1 03:01:31 pppd[583]: primary DNS address 85.175.46.130
Jan 1 03:01:31 pppd[583]: secondary DNS address 85.175.46.122
Jan 1 03:01:31 resident_ppp_handler[618]: record = action:up;iface:ppp0;link:vc1_1;ipaddr:100.66.185.94;netmask:255.255.255.255;gateway:178.34.128.9;dns1:85.175.46.130;dns2:85.175.46.122;sess_id:32871:3C:94:D5:01:4C:D4;gw_mac:3C:94:D5:01:4C:D4;
Jan 1 03:01:31 resident_ppp_handler[618]: Set default type: ipv4
Jan 1 03:01:31 resident_ppp_handler[618]: l2:vc1, l3:vc1_1, tun:||
Jan 1 03:01:31 resident[618]: ppp_is_up on vc1_1
Jan 1 03:01:31 DMS_NL_API[618]: Rtnetlink answer: Success
Jan 1 03:01:31 DMS_ROUTE_SUCCESS[618]: DEL 178.34.128.9 via (null) dev ppp0 metr 0 table 254 (ppp_is_up)
Jan 1 03:01:31 DMS_NL_API[618]: Rtnetlink answer: Success
Jan 1 03:01:31 DMS_ROUTE_SUCCESS[618]: ADD default via (null) dev ppp0 metr 50 table 254 (ppp_is_up)
Jan 1 03:01:31 DMS_NL_API[618]: Rtnetlink answer: Success
Jan 1 03:01:31 DMS_ROUTE_SUCCESS[618]: ADD default via (null) dev ppp0 metr 50 table 253 (ppp_is_up)
Jan 1 03:01:31 get_gr_name_by_l3_key[618]: start
Jan 1 03:01:31 get_gr_name_by_l3_key[618]: br0
Jan 1 03:01:31 get_gr_index[618]: gr=|0|
Jan 1 03:01:31 DMS_NL_API[618]: Rtnetlink answer: Success
Jan 1 03:01:31 DMS_ROUTE_SUCCESS[618]: DEL default via (null) dev (null) metr 0 table 254 (wan_iptables_rules)
Jan 1 03:01:31 DMS_NL_API[618]: Rtnetlink answer: Success
Jan 1 03:01:31 DMS_ROUTE_SUCCESS[618]: ADD default via (null) dev ppp0 metr 0 table 254 (wan_iptables_rules)
Jan 1 03:01:31 rlx_modem[618]: only_bridges routed connectons exist
Jan 1 03:01:31 triggerPingRespond[618]: OK
Jan 1 03:01:31 update_ripd[618]: update rip
Jan 1 03:01:31 update_igmpx[618]: begin
Jan 1 03:01:31 get_gr_name_by_l3_key[618]: start
Jan 1 03:01:31 update_igmpx[618]: igmpx cfg: upstream list empty downstream list empty
Jan 1 03:01:31 stop_igmpx[618]: stop igmpx
Jan 1 03:01:31 stop_process_t[618]: not found pid process ‘igmpx’
Jan 1 03:01:31 update_ntpclient[618]: start
Jan 1 03:01:31 update_ntpclient[618]: server string: ntpd -S /sbin/ntpevent -p pool.ntp.org&
Jan 1 03:01:31 update_wan_firewall[618]: firewall enable
Jan 1 03:01:31 recheck_dnsmasq[618]: MD5 sums of /tmp/dnsmasq.conf are equal, not restarting DNSMASQ
Jan 1 03:01:32 autoupdate[618]: Downloading file: fwupdate.dlink.ru/dislocation
Jan 1 03:01:32 autoupdate[618]: Downloading file: fwupdate.dlink.ru/xDSL/DSL-2640U_RB_U2A_8M/Firmware/exclude
Jan 1 03:01:32 autoupdate[618]: Not found exception
Jan 1 03:01:32 autoupdate[618]: Downloading file: fwupdate.dlink.ru/xDSL/DSL-2640U_RB_U2A_8M/Firmware/latest
Jan 1 03:01:33 autoupdate[618]: Downloading file: fwupdate.dlink.ru/xDSL/DSL-2640U_RB_U2A_8M/Firmware/2017.07.13-15.31_DSL_2640RTL_S_8M_B_3.0.0_release.des
Jan 1 03:01:33 autoupdate[618]: Update not needed
Jan 1 03:01:39 udhcpc[535]: Sending discover…
Feb 11 10:46:56 udhcpc[535]: Sending discover…
Feb 11 10:46:56 dms_etherwan_read[689]: start
Feb 11 10:46:56 dms_get_etherwan_port[689]: start
Feb 11 10:46:56 dms_get_etherwan_port[689]: end: etherwan port 0
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: start 1
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: end
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: start
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: eth0.5: br0
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: start 2
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: end
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: start
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: eth0.4: br0
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: start 3
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: end
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: start
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: eth0.3: br0
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: start 4
Feb 11 10:46:56 dms_get_etherwan_port_info[689]: end
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: start
Feb 11 10:46:56 get_gr_name_by_lan_key[689]: eth0.2: br0
Feb 11 10:46:56 dms_etherwan_read[689]: end
Feb 11 10:46:56 adsl_status[691]: 1950
Feb 11 10:46:57 adsl_status[702]: 1950
Feb 11 10:46:57 dms_etherwan_read[710]: start
Feb 11 10:46:57 dms_get_etherwan_port[710]: start
Feb 11 10:46:57 dms_get_etherwan_port[710]: end: etherwan port 0
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: start 1
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: end
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: start
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: eth0.5: br0
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: start 2
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: end
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: start
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: eth0.4: br0
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: start 3
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: end
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: start
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: eth0.3: br0
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: start 4
Feb 11 10:46:57 dms_get_etherwan_port_info[710]: end
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: start
Feb 11 10:46:57 get_gr_name_by_lan_key[710]: eth0.2: br0
Feb 11 10:46:57 dms_etherwan_read[710]: end
Feb 11 10:46:57 adsl_status[712]: 1950
Feb 11 10:46:57 adsl_status[717]: 1950
Feb 11 10:47:00 udhcpc[535]: Sending discover…
Feb 11 10:47:01 dms_etherwan_read[740]: start
Feb 11 10:47:01 dms_get_etherwan_port[740]: start
Feb 11 10:47:01 dms_get_etherwan_port[740]: end: etherwan port 0
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: start 1
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: end
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: start
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: eth0.5: br0
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: start 2
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: end
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: start
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: eth0.4: br0
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: start 3
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: end
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: start
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: eth0.3: br0
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: start 4
Feb 11 10:47:01 dms_get_etherwan_port_info[740]: end
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: start
Feb 11 10:47:01 get_gr_name_by_lan_key[740]: eth0.2: br0
Feb 11 10:47:01 dms_etherwan_read[740]: end
Feb 11 10:47:01 adsl_status[743]: 1950
Feb 11 10:47:01 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:0
Feb 11 10:47:01 pppd[583]: System time change detected.
Feb 11 10:47:01 pppd[583]: write: Bad address (14)
Feb 11 10:47:01 adsl_status[748]: 1950
Feb 11 10:47:05 update_ntpclient_periodic[766]: date is set, switching off periodic update.
Feb 11 10:47:05 autoupdate[763]: Downloading file: fwupdate.dlink.ru/dislocation
Feb 11 10:47:05 autoupdate[763]: Downloading file: fwupdate.dlink.ru/xDSL/DSL-2640U_RB_U2A_8M/Firmware/exclude
Feb 11 10:47:05 autoupdate[763]: Not found exception
Feb 11 10:47:05 autoupdate[763]: Downloading file: fwupdate.dlink.ru/xDSL/DSL-2640U_RB_U2A_8M/Firmware/latest
Feb 11 10:47:06 autoupdate[763]: Downloading file: fwupdate.dlink.ru/xDSL/DSL-2640U_RB_U2A_8M/Firmware/2017.07.13-15.31_DSL_2640RTL_S_8M_B_3.0.0_release.des
Feb 11 10:47:06 autoupdate[763]: Update not needed
Feb 11 10:47:13 udhcpc[728]: Sending discover…
Feb 11 10:47:15 udhcpc[728]: Sending discover…
Feb 11 10:47:19 udhcpc[728]: Sending discover…
Feb 11 10:47:31 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:1
Feb 11 10:47:31 pppd[583]: write: Bad address (14)
Feb 11 10:47:32 udhcpc[728]: Sending discover…
Feb 11 10:47:34 udhcpc[728]: Sending discover…
Feb 11 10:47:38 udhcpc[728]: Sending discover…
Feb 11 10:48:01 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:2
Feb 11 10:48:01 pppd[583]: write: Bad address (14)
Feb 11 10:48:31 pppd[583]: write: Bad address (14)
Feb 11 10:48:31 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:3
Feb 11 10:48:42 udhcpc[728]: Sending discover…
Feb 11 10:48:44 udhcpc[728]: Sending discover…
Feb 11 10:48:48 udhcpc[728]: Sending discover…
Feb 11 10:49:01 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:4
Feb 11 10:49:01 pppd[583]: write: Bad address (14)
Feb 11 10:49:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:5
Feb 11 10:49:32 pppd[583]: write: Bad address (14)
Feb 11 10:49:52 udhcpc[728]: Sending discover…
Feb 11 10:49:54 udhcpc[728]: Sending discover…
Feb 11 10:49:58 udhcpc[728]: Sending discover…
Feb 11 10:50:02 pppd[583]: write: Bad address (14)
Feb 11 10:50:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:6
Feb 11 10:50:31 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:7
Feb 11 10:50:31 pppd[583]: write: Bad address (14)
Feb 11 10:51:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:8
Feb 11 10:51:02 pppd[583]: write: Bad address (14)
Feb 11 10:51:03 udhcpc[728]: Sending discover…
Feb 11 10:51:05 udhcpc[728]: Sending discover…
Feb 11 10:51:09 udhcpc[728]: Sending discover…
Feb 11 10:52:02 pppd[583]: write: Bad address (14)
Feb 11 10:52:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:10
Feb 11 10:52:13 udhcpc[728]: Sending discover…
Feb 11 10:52:15 udhcpc[728]: Sending discover…
Feb 11 10:52:19 udhcpc[728]: Sending discover…
Feb 11 10:52:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:11
Feb 11 10:52:32 pppd[583]: write: Bad address (14)
Feb 11 10:53:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:12
Feb 11 10:53:02 pppd[583]: write: Bad address (14)
Feb 11 10:53:23 udhcpc[728]: Sending discover…
Feb 11 10:53:25 udhcpc[728]: Sending discover…
Feb 11 10:53:29 udhcpc[728]: Sending discover…
Feb 11 10:53:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:13
Feb 11 10:53:32 pppd[583]: write: Bad address (14)
Feb 11 10:54:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:14
Feb 11 10:54:02 pppd[583]: write: Bad address (14)
Feb 11 10:54:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:15
Feb 11 10:54:32 pppd[583]: write: Bad address (14)
Feb 11 10:54:32 udhcpc[728]: Sending discover…
Feb 11 10:54:34 udhcpc[728]: Sending discover…
Feb 11 10:54:38 udhcpc[728]: Sending discover…
Feb 11 10:55:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:16
Feb 11 10:55:02 pppd[583]: write: Bad address (14)
Feb 11 10:55:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:17
Feb 11 10:55:32 pppd[583]: write: Bad address (14)
Feb 11 10:55:42 udhcpc[728]: Sending discover…
Feb 11 10:55:44 udhcpc[728]: Sending discover…
Feb 11 10:55:48 udhcpc[728]: Sending discover…
Feb 11 10:56:32 pppd[583]: write: Bad address (14)
Feb 11 10:56:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:19
Feb 11 10:56:52 udhcpc[728]: Sending discover…
Feb 11 10:56:54 udhcpc[728]: Sending discover…
Feb 11 10:56:58 udhcpc[728]: Sending discover…
Feb 11 10:57:31 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:21
Feb 11 10:57:31 pppd[583]: write: Bad address (14)
Feb 11 10:58:01 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:22
Feb 11 10:58:01 pppd[583]: write: Bad address (14)
Feb 11 10:58:02 udhcpc[728]: Sending discover…
Feb 11 10:58:04 udhcpc[728]: Sending discover…
Feb 11 10:58:08 udhcpc[728]: Sending discover…
Feb 11 10:58:31 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:23
Feb 11 10:58:31 pppd[583]: write: Bad address (14)
Feb 11 10:59:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:24
Feb 11 10:59:02 pppd[583]: write: Bad address (14)
Feb 11 10:59:13 udhcpc[728]: Sending discover…
Feb 11 10:59:15 udhcpc[728]: Sending discover…
Feb 11 10:59:19 udhcpc[728]: Sending discover…
Feb 11 11:00:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:26
Feb 11 11:00:02 pppd[583]: write: Bad address (14)
Feb 11 11:00:23 udhcpc[728]: Sending discover…
Feb 11 11:00:25 udhcpc[728]: Sending discover…
Feb 11 11:00:29 udhcpc[728]: Sending discover…
Feb 11 11:00:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:27
Feb 11 11:00:32 pppd[583]: write: Bad address (14)
Feb 11 11:01:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:28
Feb 11 11:01:02 pppd[583]: write: Bad address (14)
Feb 11 11:01:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:29
Feb 11 11:01:32 pppd[583]: write: Bad address (14)
Feb 11 11:01:33 udhcpc[728]: Sending discover…
Feb 11 11:01:35 udhcpc[728]: Sending discover…
Feb 11 11:01:39 udhcpc[728]: Sending discover…
Feb 11 11:02:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:30
Feb 11 11:02:02 pppd[583]: write: Bad address (14)
Feb 11 11:02:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:31
Feb 11 11:02:32 pppd[583]: write: Bad address (14)
Feb 11 11:02:42 udhcpc[728]: Sending discover…
Feb 11 11:02:44 udhcpc[728]: Sending discover…
Feb 11 11:02:48 udhcpc[728]: Sending discover…
Feb 11 11:03:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:32
Feb 11 11:03:02 pppd[583]: write: Bad address (14)
Feb 11 11:03:04 anweb[224]: check need_redirect started
Feb 11 11:03:04 anweb[224]: need_redirect: is defconf
Feb 11 11:03:04 anweb[225]: check need_redirect started
Feb 11 11:03:04 anweb[225]: need_redirect: is defconf
Feb 11 11:03:15 dms_etherwan_read[1545]: start
Feb 11 11:03:15 dms_get_etherwan_port[1545]: start
Feb 11 11:03:15 dms_get_etherwan_port[1545]: end: etherwan port 0
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: start 1
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: end
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: start
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: eth0.5: br0
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: start 2
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: end
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: start
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: eth0.4: br0
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: start 3
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: end
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: start
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: eth0.3: br0
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: start 4
Feb 11 11:03:15 dms_get_etherwan_port_info[1545]: end
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: start
Feb 11 11:03:15 get_gr_name_by_lan_key[1545]: eth0.2: br0
Feb 11 11:03:15 dms_etherwan_read[1545]: end
Feb 11 11:03:15 adsl_status[1552]: 1950
Feb 11 11:03:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:33
Feb 11 11:03:32 pppd[583]: write: Bad address (14)
Feb 11 11:03:52 udhcpc[728]: Sending discover…
Feb 11 11:03:54 udhcpc[728]: Sending discover…
Feb 11 11:03:58 udhcpc[728]: Sending discover…
Feb 11 11:04:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:34
Feb 11 11:04:02 pppd[583]: write: Bad address (14)
Feb 11 11:04:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:35
Feb 11 11:04:32 pppd[583]: write: Bad address (14)
Feb 11 11:05:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:36
Feb 11 11:05:02 pppd[583]: write: Bad address (14)
Feb 11 11:05:02 udhcpc[728]: Sending discover…
Feb 11 11:05:04 udhcpc[728]: Sending discover…
Feb 11 11:05:08 udhcpc[728]: Sending discover…
Feb 11 11:06:02 pppd[583]: write: Bad address (14)
Feb 11 11:06:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:38
Feb 11 11:06:13 udhcpc[728]: Sending discover…
Feb 11 11:06:15 udhcpc[728]: Sending discover…
Feb 11 11:06:19 udhcpc[728]: Sending discover…
Feb 11 11:06:32 pppd[583]: write: Bad address (14)
Feb 11 11:06:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:39
Feb 11 11:07:02 pppd[583]: write: Bad address (14)
Feb 11 11:07:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:40
Feb 11 11:07:23 udhcpc[728]: Sending discover…
Feb 11 11:07:25 udhcpc[728]: Sending discover…
Feb 11 11:07:29 udhcpc[728]: Sending discover…
Feb 11 11:07:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:41
Feb 11 11:07:32 pppd[583]: write: Bad address (14)
Feb 11 11:08:02 pppd[583]: write: Bad address (14)
Feb 11 11:08:02 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:42
Feb 11 11:08:32 kernel: in func<pppoe_rcv>, LCP reply send in protocol stack sid:32871, id:43
Feb 11 11:08:32 pppd[583]: write: Bad address (14)
Feb 11 11:08:33 udhcpc[728]: Sending discover…
Feb 11 11:08:35 udhcpc[728]: Sending discover…
Feb 11 11:08:39 udhcpc[728]: Sending discover..

Источник

OpenWrt Forum

Loading

Источник
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
Status
Not open for further replies.

  • #1

Hey fellas!
I have a problem with my D-Link DSL-224/R1 router. Basically the WAN connection is lost for 5~ minutes and then goes back up.
I’m not sure what causes it, but I’ve snooped this from the logs, connection is down from Aug 13 16:45:47 to Aug 13 16:49:36 :

Aug 13 16:36:58 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:27:dd:c7:7c:4c:ed:**:**:**:**
Aug 13 16:40:49 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:40:49 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:40:49 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:40:50 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:40:51 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:45:47 kernel: [ptm_event_detect]: Trigger PTM Rx reset event
Aug 13 16:45:47 kernel: ptm_event_detect: rx=1, tx=0
Aug 13 16:45:47 kernel: ptm_event_process: ptm reset
Aug 13 16:45:47 kernel: ptm_SwitchPHYIfEnable: PCRP5=0x1614200f
Aug 13 16:45:47 kernel: 0xb8a85040 :  1
Aug 13 16:45:47 kernel: ptm_timer_exit
Aug 13 16:45:47 kernel: PTM: disable IP e03ef6ab
Aug 13 16:45:47 kernel: PTM: enable IP f03ef6ab
Aug 13 16:45:47 kernel: ptm_timer_exit
Aug 13 16:45:47 kernel: idx=0, 1, ptm0_1, 0, 0, bc0f9adccdab
Aug 13 16:45:47 kernel: idx=1, 0, , 0, 0, 000000000000
Aug 13 16:45:48 kernel: ptm_timer_exit
Aug 13 16:45:48 kernel: Disable_SAR
Aug 13 16:45:48 pppd[1561]: Terminating on signal 15
Aug 13 16:45:48 pppd[1561]: lcp_close: unit:0, reason: "User request" (status: 5, state: 9, was_ip_down: 0)
Aug 13 16:45:48 pppd[1561]: Connect time 98.4 minutes.
Aug 13 16:45:48 pppd[1561]: Sent 2375290 bytes, received 499452356 bytes.
Aug 13 16:45:48 pppd[1561]: Down ppp with status (5)5
Aug 13 16:45:49 kernel: ==> peerDetectorStop .. (7 17)
Aug 13 16:45:55 pppd[1561]: Connection terminated.
Aug 13 16:45:55 pppd[1561]: Sent PADT
Aug 13 16:45:55 pppd[1561]: Modem hangup
Aug 13 16:45:55 pppd[1561]: lcp_close: unit:0, reason: "" (status: 5, state: 0, was_ip_down: 1)
Aug 13 16:45:55 pppd[1561]: Exit.(5)
Aug 13 16:45:55 kernel: _rtl865x_detachMasterNetif 429 ppp0
Aug 13 16:45:55 kernel: detach ppp0 success.
Aug 13 16:45:55 kernel: _rtl865x_eventHandle_delL2Fdb(283)
Aug 13 16:45:55 kernel: _rtl865x_detachMasterNetif 429 ppp0
Aug 13 16:45:55 stop_process_t[3299]: not found pid process 'igmpx'
Aug 13 16:45:56 kernel: ==> peerDetectorStop .. (9 61)
Aug 13 16:45:56 stop_process_t[3306]: not found pid process 'igmpx'
Aug 13 16:45:57 dms_reset_uptime[3306]: enter key ptm0_1
Aug 13 16:46:01 kernel: Start Phase 0: Vectored VDSL2 17A Discovery Phase...
Aug 13 16:46:20 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:46:20 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:46:21 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:46:23 kernel: Start Phase 1: VDSL2 Training Phase...
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:46:47 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:46:47 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:46:58 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:27:dd:c7:7c:4c:ed:**:**:**:**
Aug 13 16:47:15 conf_wan[3674]: CONFIG_ACTION_EDIT - start
Aug 13 16:47:15 conf_wan[3674]: key_l2_incoming = ptm0
Aug 13 16:47:15 conf_wan[3674]: test
Aug 13 16:47:15 conf_wan[3674]: max_count = 3
Aug 13 16:47:15 conf_wan[3674]: key_l3_incoming = ptm0_1
Aug 13 16:47:15 conf_wan[3674]: Get incoming L2 ptm0 from config
Aug 13 16:47:15 conf_wan[3674]:  ololo
Aug 13 16:47:15 conf_wan[3674]:  line 739
Aug 13 16:47:15 conf_wan[3674]:  line 771
Aug 13 16:47:15 conf_wan[3674]: Is it lan?
Aug 13 16:47:15 conf_wan[3674]: It's wan iface
Aug 13 16:47:15 conf_wan[3674]: Make edit old
Aug 13 16:47:15 conf_wan[3674]:  line 1088
Aug 13 16:47:15 conf_wan[3674]: 1096: l2_key=ptm0, l3_key=ptm0_1
Aug 13 16:47:15 conf_wan[3674]: 1099: stop old l3 with tunnels
Aug 13 16:47:15 conf_wan[3674]: 1103: L3 or Tunnel with gwif=true deleting detected
Aug 13 16:47:15 stop_process_t[3674]: not found pid process 'igmpx'
Aug 13 16:47:15 conf_wan[3674]: 1110
Aug 13 16:47:15 conf_wan[3674]: Renew search L3 ptm0_1
Aug 13 16:47:15 conf_wan[3674]: Delete link ptm0_1
Aug 13 16:47:15 conf_wan[3674]: Set link name ptm0_1
Aug 13 16:47:15 conf_wan[3674]: lets create ethernet
Aug 13 16:47:15 conf_wan[3674]: l2=ptm0 l3=ptm0_1
Aug 13 16:47:15 conf_wan[3674]: contype = ppp
Aug 13 16:47:15 conf_wan[3674]: old connection ptm0 - ptm0_1
Aug 13 16:47:15 kernel: smux_unregister_device remove smux dev ptm0_1
Aug 13 16:47:15 kernel: idx=0, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=1, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=2, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=3, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=4, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=5, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=6, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=7, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: ptm0_1 (): not using net_device_ops yet
Aug 13 16:47:16 kernel: idx=0, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=1, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=2, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=3, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=4, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=5, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=6, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=7, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=0, 1, ptm0_1, 0, 0, bc0f9adccdab
Aug 13 16:47:16 kernel: idx=0, 1, ptm0_1, 0, 0, bc0f9adccdab
Aug 13 16:47:16 conf_wan[3674]: ethernet created
Aug 13 16:47:16 kernel: ADDRCONF(NETDEV_UP): ptm0_1: link is not ready
Aug 13 16:47:17 conf_wan[3674]: L3 ethernet
Aug 13 16:47:17 conf_wan[3674]: Change mac or mtu on L2 iface ptm0 !!!
Aug 13 16:47:17 stop_process_t[3674]: not found pid process 'igmpx'
Aug 13 16:47:17 conf_wan[3674]: Change mac = or mtu=1500 !!!
Aug 13 16:47:17 conf_wan[3674]: CONFIG_ACTION_EDIT - exit
Aug 13 16:47:41 kernel: TIME_OUT (12 236) (16 17 0)
Aug 13 16:47:42 kernel: ==> peerDetectorStop .. (7 16)
Aug 13 16:47:49 kernel: ==> peerDetectorStop .. (9 62)
Aug 13 16:47:54 kernel: Start Phase 0: Vectored VDSL2 17A Discovery Phase...
Aug 13 16:48:19 kernel: Start Phase 1: VDSL2 Training Phase...
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:48:49 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:48:49 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:49:10 kernel: Start Phase 2: VDSL2 Exchange Phase...
Aug 13 16:49:18 kernel: Enter Showtime: TX 0,5759 / RX 0,65617 (kbps)
Aug 13 16:49:18 kernel: LoopLength(m)=400
Aug 13 16:49:24 kernel: ptm_timer_add
Aug 13 16:49:24 kernel: ADDRCONF(NETDEV_CHANGE): ptm0_1: link becomes ready
Aug 13 16:49:27 kernel: device ptm0_1 already exist.
Aug 13 16:49:27 stop_process_t[637]: not found pid process 'igmpx'
Aug 13 16:49:29 pppd[674]: Plugin /usr/lib/pppd/rp-pppoe.so loaded.
Aug 13 16:49:29 pppd[675]: pppd 2.4.4 started by admin, uid 0
Aug 13 16:49:36 pppd[675]: PPP session is 7809
Aug 13 16:49:36 pppd[675]: Used ACName = "43" in ppp(0)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:215
Aug 13 16:49:36 kernel: ,fid(0),mac(8c:90:d3:42:c5:48)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:218
Aug 13 16:49:36 kernel: _rtl865x_addPpp:215
Aug 13 16:49:36 kernel: ,fid(0),mac(8c:90:d3:42:c5:48)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:218
Aug 13 16:49:36 kernel: _rtl865x_addPpp:233
Aug 13 16:49:36 kernel: ,fid(0),mac(8c:90:d3:42:c5:48)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:236
Aug 13 16:49:36 pppd[675]: Using interface ppp0
Aug 13 16:49:36 pppd[675]: Connect: ppp0 <--> ptm0_1
Aug 13 16:49:37 pppd[675]: PAP authentication succeeded
Aug 13 16:49:37 pppd[675]: peer from calling number 8C:90:D3:42:C5:48 authorized
Aug 13 16:49:37 pppd[675]: local  IP address ***.***.***.***
Aug 13 16:49:37 pppd[675]: remote IP address ***.***.***.***
Aug 13 16:49:37 pppd[675]: primary   DNS address ***.***.***.***
Aug 13 16:49:37 pppd[675]: secondary DNS address ***.***.***.***
Aug 13 16:49:37 stop_process_t[756]: not found pid process 'igmpx'
Aug 13 16:56:58 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:27:dd:c7:7c:4c:ed:**:**:**:**

Note: not sure if MAC addresses are sensitive, so I changed them with asterisks (please notify me if I have exposed any sensitive information here, as I am quite new to administrating the router).

Does anyone know what exactly is «PTM Rx reset event» or what caused it? The connection is PPPoE based, PTM interface, using authorization, ADSL2+ enabled.
My router is connected properly, cables weren’t tampered with (the WAN exit goes to a microfilter that connects to a phone line exit on my wall — ADSL).
During the disconnect, I still had access to my router — suggesting LAN worked properly, and the status on the WAN port showed «cable disconnect» (or just disconnected).

Also, only 1 Ethernet and 2 Wifi devices are connected to the router. Does anyone knows how to solve this?

Last edited:

  • B

    bill001g

There is nothing you can really set in DSL part of the router. Anything you can actually change would make it not work at all or do nothing. The router will negotiate with the ISP equipment for the best connection speed possible. The ISP has some settings but it is on their end.

The router could be defective but you would have to blindly replace that. Your best bet is to call the ISP and they can run a test from their office. If they go everything is fine. Then maybe you blindly replace the router and when that doesn’t work you have them come out and actually test the line at your house.
Aug 9, 2012
27,157
2,380
123,140


  • #2

The mac address don’t matter because even though people think they are unique they really are not. The manufactures have large pools but if they had to be unique eventually we could not have any new computers. Duplicates are actually fairly common which most large companies that buy thousands of laptops at a time find out.
The one thing that is slightly sensitive is the local IP address that you did not block out. This likely changes sometimes when the DSL is reset. All a hacker could do is try to run denile of service attacks which does not get him any money so his time is better spent elsewhere.

This looks like the DSL is just going down. It is likely some issue with the ISP but you should check all your in house wiring to be sure nothing looks damaged.

  • #3

Thanks for the reply! I masked the IP addresses, too, just in case. So this is ISP related problem? not router or router configuration? We can rule out wiring, the router sits right in front of me, as well as the microfilter and the phone line exit on the wall.
Aug 9, 2012
27,157
2,380
123,140


  • #4

There is nothing you can really set in DSL part of the router. Anything you can actually change would make it not work at all or do nothing. The router will negotiate with the ISP equipment for the best connection speed possible. The ISP has some settings but it is on their end.

The router could be defective but you would have to blindly replace that. Your best bet is to call the ISP and they can run a test from their office. If they go everything is fine. Then maybe you blindly replace the router and when that doesn’t work you have them come out and actually test the line at your house.

  • #5

I see. I’ve talked to my ISP, they say they cannot really check the drop they detected since it will cause other clients to disconnect as well. They said it is an infrastructure problem, I have to contact a different company to check that instead.

  • #6

By the way, could it be because of IPv6 being enabled in the router? Or does it makes sense I have high ping (1200 — 600ms) after the DSL connection goes down?
Aug 9, 2012
27,157
2,380
123,140


  • #7

IPV6 can cause a different issue. Mostly you get strange errors with some but not all web sites. It does not cause the dsl to drop.

Just turn off the ipv6 support in your pc nic settings, it likely will not fix the problem but there is still almost nothing that requires IPv6 to function.

Most dsl connection fail becuase of errors on the connection. You will at times get longer pings as the router is trying to restablish the connection and is holding data in a buffer. What is sounds like is your ISP leases the phone lines from another isp,like the local phone company that actually owns the copper lines. This tends to be why even if it is slightly more expensive you buy your service directly from the company that owns the wires so they can’t play these silly games.

Can you actually call the other company yourself. Very technically you are not their customer your ISP is their customer. You do not pay them money directly.

  • #8

IPV6 can cause a different issue. Mostly you get strange errors with some but not all web sites. It does not cause the dsl to drop.

Just turn off the ipv6 support in your pc nic settings, it likely will not fix the problem but there is still almost nothing that requires IPv6 to function.

Most dsl connection fail becuase of errors on the connection. You will at times get longer pings as the router is trying to restablish the connection and is holding data in a buffer. What is sounds like is your ISP leases the phone lines from another isp,like the local phone company that actually owns the copper lines. This tends to be why even if it is slightly more expensive you buy your service directly from the company that owns the wires so they can’t play these silly games.

Can you actually call the other company yourself. Very technically you are not their customer your ISP is their customer. You do not pay them money directly.

Hi, thanks for answering!

Here, in my country, you have 2 separate company types or fields for network communications. One is your ISP, the other is referred to «infrastructure». My ISP just like most ISP’s gives me access to the internet, depending I have working infrastructure or (copper wires, phone exit and all of that). I pay them directly for 70-100 mbps connection.

The other company «infrastructure» actually owns the copper wires and down the path the fiber optics cables. I also pay them directly. They are in charge of the Telephone Switchboard which aggregates the copper wires from a building block down the road and then into the backbone — again this time with fiber optics cables for the backbone.

This is problematic since a customer like myself will often be playing Ping-Pong or table tennis, only this time as the ball, jumping between the two companies to try and get help resolving the issue. From what it seems, in a matter of a few years this will stop and every ISP in my country will merge with an infrastructure company. Right now, that’s not the case.

I’ve talked to the ISP, mainly, they just need to send me my PPPoE authentication details (which they did) and make sure to allocate to me our agreed upon speeds (70-100mbps down,
5-6mbps up). If I had an issue with them, I would assume it would be capped speeds (say 40mbps instead of 100) or maybe no connection at all (wrong details/ account status is inactive).

So they obviously referred me to the infrastructure company. Note, I have a deal with the ISP that covers them and the infrastructure company under the same bill. It’s a deal package, but it doesn’t help them communicate better with each other when issues like mine arise.

The infrastructure company sent a technician that didn’t do much, he connected to the Telephone Switchboard via his smartphone to monitor our line and I logged onto my router and we saw the line statistics matched, the router and the switchboard both had almost the same values for my internet down and up speeds. He said if they had a problem the whole block would have increased number of disconnects and they would issue a checkup on the switchboard themselves (which is not the case, apparently only my line drops daily).

The technician did replace a microfilter adapter to a normal phone line to ethernet cable, but after he left I had another disconnect or even two, later in the same evening.
His suggestion is that I rent a router from the infrastructure company. Even if the disconnects will occur, they will have much more information about the cause of the problem rather than only knowing there’s a problem which is the case with my personally owned router.

I’d suspect either company to deliberately disconnect me just to get me rent a router, but then what happens if I rent the router from the other company, which is not responsible for this allegation instead?
So I’m not sure. Currently my best options are:

  • Contacting D-Link technical support for my country (my router has active warranty).
  • Switching a router to infrastructure’s one, and if that don’t work then to ISP’s one.
  • Switching infrastructure company or ISP company.

These are sadly by far the least convenient solutions, but even if 1 of them will resolve this issue, I will be a happy man, surfing the web without interrupts.

  • #9

I have the exact same problem. Same router, same log, and same country I presume by your description.
However, the fact that this is the same router might be unrelated, because I got here by searching the exact log message «Trigger PTM Rx reset event».
Did you get it solved?

Status
Not open for further replies.

Similar threads

Timtom_121

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions

Источник

с чем может быть связана такая проблема:
Соединение разрзывается раз в сутки, но не переподключается автоматически.
Галочка keep alive стоит, но при переподключении висит на статусе «соединение», пока не нажмешь вручную «переподключить.»
в логах показывается следующее:
Dec 26 10:35:39 pppd[21713]: LCP terminated by peer
Dec 26 10:35:39 pppd[21713]: Connect time 1440.1 minutes.
Dec 26 10:35:39 miniupnpd[2604]: ioctl(s, SIOCGIFADDR, …): Cannot assign requested address
Dec 26 10:35:39 miniupnpd[2604]: Failed to get IP for interface ppp0
Dec 26 10:35:39 miniupnpd[2604]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 26 10:35:39 miniupnpd[2604]: ioctl(s, SIOCGIFADDR, …): Cannot assign requested address
Dec 26 10:35:39 miniupnpd[2604]: ioctl(s, SIOCGIFADDR, …): Cannot assign requested address
Dec 26 10:35:39 miniupnpd[2604]: ioctl(s, SIOCGIFADDR, …): Cannot assign requested address
Dec 26 10:35:39 miniupnpd[2604]: ioctl(s, SIOCGIFADDR, …): Cannot assign requested address
Dec 26 10:35:39 stop_process_t[9907]: not found pid process ‘igmpx’
Dec 26 10:35:42 pppd[21713]: Connection terminated.

модель роутера Dlink-825ACG1 прошивка стандартная официальная.

уже все настройки изковырял, и сбрасывал, не могу понять причину почему нет автоматического переподключения
PS звонок в техподдержку не помог, причину найти не смогли.

Источник
  • Remove From My Forums

  • Question

  • I tried to profile a dll in by my Azure cloud service using instrumentation method. My web site only support https. Originally I tried «VSPerfAspNetCmd» but it seems it does not support https, so I have to use «VSPerfAspCmd» however
    got «Error VSP1312: Process <PID> not found in list of active profile targets».

    I remotely login to the Azure VM, and then ran the following commands from the «x64» folder of the performance tools (Visual Studio 2015).

    1. Run «VSInstr <mydll>» to generate the instrumented dll in my site.

    2. Run «VSPerfCLREnv.cmd /traceon» and «VSPerfCLREnv.cmd /globaltraceon», and then restart the VM.

    I validated that the instrumented dll is correctly loaded by w3wp.exe process

    3. Run «VSPerfCmd.exe /start:trace /output:c:\myReport.vsp /cs /user:Everyone /ProcessOn:<PID of w3wp.exe>», but got error «Error VSP1312: Process <PID> not found in list of active profile targets».

    Note that «w3wp.exe» is running under user «NT Authority\Network Service» in session 0, but I am running the command with my own user name under a remote login session. That is the reason I specified «/user:Everyone» and «/cs»
    in the «VSPerfCmd.exe» command line above, but still got the error.

    Does anyone know the cause?

Answers

  • I’ve figured it out. Hope it is helpful to anyone who encountered the same issue.

    In step 3, remove «/processon:<pid>» but leave other options, this will just start the perf monitoring.

    Then after that, restart w3wp service and it will then be recognized by the perf monitor.

    You can verify that with «VsPerfCmd.exe /status» it will show «Number of Active Processes» as 1, and the w3wp.exe process and its thread will be also listed below.

    Now with option «/processon» or «/processoff», you can resume/pause the collection on a process. Keep in mind that «/processon» will resume a paused collection, not to start a new collection.

    — VsPerfCmd.exe /processon:<pid of w3wp>

    — VsPerfCmd.exe /processoff:<pid of w3wp>

    • Marked as answer by

      Monday, January 25, 2016 7:41 PM

Источник

Понравилась статья? Поделить с друзьями:
  • Normal mode focus 3 что означает ошибка
  • Not allowed to load local resource ошибка
  • Normal dotm ошибка word 2010
  • Not all variables bound oracle ошибка
  • Normacs ошибка 12029