D-link DIR-825 keeps automatically rebooting at random times

J

Jonntra_Volta

Member
Joined
May 2, 2020
Messages
23
Reaction score
0
Router: D-link DIR-825
Hardware version: R1

Hi there,

2 weeks ago I signed up for Fibre witih Afrihost. A day after receiving and connecting my router, I noticed that it automatically reboots at random times every 1-3 (sometimes 3) days. I went through all the usual steps like factory resetting the router, which didn't work, after which Afrihost sent me a brand new router. Now, after 3 days of using the new router, the automatic reboot issue started again. Today it rebooted 3 times.

I read online that disabling the auto uplink speed in the QoS settings fixes this issue, however, the DIR-825's issued by Afrihost doesn't seem to have this setting.

Also, my firmware version is v1.0.0. which is the latest version.

Any indication as to what might be causing this?
 
Jonntra_Volta said:
Router: D-link DIR-825
Hardware version: R1

Hi there,

2 weeks ago I signed up for Fibre witih Afrihost. A day after receiving and connecting my router, I noticed that it automatically reboots at random times every 1-3 (sometimes 3) days. I went through all the usual steps like factory resetting the router, which didn't work, after which Afrihost sent me a brand new router. Now, after 3 days of using the new router, the automatic reboot issue started again. Today it rebooted 3 times.

I read online that disabling the auto uplink speed in the QoS settings fixes this issue, however, the DIR-825's issued by Afrihost doesn't seem to have this setting.

Also, my firmware version is v1.0.0. which is the latest version.

Any indication as to what might be causing this?
Click to expand...

The lastest firmware says Version 3.0.0 Here http://ftp.dlink.ru/pub/Router/DIR-825/Firmware/RevR1/

In your logs what does it say just before it reboots.

You could be cusing a boot loop and its getting overloaded and rebooting.
 
Rickster said:
The lastest firmware says Version 3.0.0 Here http://ftp.dlink.ru/pub/Router/DIR-825/Firmware/RevR1/

In your logs what does it say just before it reboots.

You could be cusing a boot loop and its getting overloaded and rebooting.
Click to expand...

I updated the firmware to 3.0.0 last night (and then an auto update happened to 3.0.1) but the automatic reboot just happened again now.

I'm not familiar with checking the logs. I know where to view it but I'm not sure what I'm looking at. Any indication of what to look for?
 
Jonntra_Volta said:
I updated the firmware to 3.0.0 last night (and then an auto update happened to 3.0.1) but the automatic reboot just happened again now.

I'm not familiar with checking the logs. I know where to view it but I'm not sure what I'm looking at. Any indication of what to look for?
Click to expand...

Something like this i guess:

Code: 
May  2 12:03:06 kernel: wlan1: (Home Network) Deauth sent to f0:0f:ec:71:6f:7f Reason: 4-Way Handshake timeout[15]
May  2 12:03:06 kernel: wlan1: A STA is rejected by 802.1x daemon - F0:0F:EC:71:6F:7F
May  2 12:03:06 kernel: wlan1: (Home Network) Deauth sent to bc:85:56:48:9a:99 Reason: 4-Way Handshake timeout[15]
May  2 12:03:06 kernel: wlan1: A STA is rejected by 802.1x daemon - BC:85:56:48:9A:99
May  2 12:15:24 kernel: wlan1: A wireless client is associated - F0:0F:EC:71:6F:7F
May  2 12:15:24 kernel: wlan1: (Home Network) STA: f0:0f:ec:71:6f:7f Status: Successful[0]
May  2 12:15:24 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 12:15:24 kernel: wlan1: A wireless client is associated - F0:0F:EC:71:6F:7F
May  2 12:15:24 kernel: wlan1: Open and authenticated
May  2 12:35:07 kernel: wlan1: (Home Network) Disassoc received from ac:07:5f:81:e4:b8 Reason: Leaving (or has left) BSS[8]
May  2 12:35:07 kernel: wlan1: A wireless client is disassociated - AC:07:5F:81:E4:B8
May  2 12:36:24 kernel: wlan1: A STA is deleted by application program - 98:9C:57:52:84:D6
May  2 12:56:45 kernel: wlan1: A wireless client is associated - DC:F7:56:10:FB:1A
May  2 12:56:45 kernel: wlan1: (Home Network) STA: dc:f7:56:10:fb:1a Status: Successful[0]
May  2 12:56:45 kernel: wlan0: A STA is deleted by application program - DC:F7:56:10:FB:1A
May  2 12:56:45 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 12:56:45 kernel: wlan1: A wireless client is associated - DC:F7:56:10:FB:1A
May  2 12:56:45 kernel: wlan1: Open and authenticated
May  2 12:56:54 kernel: wlan1: Delete MC entry not found!
May  2 13:13:42 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:13:42 kernel: wlan1: (Home Network) STA: d0:c5:f3:2a:a5:c2 Status: Successful[0]
May  2 13:13:42 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 13:13:42 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:13:42 kernel: wlan1: Open and authenticated
May  2 13:17:27 kernel: wlan1: A STA is deleted by application program - D0:C5:F3:2A:A5:C2
May  2 13:48:20 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:48:20 kernel: wlan1: (Home Network) STA: d0:c5:f3:2a:a5:c2 Status: Successful[0]
May  2 13:48:20 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 13:48:20 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:48:20 kernel: wlan1: Open and authenticated
May  2 13:52:06 kernel: wlan1: Delete MC entry not found!
May  2 13:57:47 kernel: wlan1: A STA is deleted by application program - D0:C5:F3:2A:A5:C2
May  2 14:00:48 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 14:00:48 kernel: wlan1: (Home Network) STA: d0:c5:f3:2a:a5:c2 Status: Successful[0]
May  2 14:00:48 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 14:00:48 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 14:00:48 kernel: wlan1: Open and authenticated
May  2 14:01:58 kernel: wlan1: Delete MC entry not found!
May  2 14:01:58 kernel: wlan1: Delete MC entry not found!
May  2 14:04:18 kernel: [RTL_NIC]: LAN1 is down!
May  2 14:04:22 kernel: wlan1: A wireless client is associated - 98:9C:57:52:84:D6
May  2 14:04:22 kernel: wlan1: (Home Network) STA: 98:9c:57:52:84:d6 Status: Successful[0]
May  2 14:04:22 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 14:04:22 kernel: wlan1: A wireless client is associated - 98:9C:57:52:84:D6
May  2 14:04:22 kernel: wlan1: Open and authenticated
May  2 14:04:22 kernel: [RTL_NIC]: LAN1 is up! 1000full
May  2 14:04:26 kernel: wlan1: A wireless client is associated - F0:79:60:11:35:18
May  2 14:04:26 kernel: wlan1: (Home Network) STA: f0:79:60:11:35:18 Status: Successful[0]
May  2 14:04:26 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 14:04:26 kernel: wlan1: A wireless client is associated - F0:79:60:11:35:18
May  2 14:04:26 kernel: wlan1: Open and authenticated
May  2 14:04:32 kernel: [RTL_NIC]: LAN1 is down!
May  2 14:04:35 kernel: [RTL_NIC]: LAN1 is up! 1000full
May  2 14:04:55 kernel: wlan0: A wireless client is associated - 7C:2A:31:21:DC:20
May  2 14:04:55 kernel: wlan0: (Home Network) STA: 7c:2a:31:21:dc:20 Status: Successful[0]
May  2 14:04:55 kernel: wlan0: WPA2-AES PSK authentication in progress...
May  2 14:04:55 kernel: wlan0: A wireless client is associated - 7C:2A:31:21:DC:20
May  2 14:04:55 kernel: wlan0: Open and authenticated
May  2 14:04:58 kernel: wlan1: A STA is deleted by application program - D0:C5:F3:2A:A5:C2
 
Rickster said:
Something like this i guess:

Code: 
May  2 12:03:06 kernel: wlan1: (Home Network) Deauth sent to f0:0f:ec:71:6f:7f Reason: 4-Way Handshake timeout[15]
May  2 12:03:06 kernel: wlan1: A STA is rejected by 802.1x daemon - F0:0F:EC:71:6F:7F
May  2 12:03:06 kernel: wlan1: (Home Network) Deauth sent to bc:85:56:48:9a:99 Reason: 4-Way Handshake timeout[15]
May  2 12:03:06 kernel: wlan1: A STA is rejected by 802.1x daemon - BC:85:56:48:9A:99
May  2 12:15:24 kernel: wlan1: A wireless client is associated - F0:0F:EC:71:6F:7F
May  2 12:15:24 kernel: wlan1: (Home Network) STA: f0:0f:ec:71:6f:7f Status: Successful[0]
May  2 12:15:24 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 12:15:24 kernel: wlan1: A wireless client is associated - F0:0F:EC:71:6F:7F
May  2 12:15:24 kernel: wlan1: Open and authenticated
May  2 12:35:07 kernel: wlan1: (Home Network) Disassoc received from ac:07:5f:81:e4:b8 Reason: Leaving (or has left) BSS[8]
May  2 12:35:07 kernel: wlan1: A wireless client is disassociated - AC:07:5F:81:E4:B8
May  2 12:36:24 kernel: wlan1: A STA is deleted by application program - 98:9C:57:52:84:D6
May  2 12:56:45 kernel: wlan1: A wireless client is associated - DC:F7:56:10:FB:1A
May  2 12:56:45 kernel: wlan1: (Home Network) STA: dc:f7:56:10:fb:1a Status: Successful[0]
May  2 12:56:45 kernel: wlan0: A STA is deleted by application program - DC:F7:56:10:FB:1A
May  2 12:56:45 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 12:56:45 kernel: wlan1: A wireless client is associated - DC:F7:56:10:FB:1A
May  2 12:56:45 kernel: wlan1: Open and authenticated
May  2 12:56:54 kernel: wlan1: Delete MC entry not found!
May  2 13:13:42 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:13:42 kernel: wlan1: (Home Network) STA: d0:c5:f3:2a:a5:c2 Status: Successful[0]
May  2 13:13:42 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 13:13:42 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:13:42 kernel: wlan1: Open and authenticated
May  2 13:17:27 kernel: wlan1: A STA is deleted by application program - D0:C5:F3:2A:A5:C2
May  2 13:48:20 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:48:20 kernel: wlan1: (Home Network) STA: d0:c5:f3:2a:a5:c2 Status: Successful[0]
May  2 13:48:20 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 13:48:20 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 13:48:20 kernel: wlan1: Open and authenticated
May  2 13:52:06 kernel: wlan1: Delete MC entry not found!
May  2 13:57:47 kernel: wlan1: A STA is deleted by application program - D0:C5:F3:2A:A5:C2
May  2 14:00:48 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 14:00:48 kernel: wlan1: (Home Network) STA: d0:c5:f3:2a:a5:c2 Status: Successful[0]
May  2 14:00:48 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 14:00:48 kernel: wlan1: A wireless client is associated - D0:C5:F3:2A:A5:C2
May  2 14:00:48 kernel: wlan1: Open and authenticated
May  2 14:01:58 kernel: wlan1: Delete MC entry not found!
May  2 14:01:58 kernel: wlan1: Delete MC entry not found!
May  2 14:04:18 kernel: [RTL_NIC]: LAN1 is down!
May  2 14:04:22 kernel: wlan1: A wireless client is associated - 98:9C:57:52:84:D6
May  2 14:04:22 kernel: wlan1: (Home Network) STA: 98:9c:57:52:84:d6 Status: Successful[0]
May  2 14:04:22 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 14:04:22 kernel: wlan1: A wireless client is associated - 98:9C:57:52:84:D6
May  2 14:04:22 kernel: wlan1: Open and authenticated
May  2 14:04:22 kernel: [RTL_NIC]: LAN1 is up! 1000full
May  2 14:04:26 kernel: wlan1: A wireless client is associated - F0:79:60:11:35:18
May  2 14:04:26 kernel: wlan1: (Home Network) STA: f0:79:60:11:35:18 Status: Successful[0]
May  2 14:04:26 kernel: wlan1: WPA2-AES PSK authentication in progress...
May  2 14:04:26 kernel: wlan1: A wireless client is associated - F0:79:60:11:35:18
May  2 14:04:26 kernel: wlan1: Open and authenticated
May  2 14:04:32 kernel: [RTL_NIC]: LAN1 is down!
May  2 14:04:35 kernel: [RTL_NIC]: LAN1 is up! 1000full
May  2 14:04:55 kernel: wlan0: A wireless client is associated - 7C:2A:31:21:DC:20
May  2 14:04:55 kernel: wlan0: (Home Network) STA: 7c:2a:31:21:dc:20 Status: Successful[0]
May  2 14:04:55 kernel: wlan0: WPA2-AES PSK authentication in progress...
May  2 14:04:55 kernel: wlan0: A wireless client is associated - 7C:2A:31:21:DC:20
May  2 14:04:55 kernel: wlan0: Open and authenticated
May  2 14:04:58 kernel: wlan1: A STA is deleted by application program - D0:C5:F3:2A:A5:C2
Click to expand...

Here's my most recent logs:

May 2 15:14:32 ip_is_up[1070]: eth1 speed: 1000M Full
May 2 15:14:32 igmpx[1302]: active route 239.255.255.250 changed source from 192.168.0.104 to 192.168.0.175
May 2 15:14:32 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 192.168.0.175
May 2 15:14:38 igmpx[1302]: added membership for 224.0.1.187 on upstream #0 102.182.112.122
May 2 15:14:38 igmpx[1302]: added new route 224.0.1.187: 102.182.112.122 -> 192.168.0.1
May 2 15:14:38 igmpx[1302]: route 224.0.1.187 on upstream #0 activated with 192.168.0.175
May 2 15:14:47 igmpx[1302]: active route 239.255.255.250 changed source from 192.168.0.175 to 169.1.211.141
May 2 15:14:47 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 169.1.211.141
May 2 15:15:13 kernel: wlan1: A wireless client is associated - E4:A7:C5:DD:D0:0E
May 2 15:15:13 kernel: wlan1: (Family SSHZ Fibre) STA: e4:a7:c5:dd:d0:0e Status: Successful[0]
May 2 15:15:13 kernel: wlan1: WPA2-AES PSK authentication in progress...
May 2 15:15:13 kernel: wlan1: A wireless client is associated - E4:A7:C5:DD:D0:0E
May 2 15:15:13 kernel: wlan1: Open and authenticated
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPDISCOVER(br0) e4:a7:c5:dd:d0:0e
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPOFFER(br0) 192.168.0.134 e4:a7:c5:dd:d0:0e
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPREQUEST(br0) 192.168.0.134 e4:a7:c5:dd:d0:0e
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPACK(br0) 192.168.0.134 e4:a7:c5:dd:d0:0e HUAWEI_P_smart-48fdf6cea7
May 2 15:15:13 dnsmasq-dhcp[994]: not giving name localhost.Dlink to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1
May 2 15:15:13 dnsmasq-dhcp[994]: not giving name localhost to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1
May 2 15:16:33 igmpx[1302]: active route 239.255.255.250 changed source from 169.1.211.141 to 192.168.0.1
May 2 15:16:33 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 192.168.0.1
May 2 15:17:49 igmpx[1302]: leave group 224.0.1.187 from 192.168.0.175
May 2 15:19:44 igmpx[1302]: active route 239.255.255.250 changed source from 192.168.0.1 to 192.168.0.134
May 2 15:19:44 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 192.168.0.134
May 2 15:20:05 igmpx[1302]: leave group 239.255.255.250 from 192.168.0.134
May 2 15:20:05 igmpx[1302]: leave group 224.0.0.251 from 192.168.0.134
May 2 15:20:47 kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.


It rebooted automatically 3 times in the last 20-30 minutes.
 
Jonntra_Volta said:
Here's my most recent logs:

May 2 15:14:32 ip_is_up[1070]: eth1 speed: 1000M Full
May 2 15:14:32 igmpx[1302]: active route 239.255.255.250 changed source from 192.168.0.104 to 192.168.0.175
May 2 15:14:32 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 192.168.0.175
May 2 15:14:38 igmpx[1302]: added membership for 224.0.1.187 on upstream #0 102.182.112.122
May 2 15:14:38 igmpx[1302]: added new route 224.0.1.187: 102.182.112.122 -> 192.168.0.1
May 2 15:14:38 igmpx[1302]: route 224.0.1.187 on upstream #0 activated with 192.168.0.175
May 2 15:14:47 igmpx[1302]: active route 239.255.255.250 changed source from 192.168.0.175 to 169.1.211.141
May 2 15:14:47 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 169.1.211.141
May 2 15:15:13 kernel: wlan1: A wireless client is associated - E4:A7:C5:DD:D0:0E
May 2 15:15:13 kernel: wlan1: (Family SSHZ Fibre) STA: e4:a7:c5:dd:d0:0e Status: Successful[0]
May 2 15:15:13 kernel: wlan1: WPA2-AES PSK authentication in progress...
May 2 15:15:13 kernel: wlan1: A wireless client is associated - E4:A7:C5:DD:D0:0E
May 2 15:15:13 kernel: wlan1: Open and authenticated
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPDISCOVER(br0) e4:a7:c5:dd:d0:0e
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPOFFER(br0) 192.168.0.134 e4:a7:c5:dd:d0:0e
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPREQUEST(br0) 192.168.0.134 e4:a7:c5:dd:d0:0e
May 2 15:15:13 dnsmasq-dhcp[994]: DHCPACK(br0) 192.168.0.134 e4:a7:c5:dd:d0:0e HUAWEI_P_smart-48fdf6cea7
May 2 15:15:13 dnsmasq-dhcp[994]: not giving name localhost.Dlink to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1
May 2 15:15:13 dnsmasq-dhcp[994]: not giving name localhost to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1
May 2 15:16:33 igmpx[1302]: active route 239.255.255.250 changed source from 169.1.211.141 to 192.168.0.1
May 2 15:16:33 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 192.168.0.1
May 2 15:17:49 igmpx[1302]: leave group 224.0.1.187 from 192.168.0.175
May 2 15:19:44 igmpx[1302]: active route 239.255.255.250 changed source from 192.168.0.1 to 192.168.0.134
May 2 15:19:44 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 192.168.0.134
May 2 15:20:05 igmpx[1302]: leave group 239.255.255.250 from 192.168.0.134
May 2 15:20:05 igmpx[1302]: leave group 224.0.0.251 from 192.168.0.134
May 2 15:20:47 kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.


