Jump to content

ASUS RT-AC1200G+ restarty routera

Rate this topic


Guest house

Recommended Posts

Guest piotreek

Może ktoś na to spojrzeć? 

Jest sens cokolwiek jeszcze z tym robić, czy oddać ten szmelc do sklepu?

Spoiler

Dec 27 10:45:51 miniupnpd[370]: HTTP Connection from 192.168.1.169 closed unexpectedly
Dec 27 10:45:51 miniupnpd[370]: HTTP Connection from 192.168.1.169 closed unexpectedly
Dec 27 10:45:51 miniupnpd[370]: HTTP Connection from 192.168.1.169 closed unexpectedly
Dec 27 15:25:22 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:25:29 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:25:44 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:25:44 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:25:45 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:25:45 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:28:35 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:28:42 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:29:24 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 15:29:24 miniupnpd[370]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Dec 27 17:26:53 watchdog: restart httpd
Dec 27 17:26:53 rc_service: watchdog 214:notify_rc stop_httpd
Dec 27 17:26:54 rc_service: watchdog 214:notify_rc start_httpd
Dec 27 17:26:54 RT-AC1200G+: start httpd
Dec 28 05:05:04 watchdog: restart httpd
Dec 28 05:05:04 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 05:05:04 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 05:05:04 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 05:05:05 RT-AC1200G+: start httpd
Dec 28 05:06:05 watchdog: restart httpd
Dec 28 05:06:05 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 05:06:05 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 05:06:05 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 05:06:06 RT-AC1200G+: start httpd
Dec 28 05:07:36 watchdog: restart httpd
Dec 28 05:07:36 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 05:07:36 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 05:07:36 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 05:07:37 RT-AC1200G+: start httpd
Dec 28 05:08:04 rc_service: httpd 14731:notify_rc start_webs_update
Dec 28 07:08:57 syslogd started: BusyBox v1.17.4
Dec 28 07:08:57 kernel: klogd started: BusyBox v1.17.4 (2017-11-30 19:50:57 CST)
Dec 28 07:08:57 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Dec 28 07:08:58 miniupnpd[15027]: version 1.9 started
Dec 28 07:08:58 miniupnpd[15027]: HTTP listening on port 35260
Dec 28 07:08:58 miniupnpd[15027]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 28 07:08:58 miniupnpd[15027]: shutting down MiniUPnPd
Dec 28 07:08:58 miniupnpd[15030]: version 1.9 started
Dec 28 07:08:58 miniupnpd[15030]: HTTP listening on port 48213
Dec 28 07:08:58 miniupnpd[15030]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 28 07:08:59 hour monitor: daemon is starting
Dec 28 07:08:59 hour monitor: daemon terminates
Dec 28 07:09:12 watchdog: restart httpd
Dec 28 07:09:12 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 07:09:12 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 07:09:12 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 07:09:13 RT-AC1200G+: start httpd
Dec 28 07:09:43 watchdog: restart httpd
Dec 28 07:09:43 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 07:09:43 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 07:09:43 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 07:09:44 RT-AC1200G+: start httpd
Dec 28 07:10:28 rc_service: httpd 15043:notify_rc reboot
Dec 28 07:10:28 kernel: Attempt to kill tasklet from interrupt
Dec 28 07:10:30 iTunes: daemon is stoped
Dec 28 07:10:30 FTP Server: daemon is stoped
Dec 28 07:10:30 Samba Server: smb daemon is stoped
Dec 28 07:10:30 kernel: gro disabled
Feb 14 01:00:10 syslogd started: BusyBox v1.17.4
Feb 14 01:00:10 kernel: klogd started: BusyBox v1.17.4 (2017-11-30 19:50:57 CST)
Feb 14 01:00:10 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 PREEMPT Thu Nov 30 19:55:37 CST 2017
Feb 14 01:00:10 kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7f
Feb 14 01:00:10 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Feb 14 01:00:10 kernel: Machine: Northstar Prototype
Feb 14 01:00:10 kernel: Ignoring unrecognised tag 0x00000000
Feb 14 01:00:10 kernel: Memory policy: ECC disabled, Data cache writealloc
Feb 14 01:00:10 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Feb 14 01:00:10 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Feb 14 01:00:10 kernel: Memory: 125464k/125464k available, 5608k reserved, 0K highmem
Feb 14 01:00:10 kernel: Virtual kernel memory layout:
Feb 14 01:00:10 kernel:     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Feb 14 01:00:10 kernel:     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
Feb 14 01:00:10 kernel:     DMA     : 0xf7e00000 - 0xffe00000   ( 128 MB)
Feb 14 01:00:10 kernel:     vmalloc : 0x88800000 - 0xf0000000   (1656 MB)
Feb 14 01:00:10 kernel:     lowmem  : 0x80000000 - 0x88000000   ( 128 MB)
Feb 14 01:00:10 kernel:     modules : 0x7f000000 - 0x80000000   (  16 MB)
Feb 14 01:00:10 kernel:       .init : 0x80008000 - 0x80039000   ( 196 kB)
Feb 14 01:00:10 kernel:       .text : 0x80039000 - 0x803e5000   (3760 kB)
Feb 14 01:00:10 kernel:       .data : 0x803fe000 - 0x80420f40   ( 140 kB)
Feb 14 01:00:10 kernel: Mount-cache hash table entries: 512
Feb 14 01:00:10 kernel: Found ST compatible serial flash with 256 64KB blocks; total size 16MB
Feb 14 01:00:10 kernel: ACP (Accelerator Coherence Port) enabled
Feb 14 01:00:10 kernel: bio: create slab <bio-0> at 0
Feb 14 01:00:10 kernel: PCI: no core
Feb 14 01:00:10 kernel: PCI: no core
Feb 14 01:00:10 kernel: PCI: Fixing up bus 0
Feb 14 01:00:10 kernel: PCI: Fixing up bus 1
Feb 14 01:00:10 kernel: PCI: scanning bus 0 !!!
Feb 14 01:00:11 kernel: PCI: Fixing up bus 0
Feb 14 01:00:11 kernel: VFS: Disk quotas dquot_6.5.2
Feb 14 01:00:11 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 14 01:00:11 kernel: pflash: found no supported devices
Feb 14 01:00:11 kernel: bcmsflash: squash filesystem found at block 30
Feb 14 01:00:11 kernel: Creating 5 MTD partitions on "bcmsflash":
Feb 14 01:00:11 kernel: 0x000000000000-0x000000040000 : "boot"
Feb 14 01:00:11 kernel: 0x000000040000-0x000000ff0000 : "linux"
Feb 14 01:00:11 kernel: 0x0000001ef90c-0x000000e10000 : "rootfs"
Feb 14 01:00:11 kernel: 0x000000e10000-0x000000ff0000 : "jffs2"
Feb 14 01:00:11 kernel: 0x000000ff0000-0x000001000000 : "nvram"
Feb 14 01:00:11 kernel: === PPTP init ===
Feb 14 01:00:11 kernel: Registering the dns_resolver key type
Feb 14 01:00:11 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Feb 14 01:00:11 kernel: ctf: module license 'Proprietary' taints kernel.
Feb 14 01:00:11 kernel: Disabling lock debugging due to kernel taint
Feb 14 01:00:11 kernel: et_module_init: passivemode set to 0x0
Feb 14 01:00:11 kernel: et_module_init: txworkq set to 0x1
Feb 14 01:00:11 kernel: et_module_init: et_txq_thresh set to 0xce4
Feb 14 01:00:11 kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Feb 14 01:00:11 kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Feb 14 01:00:11 kernel: bcm_robo_enable_switch: EEE is disabled
Feb 14 01:00:11 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 kernel: wl_module_init: passivemode set to 0x0
Feb 14 01:00:11 kernel: wl_module_init: txworkq set to 0x1
Feb 14 01:00:11 kernel: PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
Feb 14 01:00:11 kernel: eth1: Broadcom BCM43227 802.11 Wireless Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 kernel: eth2: Broadcom BCM43c8 802.11 Wireless Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 nat: apply redirect rules
Feb 14 01:00:11 WAN Connection: ISP's DHCP did not function properly.
Feb 14 01:00:12 dnsmasq[204]: warning: no upstream servers configured
Feb 14 01:00:12 RT-AC1200G+: start httpd
Feb 14 01:00:13 syslog: Generating SSL certificate...
Feb 14 01:00:13 disk monitor: be idle
Feb 14 01:00:13 jffs2: valid logs(1)
Feb 14 01:00:13 hour monitor: daemon is starting
Feb 14 01:00:13 hour monitor: daemon terminates
Feb 14 01:00:13 miniupnpd[250]: version 1.9 started
Feb 14 01:00:13 miniupnpd[250]: HTTP listening on port 35001
Feb 14 01:00:13 miniupnpd[250]: Listening for NAT-PMP/PCP traffic on port 5351
Feb 14 01:00:14 syslog: module ledtrig-usbdev not found in modules.dep
Feb 14 01:00:14 syslog: module leds-usb not found in modules.dep
Feb 14 01:00:14 rc_service: udhcpc 252:notify_rc start_firewall
Feb 14 01:00:14 rc_service: udhcpc 252:notify_rc stop_upnp
Feb 14 01:00:14 rc_service: waitting "start_firewall" via udhcpc ...
Feb 14 01:00:15 kernel: SCSI subsystem initialized
Feb 14 01:00:17 WAN Connection: WAN was restored.
Feb 14 01:00:17 ntp: start NTP update
Dec 28 07:11:32 miniupnpd[250]: shutting down MiniUPnPd
Dec 28 07:11:33 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Dec 28 07:11:33 rc_service: ntp 270:notify_rc restart_upnp
Dec 28 07:11:33 rc_service: waitting "start_firewall" via udhcpc ...
Dec 28 07:11:34 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 28 07:11:34 kernel: nf_nat_rtsp v0.6.21 loading
Dec 28 07:11:34 miniupnpd[363]: version 1.9 started
Dec 28 07:11:34 miniupnpd[363]: HTTP listening on port 43266
Dec 28 07:11:34 miniupnpd[363]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 28 07:11:35 rc_service: udhcpc 252:notify_rc start_upnp
Dec 28 07:11:35 rc_service: waitting "stop_upnp" via udhcpc ...
Dec 28 07:11:35 miniupnpd[363]: shutting down MiniUPnPd
Dec 28 07:11:35 miniupnpd[365]: version 1.9 started
Dec 28 07:11:35 miniupnpd[365]: HTTP listening on port 43472
Dec 28 07:11:35 miniupnpd[365]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 28 07:11:36 rc_service: ntp 270:notify_rc restart_diskmon
Dec 28 07:11:36 miniupnpd[371]: MiniUPnPd is already running. EXITING
Dec 28 07:11:36 disk_monitor: Finish
Dec 28 07:11:37 dhcp client: bound 89.77.29.172 via 89.77.28.1 during 3600 seconds.
Dec 28 07:11:39 disk monitor: be idle
Dec 28 07:21:58 watchdog: restart httpd
Dec 28 07:21:58 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 07:21:58 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 07:21:58 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 07:21:59 RT-AC1200G+: start httpd
Dec 28 08:00:44 disk_monitor: Got SIGALRM...
Feb 14 01:00:10 syslogd started: BusyBox v1.17.4
Feb 14 01:00:10 kernel: klogd started: BusyBox v1.17.4 (2017-11-30 19:50:57 CST)
Feb 14 01:00:10 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 PREEMPT Thu Nov 30 19:55:37 CST 2017
Feb 14 01:00:10 kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7f
Feb 14 01:00:10 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Feb 14 01:00:10 kernel: Machine: Northstar Prototype
Feb 14 01:00:10 kernel: Ignoring unrecognised tag 0x00000000
Feb 14 01:00:10 kernel: Memory policy: ECC disabled, Data cache writealloc
Feb 14 01:00:10 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Feb 14 01:00:10 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Feb 14 01:00:10 kernel: Memory: 125464k/125464k available, 5608k reserved, 0K highmem
Feb 14 01:00:10 kernel: Virtual kernel memory layout:
Feb 14 01:00:10 kernel:     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Feb 14 01:00:10 kernel:     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
Feb 14 01:00:10 kernel:     DMA     : 0xf7e00000 - 0xffe00000   ( 128 MB)
Feb 14 01:00:10 kernel:     vmalloc : 0x88800000 - 0xf0000000   (1656 MB)
Feb 14 01:00:10 kernel:     lowmem  : 0x80000000 - 0x88000000   ( 128 MB)
Feb 14 01:00:10 kernel:     modules : 0x7f000000 - 0x80000000   (  16 MB)
Feb 14 01:00:10 kernel:       .init : 0x80008000 - 0x80039000   ( 196 kB)
Feb 14 01:00:10 kernel:       .text : 0x80039000 - 0x803e5000   (3760 kB)
Feb 14 01:00:10 kernel:       .data : 0x803fe000 - 0x80420f40   ( 140 kB)
Feb 14 01:00:10 kernel: Mount-cache hash table entries: 512
Feb 14 01:00:10 kernel: Found ST compatible serial flash with 256 64KB blocks; total size 16MB
Feb 14 01:00:10 kernel: ACP (Accelerator Coherence Port) enabled
Feb 14 01:00:10 kernel: bio: create slab <bio-0> at 0
Feb 14 01:00:10 kernel: PCI: no core
Feb 14 01:00:10 kernel: PCI: no core
Feb 14 01:00:10 kernel: PCI: Fixing up bus 0
Feb 14 01:00:10 kernel: PCI: Fixing up bus 1
Feb 14 01:00:10 kernel: PCI: scanning bus 0 !!!
Feb 14 01:00:11 kernel: PCI: Fixing up bus 0
Feb 14 01:00:11 kernel: VFS: Disk quotas dquot_6.5.2
Feb 14 01:00:11 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 14 01:00:11 kernel: pflash: found no supported devices
Feb 14 01:00:11 kernel: bcmsflash: squash filesystem found at block 30
Feb 14 01:00:11 kernel: Creating 5 MTD partitions on "bcmsflash":
Feb 14 01:00:11 kernel: 0x000000000000-0x000000040000 : "boot"
Feb 14 01:00:11 kernel: 0x000000040000-0x000000ff0000 : "linux"
Feb 14 01:00:11 kernel: 0x0000001ef90c-0x000000e10000 : "rootfs"
Feb 14 01:00:11 kernel: 0x000000e10000-0x000000ff0000 : "jffs2"
Feb 14 01:00:11 kernel: 0x000000ff0000-0x000001000000 : "nvram"
Feb 14 01:00:11 kernel: === PPTP init ===
Feb 14 01:00:11 kernel: Registering the dns_resolver key type
Feb 14 01:00:11 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Feb 14 01:00:11 kernel: ctf: module license 'Proprietary' taints kernel.
Feb 14 01:00:11 kernel: Disabling lock debugging due to kernel taint
Feb 14 01:00:11 kernel: et_module_init: passivemode set to 0x0
Feb 14 01:00:11 kernel: et_module_init: txworkq set to 0x1
Feb 14 01:00:11 kernel: et_module_init: et_txq_thresh set to 0xce4
Feb 14 01:00:11 kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Feb 14 01:00:11 kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Feb 14 01:00:11 kernel: bcm_robo_enable_switch: EEE is disabled
Feb 14 01:00:11 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 kernel: wl_module_init: passivemode set to 0x0
Feb 14 01:00:11 kernel: wl_module_init: txworkq set to 0x1
Feb 14 01:00:11 kernel: PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
Feb 14 01:00:11 kernel: eth1: Broadcom BCM43227 802.11 Wireless Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 kernel: eth2: Broadcom BCM43c8 802.11 Wireless Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 kernel: [dump prev ops] from 87000000, local len(1403)
Feb 14 01:00:11 kernel: _ Reboot message ... _______________________________________________________
Feb 14 01:00:12 kernel: <0>Kernel panic - not syncing: Out of memory: system-wide panic_on_oom is enabled
Feb 14 01:00:12 kernel: <0>
Feb 14 01:00:12 kernel: <4>[<8003f734>] (unwind_backtrace+0x0/0xf8) from [<803000a8>] (panic+0x7c/0x1a4)
Feb 14 01:00:12 kernel: <4>[<803000a8>] (panic+0x7c/0x1a4) from [<80092164>] (out_of_memory+0x2c8/0x328)
Feb 14 01:00:12 kernel: <4>[<80092164>] (out_of_memory+0x2c8/0x328) from [<800953ec>] (__alloc_pages_nodemask+0x66c/0x694)
Feb 14 01:00:12 kernel: <4>[<800953ec>] (__alloc_pages_nodemask+0x66c/0x694) from [<8009712c>] (__do_page_cache_readahead+0x140/0x2d0)
Feb 14 01:00:12 kernel: <4>[<8009712c>] (__do_page_cache_readahead+0x140/0x2d0) from [<8009756c>] (ra_submit+0x28/0x30)
Feb 14 01:00:12 kernel: <4>[<8009756c>] (ra_submit+0x28/0x30) from [<8008f6fc>] (filemap_fault+0x42c/0x454)
Feb 14 01:00:12 nat: apply redirect rules
Feb 14 01:00:12 kernel: <4>[<8008f6fc>] (filemap_fault+0x42c/0x454) from [<800a4288>] (__do_fault.clone.60+0x54/0x4c8)
Feb 14 01:00:12 kernel: <4>[<800a4288>] (__do_fault.clone.60+0x54/0x4c8) from [<800a78f0>] (handle_mm_fault+0x114/0x934)
Feb 14 01:00:12 kernel: <4>[<800a78f0>] (handle_mm_fault+0x114/0x934) from [<80040d90>] (do_page_fault+0x178/0x1ec)
Feb 14 01:00:12 kernel: <4>[<80040d90>] (do_page_fault+0x178/0x1ec) from [<80039298>] (do_PrefetchAbort+0x30/0x9c)
Feb 14 01:00:12 kernel: <4>[<80039298>] (do_PrefetchAbort+0x30/0x9c) from [<803c0840>] (ret_from_exception+0x0/0x10)
Feb 14 01:00:12 kernel: <4>Exception stack(0x8531bfb0 to 0x8531bff8)
Feb 14 01:00:12 kernel: <4>bfa0:                                     00000000 00000000 00000258 000f4240
Feb 14 01:00:12 kernel: <4>bfc0: 00000000 7eadad30 000123dc 000000a2 00000000 000123f4 0000012b 000123f8
Feb 14 01:00:12 kernel: <4>bfe0: 2ac50de8 7eadad08 2ac46ee4 2ac6e890 60000010 ffffffff
Feb 14 01:00:12 kernel: <0>Rebooting in 3 seconds..
Feb 14 01:00:12 kernel: ____________________________________________________________________________
Feb 14 01:00:12 WAN Connection: ISP's DHCP did not function properly.
Feb 14 01:00:12 dnsmasq[204]: warning: no upstream servers configured
Feb 14 01:00:12 RT-AC1200G+: start httpd
Feb 14 01:00:13 disk monitor: be idle
Feb 14 01:00:13 jffs2: valid logs(1)
Feb 14 01:00:13 hour monitor: daemon is starting
Feb 14 01:00:13 hour monitor: daemon terminates
Feb 14 01:00:13 miniupnpd[244]: version 1.9 started
Feb 14 01:00:13 miniupnpd[244]: HTTP listening on port 47261
Feb 14 01:00:13 miniupnpd[244]: Listening for NAT-PMP/PCP traffic on port 5351
Feb 14 01:00:14 syslog: module ledtrig-usbdev not found in modules.dep
Feb 14 01:00:14 syslog: Generating SSL certificate...
Feb 14 01:00:14 syslog: module leds-usb not found in modules.dep
Feb 14 01:00:14 rc_service: udhcpc 247:notify_rc start_firewall
Feb 14 01:00:14 kernel: SCSI subsystem initialized
Feb 14 01:00:15 rc_service: udhcpc 247:notify_rc stop_upnp
Feb 14 01:00:15 rc_service: waitting "start_firewall" via udhcpc ...
Feb 14 01:00:17 WAN Connection: WAN was restored.
Feb 14 01:00:18 ntp: start NTP update
Dec 28 19:17:56 miniupnpd[244]: shutting down MiniUPnPd
Dec 28 19:17:56 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Dec 28 19:17:56 rc_service: ntp 270:notify_rc restart_upnp
Dec 28 19:17:56 rc_service: waitting "start_firewall" via udhcpc ...
Dec 28 19:17:58 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 28 19:17:58 kernel: nf_nat_rtsp v0.6.21 loading
Dec 28 19:17:58 rc_service: udhcpc 247:notify_rc start_upnp
Dec 28 19:17:58 rc_service: waitting "stop_upnp" via udhcpc ...
Dec 28 19:17:58 miniupnpd[363]: version 1.9 started
Dec 28 19:17:58 miniupnpd[363]: HTTP listening on port 48498
Dec 28 19:17:58 miniupnpd[363]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 28 19:17:58 miniupnpd[363]: shutting down MiniUPnPd
Dec 28 19:17:59 miniupnpd[365]: version 1.9 started
Dec 28 19:17:59 miniupnpd[365]: HTTP listening on port 37285
Dec 28 19:17:59 miniupnpd[365]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 28 19:17:59 rc_service: ntp 270:notify_rc restart_diskmon
Dec 28 19:18:00 disk_monitor: Finish
Dec 28 19:18:00 miniupnpd[371]: MiniUPnPd is already running. EXITING
Dec 28 19:18:01 dhcp client: bound 89.77.29.172 via 89.77.28.1 during 131020 seconds.
Dec 28 19:18:01 disk monitor: be idle
Dec 28 20:00:06 disk_monitor: Got SIGALRM...
Dec 28 21:03:56 watchdog: restart httpd
Dec 28 21:03:56 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 21:03:56 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 21:03:56 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 21:03:57 RT-AC1200G+: start httpd
Dec 28 21:04:57 watchdog: restart httpd
Dec 28 21:04:57 rc_service: watchdog 214:notify_rc stop_httpd
Dec 28 21:04:57 rc_service: watchdog 214:notify_rc start_httpd
Dec 28 21:04:57 rc_service: waitting "stop_httpd" via watchdog ...
Dec 28 21:04:58 RT-AC1200G+: start httpd

 

