100% correct. That's why I wasn't interested in the results of them testing my router. Because there's no way they're testing it in the exact same environment as mine and then working on the process of elimination.
Hopefully this is a software issue and not hardware with this actual router...
I had the same issue with 2 brand new routers that Afrihost sent. So I think there's either an issue with a specific batch from Dlink, or it is an issue with the router in general. Because I also live in a complex with many other 2.4ghz wifi networks.
But Afrihost now sent a 3rd router to me...
Thanks for the reply. I live in an apartment complex so it could be that. I thought of it before (the overcrowding) and changed channels on the 2.4ghz but didn't work. I'll definitely try switching to 5ghz and report back.
Update: I disconnected the router and connected my old Huawei B315 LTE router instead. It's been running without any issues for 24 hours now. No reboots. Current connection Duration: 24:05:33
In the logs, there are a few entries of "log out succeeded" and "log in succeeded", however, I don't...
It rebooted again now 5 minutes after the last one. Here's the log (I'm breaking it up in 2 messages due to character limitations):
Jan 1 00:00:05 syslogd started: BusyBox v1.26.2
Jan 1 00:00:05 kernel: klogd started: BusyBox v1.26.2 (2019-09-16 12:59:18 MSK)
Jan 1 00:00:05 kernel: ctnetlink...
It just rebooted again now and I see the following in the logs (these are the latest entries, even though it shows Jan 1):
Jan 1 00:00:47 udhcpc[1110]: sending DHCPDISCOVER
Jan 1 00:00:50 udhcpc[1110]: sending DHCPDISCOVER
Jan 1 00:00:53 udhcpc[1110]: sending DHCPDISCOVER
Jan 1 02:01:00...
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!
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...
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:
May 3 11:04:12 ip_is_up[1074]: eth1 speed: 1000M Full
May 3 11:06:03 dnsmasq-dhcp[999]: DHCPSOLICIT(br0)...