Penecho
DD-WRT Novice
Joined: 29 Jun 2019
Posts: 2
|
 Posted: Sat Jun 29, 2019 12:26 Post subject: DIR-615 permanent restarts |
 |
Hi guys,
I have a DIR-615 D1 with the latest Firmware and since like 1 week or so the router seems to restart/hang every couple of minutes...
DHCP Type = forwarder
(Router from ISP --> DIR-615 --> Network Switch --> PCs)
I have no clue why and also from the log files I can not read any useful information:
| Code: |
Jan 1 00:40:22 192.168.0.2 user info bridge : interface ra0 successfully added to bridge br0
Jan 1 00:40:28 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:40:28 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:40:28 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:40:28 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:40:28 192.168.0.2 user info process_monitor : daemon successfully stopped
Jan 1 00:40:28 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:40:28 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:40:29 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:40:29 192.168.0.2 user info cron : daemon successfully stopped
Jan 1 00:40:29 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:40:29 192.168.0.2 cron info cron[3013] (CRON) STARTUP (fork ok)
Jan 1 00:40:31 192.168.0.2 user info httpd : daemon successfully stopped
Jan 1 00:40:31 192.168.0.2 daemon info httpd[779] httpd : httpd server shutdown
Jan 1 00:40:31 192.168.0.2 daemon info httpd[3015] httpd : httpd server started at port 80
Jan 1 00:42:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:42:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:44:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:44:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:46:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:46:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:48:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:48:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:50:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:50:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:52:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:52:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:54:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:54:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:56:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:56:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:58:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:58:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:00:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:00:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:04:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:04:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:12:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:12:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:14:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:14:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:16:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:16:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:18:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:18:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:20:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:20:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:22:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:22:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:24:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:24:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:26:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:26:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:28:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:28:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:30:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:30:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:32:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:32:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:34:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:34:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:36:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:36:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:38:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:38:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:40:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:40:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:42:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:42:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:44:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:44:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:46:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:46:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:48:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:48:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:50:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:50:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:52:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:52:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:54:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:54:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:56:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:56:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 01:58:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 01:58:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:00:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:00:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:04:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:04:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:12:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:12:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:14:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:14:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:16:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:16:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:18:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:18:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:20:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:20:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:22:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:22:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:24:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:24:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:26:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:26:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:28:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:28:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:30:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:30:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:32:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:32:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:34:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:34:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:36:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:36:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:38:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:38:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:40:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:40:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:42:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:42:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:44:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:44:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:46:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:46:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:48:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:48:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:50:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:50:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:52:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:52:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:54:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:54:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:56:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:56:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 02:58:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 02:58:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:00:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:00:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:04:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:04:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:12:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:12:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:14:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:14:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:16:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:16:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:18:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:18:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:20:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:20:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:22:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:22:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:24:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:24:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:26:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:26:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:28:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:28:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:30:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:30:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:32:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:32:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:34:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:34:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:36:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:36:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:38:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:38:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:40:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:40:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:42:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:42:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:44:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:44:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:46:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:46:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:48:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:48:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:50:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:50:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:52:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:52:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 03:54:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 03:54:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[631] (CRON) STARTUP (fork ok)
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[758] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:09:40 192.168.0.2 daemon err httpd[763] Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 00:09:54 192.168.0.2 daemon err httpd[763] Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:12:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:12:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:14:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:14:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:16:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:16:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:17:34 192.168.0.2 daemon err httpd[763] Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 00:18:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:18:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:20:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:20:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:22:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:22:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[760] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[625] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[758] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[627] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[625] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 user info httpd : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[761] httpd : httpd server started at port 80
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[761] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[627] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[760] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[627] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[760] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[760] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[627] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[758] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[627] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:12:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:12:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:14:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:14:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:16:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:16:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:18:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:18:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:20:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:20:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:22:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:22:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:24:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:24:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[760] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 user info httpd : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[771] httpd : httpd server started at port 80
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:10:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:12:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:12:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[626] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[758] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[757] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[625] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 user info httpd : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[762] httpd : httpd server shutdown
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[763] httpd : httpd server started at port 80
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
|
I have deactivated the NTP since the router couldn't connect to the IP anyways.
You can see clearly in the logs that whe the time starts to count from the beginning again, it did reset itself...
Does anyone by any chance can read anything useful from the Logs? |
|
Penecho
DD-WRT Novice
Joined: 29 Jun 2019
Posts: 2
|
| Posted: Sat Jun 29, 2019 14:59 Post subject: |
|
Could this also be a heat Problem, since currently it's very hot here atm. Temperature in the house is arounf 30 degrees celsius (86 Fahreheit). Maybe the router is overheating and rebooting?
But what is also weird, that when it happens in the night, it sometimes keeps hanging until I manually power on/off it. So there is literally no internet access from like midnight until I restart the router in the morning.
Edit:
I also enabled the klog now and it mentiones the BusyBox:
| Code: |
Jan 1 00:00:16 192.168.0.2 daemon info httpd[761] httpd : httpd server started at port 80
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:04:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:06:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:08:00 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info telnetd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info syslogd : daemon successfully started
Jan 1 00:00:14 192.168.0.2 user info cron : daemon successfully started
Jan 1 00:00:14 192.168.0.2 cron info cron[627] (CRON) STARTUP (fork ok)
Jan 1 00:00:14 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:00:15 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info wland : daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:00:16 192.168.0.2 user info process_monitor : successfully started
Jan 1 00:00:16 192.168.0.2 daemon info httpd[757] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon info httpd[760] httpd : httpd server started at port 80
Jan 1 00:00:16 192.168.0.2 daemon crit httpd[760] can't bind to any address
Jan 1 00:00:16 192.168.0.2 user info resetbutton : daemon successfully stopped
Jan 1 00:00:16 192.168.0.2 user info resetbutton : resetbutton daemon successfully started
Jan 1 00:02:00 192.168.0.2 user info dhcpfwd : maybe died, we need to re-exec it
Jan 1 00:02:01 192.168.0.2 user info dhcpfwd : dhcp forwarder daemon successfully started
Jan 1 00:02:31 192.168.0.2 user info dnsmasq : daemon successfully stopped
Jan 1 00:02:31 192.168.0.2 user info telnetd : daemon successfully stopped
Jan 1 00:02:31 192.168.0.2 user info syslogd : syslog daemon successfully stopped
Jan 1 00:02:31 192.168.0.2 user info pptpd : daemon successfully stopped
Jan 1 00:02:31 192.168.0.2 user info dnsmasq : daemon successfully started
Jan 1 00:02:31 192.168.0.2 user info klogd : daemon successfully started
Jan 1 00:02:31 192.168.0.2 kern notice kernel klogd started: BusyBox v1.29.3 (2018-10-10 15:42:26 CEST)
Jan 1 00:02:31 192.168.0.2 kern notice kernel Linux version 3.2.102 (root@linux) (gcc version 7.1.0 (LEDE GCC 7.1.0 r4137-89c615c691) ) #6212 Wed Oct 10 15:42:11 CEST 2018
Jan 1 00:02:31 192.168.0.2 kern debug kernel prom: fw_arg0=00000001, fw_arg1=01f5bfb0, fw_arg2=01f5c3b0, fw_arg3=00000000
Jan 1 00:02:31 192.168.0.2 kern debug kernel argv[0]= (null) is invalid, skipping
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[0]: memsize=32
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[1]: initrd_start=0x00000000
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[2]: initrd_size=0x0
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[3]: flash_start=0xBF000000
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[4]: flash_size=0x400000
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[0]: memsize=32
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[1]: initrd_start=0x00000000
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[2]: initrd_size=0x0
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[3]: flash_start=0xBF000000
Jan 1 00:02:31 192.168.0.2 kern debug kernel env[4]: flash_size=0x400000
Jan 1 00:02:31 192.168.0.2 kern info kernel bootconsole [early0] enabled
Jan 1 00:02:31 192.168.0.2 kern info kernel CPU revision is: 0001964c (MIPS 24KEc)
Jan 1 00:02:31 192.168.0.2 kern info kernel Ralink RT3052 id:1 rev:2 running at 384.00 MHz
Jan 1 00:02:31 192.168.0.2 kern info kernel Determined physical RAM map:
Jan 1 00:02:31 192.168.0.2 kern info kernel memory: 02000000 @ 00000000 (usable)
Jan 1 00:02:31 192.168.0.2 kern warning kernel Zone PFN ranges:
Jan 1 00:02:31 192.168.0.2 kern warning kernel Normal 0x00000000 -> 0x00002000
Jan 1 00:02:31 192.168.0.2 kern warning kernel Movable zone start PFN for each node
Jan 1 00:02:31 192.168.0.2 kern warning kernel early_node_map[1] active PFN ranges
Jan 1 00:02:31 192.168.0.2 kern warning kernel 0: 0x00000000 -> 0x00002000
Jan 1 00:02:31 192.168.0.2 kern debug kernel On node 0 totalpages: 8192
Jan 1 00:02:31 192.168.0.2 kern debug kernel free_area_init_node: node 0, pgdat 8022a6d0, node_mem_map 81000000
Jan 1 00:02:31 192.168.0.2 kern debug kernel Normal zone: 64 pages used for memmap
Jan 1 00:02:31 192.168.0.2 kern debug kernel Normal zone: 0 pages reserved
Jan 1 00:02:31 192.168.0.2 kern debug kernel Normal zone: 8128 pages, LIFO batch:0
Jan 1 00:02:31 192.168.0.2 kern debug kernel pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Jan 1 00:02:31 192.168.0.2 kern debug kernel pcpu-alloc: [0] 0
Jan 1 00:02:31 192.168.0.2 kern warning kernel Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Jan 1 00:02:31 192.168.0.2 kern notice kernel Kernel command line: console=ttyS1,57600n8 root=/dev/mtdblock4 rootfstype=squashfs noinitrd
Jan 1 00:02:31 192.168.0.2 kern info kernel PID hash table entries: 128 (order: -3, 512 bytes)
Jan 1 00:02:31 192.168.0.2 kern info kernel Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 00:02:31 192.168.0.2 kern info kernel Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jan 1 00:02:31 192.168.0.2 kern warning kernel Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Jan 1 00:02:31 192.168.0.2 kern warning kernel Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
Jan 1 00:02:31 192.168.0.2 kern info kernel Writing ErrCtl register=00016408
Jan 1 00:02:31 192.168.0.2 kern info kernel Readback ErrCtl register=00016408
Jan 1 00:02:31 192.168.0.2 kern info kernel Memory: 29876k/32768k available (1990k kernel code, 2892k reserved, 282k data, 156k init, 0k highmem)
Jan 1 00:02:31 192.168.0.2 kern info kernel NR_IRQS:48
Jan 1 00:02:31 192.168.0.2 kern info kernel console [ttyS1] enabled, bootconsole disabled
Jan 1 00:02:31 192.168.0.2 kern info kernel Calibrating delay loop... 255.59 BogoMIPS (lpj=1277952)
Jan 1 00:02:31 192.168.0.2 kern info kernel pid_max: default: 32768 minimum: 301
Jan 1 00:02:31 192.168.0.2 kern info kernel Mount-cache hash table entries: 512
Jan 1 00:02:31 192.168.0.2 kern info kernel NET: Registered protocol family 16
Jan 1 00:02:31 192.168.0.2 kern info kernel bio: create slab <bio-0> at 0
Jan 1 00:02:31 192.168.0.2 kern info kernel Switching to clocksource MIPS
Jan 1 00:02:31 192.168.0.2 kern info kernel NET: Registered protocol family 2
Jan 1 00:02:31 192.168.0.2 kern info kernel IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP established hash table entries: 1024 (order: 1, 8192 bytes)
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP: Hash tables configured (established 1024 bind 1024)
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP reno registered
Jan 1 00:02:31 192.168.0.2 kern info kernel UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 00:02:31 192.168.0.2 kern info kernel UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 00:02:31 192.168.0.2 kern info kernel NET: Registered protocol family 1
Jan 1 00:02:31 192.168.0.2 kern info kernel squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan 1 00:02:31 192.168.0.2 kern info kernel msgmni has been set to 58
Jan 1 00:02:31 192.168.0.2 kern info kernel io scheduler noop registered
Jan 1 00:02:31 192.168.0.2 kern info kernel io scheduler deadline registered (default)
Jan 1 00:02:31 192.168.0.2 kern info kernel Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Jan 1 00:02:31 192.168.0.2 kern info kernel serial8250: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
Jan 1 00:02:31 192.168.0.2 kern info kernel serial8250: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
Jan 1 00:02:31 192.168.0.2 kern warning kernel Ralink gpio driver initialized
Jan 1 00:02:31 192.168.0.2 kern info kernel system type: RT3052
Jan 1 00:02:31 192.168.0.2 kern info kernel boot type: 0
Jan 1 00:02:31 192.168.0.2 kern notice kernel ralink flash device: 0x1000000 at 0xbf000000
Jan 1 00:02:31 192.168.0.2 kern info kernel Ralink SoC physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x0022f9
Jan 1 00:02:31 192.168.0.2 kern debug kernel Ralink SoC physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
Jan 1 00:02:31 192.168.0.2 kern debug kernel Ralink SoC physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Jan 1 00:02:31 192.168.0.2 kern debug kernel Ralink SoC physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
Jan 1 00:02:31 192.168.0.2 kern info kernel Amd/Fujitsu Extended Query Table at 0x0040
Jan 1 00:02:31 192.168.0.2 kern info kernel Amd/Fujitsu Extended Query version 1.1.
Jan 1 00:02:31 192.168.0.2 kern notice kernel number of CFI chips: 1
Jan 1 00:02:31 192.168.0.2 kern emerg kernel found squashfs at 11B000
Jan 1 00:02:31 192.168.0.2 kern notice kernel Creating 6 MTD partitions on "Ralink SoC physically mapped flash":
Jan 1 00:02:31 192.168.0.2 kern notice kernel 0x000000000000-0x000000030000 : "uboot"
Jan 1 00:02:31 192.168.0.2 kern notice kernel 0x000000030000-0x000000040000 : "uboot-config"
Jan 1 00:02:31 192.168.0.2 kern notice kernel 0x000000040000-0x000000050000 : "factory-defaults"
Jan 1 00:02:31 192.168.0.2 kern notice kernel 0x000000050000-0x0000003f0000 : "linux"
Jan 1 00:02:31 192.168.0.2 kern notice kernel 0x00000011b000-0x0000003f0000 : "rootfs"
Jan 1 00:02:31 192.168.0.2 kern warning kernel mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan 1 00:02:31 192.168.0.2 kern notice kernel 0x0000003f0000-0x000000400000 : "nvram"
Jan 1 00:02:31 192.168.0.2 kern info kernel PPP generic driver version 2.4.2
Jan 1 00:02:31 192.168.0.2 kern info kernel PPP BSD Compression module registered
Jan 1 00:02:31 192.168.0.2 kern info kernel PPP Deflate Compression module registered
Jan 1 00:02:31 192.168.0.2 kern info kernel PPP MPPE Compression module registered
Jan 1 00:02:31 192.168.0.2 kern info kernel NET: Registered protocol family 24
Jan 1 00:02:31 192.168.0.2 kern info kernel Ralink APSoC Hardware Watchdog Timer
Jan 1 00:02:31 192.168.0.2 kern info kernel u32 classifier
Jan 1 00:02:31 192.168.0.2 kern info kernel Performance counters on
Jan 1 00:02:31 192.168.0.2 kern info kernel Actions configured
Jan 1 00:02:31 192.168.0.2 kern info kernel Netfilter messages via NETLINK v0.30.
Jan 1 00:02:31 192.168.0.2 kern info kernel nf_conntrack version 0.5.0 (466 buckets, 1864 max)
Jan 1 00:02:31 192.168.0.2 kern info kernel ctnetlink v0.93: registering with nfnetlink.
Jan 1 00:02:31 192.168.0.2 kern info kernel IPv4 over IPv4 tunneling driver
Jan 1 00:02:31 192.168.0.2 kern info kernel ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:02:31 192.168.0.2 kern info kernel IPP2P v0.8.2 loading
Jan 1 00:02:31 192.168.0.2 kern info kernel ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP bic registered
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP cubic registered
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP westwood registered
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP highspeed registered
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP hybla registered
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP htcp registered
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP vegas registered
Jan 1 00:02:31 192.168.0.2 kern info kernel TCP scalable registered
Jan 1 00:02:31 192.168.0.2 kern info kernel NET: Registered protocol family 17
Jan 1 00:02:31 192.168.0.2 kern notice kernel Bridge firewalling registered
Jan 1 00:02:31 192.168.0.2 kern info kernel 8021q: 802.1Q VLAN Support v1.8
Jan 1 00:02:31 192.168.0.2 kern info kernel searching for nvram
Jan 1 00:02:31 192.168.0.2 kern info kernel nvram size = 0
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRH -- : 0x0000000c
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRL -- : 0x43305277
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRH -- : 0x0000000c
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRL -- : 0x43305277
Jan 1 00:02:31 192.168.0.2 kern warning kernel Ralink APSoC Ethernet Driver Initilization. v2.0 256 rx/tx descriptors allocated, mtu = 1500!
Jan 1 00:02:31 192.168.0.2 kern warning kernel NAPI enable, Tx Ring = 256, Rx Ring = 256
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRH -- : 0x0000000c
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRL -- : 0x43305277
Jan 1 00:02:31 192.168.0.2 kern warning kernel rt3052 access driver initialization.
Jan 1 00:02:31 192.168.0.2 kern info kernel VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Jan 1 00:02:31 192.168.0.2 kern info kernel Freeing unused kernel memory: 156k freed
Jan 1 00:02:31 192.168.0.2 kern info kernel Started WatchDog Timer.
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRH -- : 0x00000026
Jan 1 00:02:31 192.168.0.2 kern warning kernel MAC_ADRL -- : 0x5a44cda0
Jan 1 00:02:31 192.168.0.2 kern warning kernel phy_tx_ring = 0x014c9000, tx_ring = 0xa14c9000
Jan 1 00:02:31 192.168.0.2 kern warning kernel phy_rx_ring0 = 0x01f32000, rx_ring0 = 0xa1f32000
Jan 1 00:02:31 192.168.0.2 kern warning kernel RT305x_ESW: Link Status Changed
Jan 1 00:02:31 192.168.0.2 kern warning kernel CDMA_CSG_CFG = 81000007
Jan 1 00:02:31 192.168.0.2 kern warning kernel GDMA1_FWD_CFG = 710000
Jan 1 00:02:31 192.168.0.2 kern warning kernel RT305x_ESW: Link Status Changed
Jan 1 00:02:31 192.168.0.2 kern info kernel device br0 entered promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern warning kernel RT305x_ESW: Link Status Changed
Jan 1 00:02:31 192.168.0.2 kern info kernel device vlan1 entered promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern info kernel device eth2 entered promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern info kernel device vlan2 entered promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 2(vlan2) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 2(vlan2) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 1(vlan1) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 1(vlan1) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel device br0 left promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern info kernel device br0 entered promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern info kernel device br0 left promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern warning kernel rt2860v2_ap: module license 'unspecified' taints kernel.
Jan 1 00:02:31 192.168.0.2 kern warning kernel Disabling lock debugging due to kernel taint
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 2(vlan2) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 1(vlan1) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern warning kernel 0x1300 = 00064380
Jan 1 00:02:31 192.168.0.2 kern warning kernel 0x1300 = 00064380
Jan 1 00:02:31 192.168.0.2 kern info kernel device ra0 entered promiscuous mode
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 3(ra0) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 3(ra0) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 3(ra0) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern warning kernel 0x1300 = 00064380
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 3(ra0) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 3(ra0) entering forwarding state
Jan 1 00:02:31 192.168.0.2 kern alert kernel fast-classifier: starting up
Jan 1 00:02:31 192.168.0.2 kern alert kernel fast-classifier: registered
Jan 1 00:02:31 192.168.0.2 kern info kernel br0: port 3(ra0) entering forwarding state
Jan 1 00:02:32 192.168.0.2 user info klogd : kernel log daemon successfully stopped
Jan 1 00:02:32 192.168.0.2 kern notice kernel klogd: exiting
Jan 1 00:02:32 192.168.0.2 user info syslogd : syslog daemon successfully stopped
Jan 1 00:02:32 192.168.0.2 kern notice kernel klogd started: BusyBox v1.29.3 (2018-10-10 15:42:26 CEST)
|
|
|