Link to post
Share on other sites
  • Replies 11
  • Created
  • Last Reply

Top Posters In This Topic

  • house

    4

Top Posters In This Topic

  • Administrator

@piotreek wyłącz upnp, korzystasz z tego w jakimś konkretnym celu ? Częste te restarty ?

Link to post
Share on other sites

@piotreek ja jestem dwa dni po aktualizacji do najnowszej wersji i nadal mam puste logi. Dodam tylko, że mam włączone UPNP (w sieci mam NAS) oraz włączonych w sposób ciągły 10 urządzeń (LAN /wifi) oraz inne włączane okresowo. W sumie 25 urządzeń. Patrząc na logi zastanawia mnie częste występowanie watchdog'a. Używam jedynie pasma 2.4 GHz. 5GHz nie jest mi potrzebne. Obciążenie pamięci obecnie jest 38%.

Link to post
Share on other sites
  • Administrator

@piotreek starą sprawdzoną metodę - reset do ustawień fabrycznych i ustawienie wszystkiego od nowa - przerabiałeś ?

52 minuty temu, piotreek napisał:

kupę coś lepszego. 

co lepszego za te pieniądze ?

Link to post
Share on other sites

@house nie. Powiem tak, mam ten router prawie 1,5 roku. Miałem duże problemy z restartami, jak chyba większość. Przed wgraniem przedostatniego fw (ten co zniknął ze strony ASUS) zrobiłem czyszczenie metodą 4x 30 sekund. To było we wrześniu. Tamten fw miał błędy w GUI, ale poza tym bug wszystko było ok, stabilność 100%. Po wgraniu najnowszego fw (zwykła aktualizacja poprzez stronę) błędy w GUI zniknęły a co do stabilności to zobaczę. Obecnie często sprawdzam i logi mam całkowicie puste. 