It rebooted automatically 3 times in the last 20-30 minutes.
Click to expand...

Here's some more over the last few minutes:

May 2 15:26:35 igmpx[1302]: active route 239.255.255.250 changed source from 192.168.0.134 to 169.1.246.18
May 2 15:26:35 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 169.1.246.18
May 2 15:27:13 dnsmasq-dhcp[994]: DHCPREQUEST(br0) 192.168.0.105 ac:e2:d3:07:82:9d
May 2 15:27:13 dnsmasq-dhcp[994]: Ignoring domain ant.amazon.com for DHCP host name MININT-I42PLI8
May 2 15:27:13 dnsmasq-dhcp[994]: DHCPACK(br0) 192.168.0.105 ac:e2:d3:07:82:9d MININT-I42PLI8
May 2 15:27:13 dnsmasq-dhcp[994]: not giving name localhost.Dlink to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1
May 2 15:27:13 dnsmasq-dhcp[994]: not giving name localhost to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1
May 2 15:27:13 dnsmasq-dhcp[994]: DHCPSOLICIT(br0) 00:01:00:01:24:2f:0e:21:ac:e2:d3:07:82:9d
May 2 15:27:13 dnsmasq-dhcp[994]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:24:2f:0e:21:ac:e2:d3:07:82:9d
May 2 15:27:51 igmpx[1302]: active route 239.255.255.250 changed source from 169.1.246.18 to 192.168.0.105
May 2 15:27:51 igmpx[1302]: route 239.255.255.250 on upstream #0 activated with 192.168.0.105
May 2 15:27:51 igmpx[1302]: leave group 224.0.0.251 from 192.168.0.105
 
May 2 15:27:13 dnsmasq-dhcp[994]: not giving name localhost.Dlink to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1

Could it be this? That IP address is my TV.
 
When pasting in the logs go insert as code.

3 little buttons near the smiley face when you replying.

You also need to provide exact times when it does reboot.
 
Rickster said:
When pasting in the logs go insert as code.

3 little buttons near the smiley face when you replying.

You also need to provide exact times when it does reboot.
Click to expand...

The automatic reboot happened again now at 21:23, so I went to check the logs, and its like all historical logs are wiped. The logs only starts at 21:34, which is when I logged in to check it:

Code: 
May  2 21:34:24 syslogd started: BusyBox v1.26.2
May  2 21:34:24 kernel: klogd started: BusyBox v1.26.2 (2019-09-16 12:59:18 MSK)
May  2 21:34:25 syslog: libmtd (_mtd_write_ex): to "/dev/mtd2", size: 0x18dc, offset: 0x0, buffer: 0x444980
May  2 21:34:25 syslog: libmtd (_mtd_write_ex): to "/dev/mtd2", size: 0x18dc, offset: 0x8000, buffer: 0x444980
May  2 21:35:01 syslog: libmtd (_mtd_write_ex): to "/dev/mtd2", size: 0x18dd, offset: 0x0, buffer: 0x444980
May  2 21:35:02 syslog: libmtd (_mtd_write_ex): to "/dev/mtd2", size: 0x18dd, offset: 0x8000, buffer: 0x444980
 
Jonntra_Volta said:
May 2 15:27:13 dnsmasq-dhcp[994]: not giving name localhost.Dlink to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1

Could it be this? That IP address is my TV.
Click to expand...