Edited by agar
Link to post
Share on other sites
  • Administrator

@piotreek zgłoś na RMA, może felerna sztuka Ci się przytrafiła

Link to post
Share on other sites
  • Administrator
Temat został zamknięty jako rozwiązany.

W przypadku jakichkolwiek pytań lub wątpliwości proszę użyć funkcji "Zgłoś odpowiedź". 

Link to post
Share on other sites
Guest
This topic is now closed to further replies.
  • Similar Content

    • RSK
      By RSK
      Witam.
       
      Czy posiadając router ASUS-a (np. GT-AC5300 lub podobny) oraz stały adres IP można router ustawić tak aby na podłączonym telewizorze oglądać Netflixa z USA ?
    • Greg Marsden
      By Greg Marsden
      Witam wszystkich?
      Od wczoraj posiadam router AX88U, póki co na fabrycznym oprogramowaniu, a rzuciło mi się w oczy spore użycie RAMu oscylujące na poziomie 750-950MB.
      Takie wartości są praktycznie na stałe, z podłączonym dyskiem zewnętrznym 2TB i np. przy zalogowanej jednej komórce, bez innych obciążeń. Czy takie
      obciążenie może wskazywać na jakiś problem, czy to nic dziwnego ? Przesiadłem się z Asusa RT-N18U, gdzie z 256MB Ramu zazwyczaj w użyciu była połowa przy
      takim samym obciążeniu. 
       
    • Borg
      By Borg
      Witam - 5 lat temu jeszcze na starym forum znalazłem recenzję @house Ausua RT-AC87U a ponieważ wcześniej miałem starszego RT z tomato więc 87 wylądowała u mnie. Minęło 5 lat, ostatnio podniosłem światełko do 600/60 Mbps i zonk. Na 10 pomiarów - 7 mam w granicach 450/60 (po kablu) przy czym w trakcie pomiaru za pomocą np. www.speedtest.net tracę sesję www z panelem administracyjnym routera na kilka sekund i po takim "restarcie" kolejny pomiar mam już 600/60. Do tej pory miałem łącze 200/50 więc nie wiem czy to wcześniej już występowało, czy AC87 już się powoli kończy (pracuje w dosyć trudnych warunkach, co prawda stoi na podstawce chłodzącej od laptopa ale w pawlaczu i w lato zdarzały się temperatury 80-90 stopni). Obecnie ma wgranego Merlina 384.13_10, obsługuje około 20 urządzeń (home office, szkoła, streaming 2k, gry online, reguły dla 11 latka ?  ) - miejsce zbrodni mieszkanie w cegle z dość zaśmieconym wifi.
      Miałem ochotę spróbować  Synology RT2600AC ale po przejrzeniu tematów i ewentualnym niedługim porzuceniem wsparcia dałem spokój, na polu bitwy zostały : ASUS RT-AX88U bo znam ten ekosystem i ma wifi 6 na pokładzie oraz swego czasu chwalony przez @house UBIQUITI UniFi DM - jedno co w nim przeszkadza mi to brak wifi 6 no i ostatnie posty house że coś im się tam zaczyna psuć szlifowanie softu dla DM - tylko pytanie na jakim poziomie jest to "psucie" czy to jest na poziomie Asusa i czy jeszcze gorzej. 
      Idea jest taka chcę na kolejne 5 lat mieć spokój z tym łączem i szybszym przy mocno obciążającymi użyszkodnikami domowymi ?.  Raczej nie planuję dokładać dodatkowych AP więc zasięg na mieszkanie powinien być na poziomie obecnego RT-AC87U którego i tak muszę przycinać bo zdarza mi się 50 metrów od domu w samochodzie łapać swoje wifi :).  Pytanie jak to z tymi wifi 6 - w sumie na razie nie widzę na rynku szturmy w kartach sieciowych i urządzeniach mobilnych, bardziej zależałoby mi na bezpieczeństwie, nie śledziłem jak się w końcu z WPA3 czy innym szyfrowaniem tematy rozwinęły.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, please see ours Guidelines and Privacy Policy.