By the way, I fixed this and the reboots still happen.
 
Unplug all devices except for your Wan cable from the CPE and see what happens, also disconnect all wireless devices.
 
Rickster said:
Unplug all devices except for your Wan cable from the CPE and see what happens, also disconnect all wireless devices.
Click to expand...

So you mean I have to disconnect all devices from the internet? The thing is, the reboots happens sometimes every 5-10 minutes, and other times it reboots every 2-3 days. I can't go 2-3 days without being connected, as I work from home.

Also, the reboots happened on a day when no devices were connected to the router via WAN (only 2 phones via WiFi).
 
Jonntra_Volta said:
May 2 15:27:13 dnsmasq-dhcp[994]: not giving name localhost.Dlink to the DHCP lease of 192.168.0.175 because the name exists in /tmp/hosts with address 127.0.0.1

Could it be this? That IP address is my TV.
Click to expand...
A Samsung?

How did you fix it?
 
Rickster said:
Unplug all devices except for your Wan cable from the CPE and see what happens, also disconnect all wireless devices.
Click to expand...

It happened again now. Again, its like the logs reset and there's nothing from before the router rebooted. Here are the logs after the router came back on again:

Code: 
May  3 11:04:12 ip_is_up[1074]: eth1 speed: 1000M Full
May  3 11:06:03 dnsmasq-dhcp[999]: DHCPSOLICIT(br0) 00:01:00:01:24:2f:0e:21:ac:e2:d3:07:82:9d
May  3 11:06:03 dnsmasq-dhcp[999]: DHCPREQUEST(br0) 192.168.0.105 ac:e2:d3:07:82:9d
May  3 11:06:03 dnsmasq-dhcp[999]: Ignoring domain ant.amazon.com for DHCP host name MININT-I42PLI8
May  3 11:06:03 dnsmasq-dhcp[999]: DHCPACK(br0) 192.168.0.105 ac:e2:d3:07:82:9d MININT-I42PLI8
May  3 11:06:04 dnsmasq-dhcp[999]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:24:2f:0e:21:ac:e2:d3:07:82:9d
May  3 11:06:04 igmpx[1401]: added membership for 239.255.255.250 on upstream #0 102.182.112.122
May  3 11:06:04 igmpx[1401]: added new route 239.255.255.250: 102.182.112.122 -> 192.168.0.1
May  3 11:06:04 igmpx[1401]: route 239.255.255.250 on upstream #0 activated with 192.168.0.105
May  3 11:06:14 igmpx[1401]: active route 239.255.255.250 changed source from 192.168.0.105 to 192.168.0.1
May  3 11:06:14 igmpx[1401]: route 239.255.255.250 on upstream #0 activated with 192.168.0.1
May  3 11:06:23 igmpx[1401]: active route 239.255.255.250 changed source from 192.168.0.1 to 169.1.211.141
May  3 11:06:23 igmpx[1401]: route 239.255.255.250 on upstream #0 activated with 169.1.211.141
 
The_Ogre said:
A Samsung?

How did you fix it?
Click to expand...

I searched online, and it turns out that some Samsung TVs have a bug in the OS that sets their hostname to "localhost", which is bad because the router itself is "localhost" and it causes a clash. So I gave my TV a static IP address on the TV itself and also went into the router settings and assigned that static IP address to the TV's MAC address, and renamed the TVs hostname. Now the problem is solved and I'm gonna go work as an IT technician

If you search that log message online, you'll get a few sites/forums that give you the exact steps.
 
Jonntra_Volta said:
I searched online, and it turns out that some Samsung TVs have a bug in the OS that sets their hostname to "localhost", which is bad because the router itself is "localhost" and it causes a clash. So I gave my TV a static IP address on the TV itself and also went into the router settings and assigned that static IP address to the TV's MAC address, and renamed the TVs hostname. Now the problem is solved and I'm gonna go work as an IT technician

If you search that log message online, you'll get a few sites/forums that give you the exact steps.
Click to expand...
No jokes, yesterday I was going to tell you to reserve the IP in the router for the TV but I forgot.
 
Rickster said:
Unplug all devices except for your Wan cable from the CPE and see what happens, also disconnect all wireless devices.
Click to expand...

I noticed the following entry in my log (I don't know if it is the same time as the reboot, because the dates and times in the log seem to reset so it shows 1 January).

Jan 1 00:00:08 kernel: Wan link is down!

And then after 7 seconds:

Jan 1 00:00:15 kernel: Wan link is up!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X