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

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...
That should be relatively benign. I don't see that causing a crash. I do see some igmp messages in the logs. Maybe disable IGMP snooping?
 
I have the same router from Afrihost, stupid Russian dogegg device, it was rebooting constantly, no idea why, but out of boredom I decided to try my macbook pro on the 5ghz, and the HP on ethernet, and rock solid, not a single reboot, longest online was about 17 days, only time a reboot, when the power goes out...I suspect the 2.6ghz transciever is faulty..
 
You could also try changing your broadcast channels for 2.4 band.
My laptop's were constantly being dropped of the router until I did this
 
It just rebooted again now and I see the following in the logs (these are the latest entries, even though it shows Jan 1):

Code: 
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 kernel: wlan1: (Family SSHZ Fibre) Disassoc received from e4:a7:c5:dd:d0:0e Reason: Leaving (or has left) IBSS or ESS[3]
Jan  1 02:01:00 kernel: wlan1: A wireless client is disassociated - E4:A7:C5:DD:D0:0E
Jan  1 02:01:22 udhcpc[1110]: sending DHCPDISCOVER
Jan  1 02:01:25 udhcpc[1110]: sending DHCPDISCOVER
Jan  1 02:01:28 udhcpc[1110]: sending DHCPDISCOVER
 
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):

Code: 
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 v0.93: registering with nfnetlink.
Jan  1 00:00:05 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan  1 00:00:05 kernel: TCP: cubic registered
Jan  1 00:00:05 kernel: NET: Registered protocol family 10
Jan  1 00:00:05 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan  1 00:00:05 kernel: NET: Registered protocol family 17
Jan  1 00:00:05 kernel: Ebtables v2.0 registered
Jan  1 00:00:05 kernel: l2tp_core: L2TP core driver, V2.0
Jan  1 00:00:05 kernel: 8021q: 802.1Q VLAN Support v1.8
Jan  1 00:00:05 kernel: Realtek FastPath:v1.03
Jan  1 00:00:05 kernel: nlmon: nlmon_init entry
Jan  1 00:00:05 kernel: Probing RTL819X NIC-kenel stack size order[2]...
Jan  1 00:00:05 kernel:   SoC: 8197FS
Jan  1 00:00:05 kernel: eth0 added. vid=9 Member port 0x10f...
Jan  1 00:00:05 kernel: eth1 added. vid=8 Member port 0x10...
Jan  1 00:00:05 kernel: rtl819x_dlink Generic Netlink family is registered.
Jan  1 00:00:05 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Jan  1 00:00:05 kernel: Freeing unused kernel memory: 184K (806d2000 - 80700000)
Jan  1 00:00:05 kernel: updateboot: bootloader up to date
Jan  1 00:00:05 kernel: gpiom: module license 'Proprietary' taints kernel.
Jan  1 00:00:05 kernel: Disabling lock debugging due to kernel taint
Jan  1 00:00:05 kernel: gpiom: module starting ...
Jan  1 00:00:05 kernel: gpiom: using profile DIR_825C_RT8197F.
Jan  1 00:00:05 kernel: gpiom: button support enabled.
Jan  1 00:00:05 kernel: gpiom: led support enabled.
Jan  1 00:00:05 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan  1 00:00:05 kernel: nf_nat_rtsp v0.6.21 loading
Jan  1 00:00:05 kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jan  1 00:00:05 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_enable=0" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_pure=0" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_priority=1" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_encrypt=0" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_num=0" failed
Jan  1 00:00:05 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Jan  1 00:00:05 kernel: WlanSupportAbility = 0x3
Jan  1 00:00:05 kernel: [hard_code_8822_mibs] +++
Jan  1 00:00:05 kernel: MAX_RX_BUF_LEN = 4000
Jan  1 00:00:05 kernel: [ODM_software_init]
Jan  1 00:00:05 kernel: clock 40MHz
Jan  1 00:00:05 kernel: InitPON OK!!!
Jan  1 00:00:05 kernel: load efuse ok
Jan  1 00:00:05 kernel: rom_progress: 0x200006f
Jan  1 00:00:05 kernel: rom_progress: 0x400006f
Jan  1 00:00:05 kernel: InitMAC Page0
Jan  1 00:00:05 kernel: Init Download FW OK
Jan  1 00:00:05 kernel: halmac_init_mac_cfg OK
Jan  1 00:00:05 kernel: halmac_cfg_rx_aggregation OK
Jan  1 00:00:05 kernel: halmac_init_mac_cfg OK
Jan  1 00:00:05 kernel: [GetHwReg88XX][size PHY_REG_PG_8822Bmp_Type0]
Jan  1 00:00:05 kernel: [GetHwReg88XX][PHY_REG_PG_8822Bmp_Type0]
Jan  1 00:00:05 kernel: RL6302_MAC_PHY_Parameter_v018_20140708
Jan  1 00:00:05 kernel: [set_8822_trx_regs] +++
Jan  1 00:00:05 kernel: efuse content 0x3D7 = 0xf2
Jan  1 00:00:05 kernel: efuse content 0x3D8 = 0xf0
Jan  1 00:00:05 kernel: -------> Set MIB from /etc/Wireless/RTL8192CD.dat
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_enable=0" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_pure=0" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_priority=1" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_encrypt=0" failed
Jan  1 00:00:05 kernel: CFGFILE set_mib "wds_num=0" failed
Jan  1 00:00:05 kernel: <------- Set MIB from /etc/Wireless/RTL8192CD.dat Success
Jan  1 00:00:05 kernel: WlanSupportAbility = 0x3
Jan  1 00:00:05 kernel: [ODM_software_init]
Jan  1 00:00:05 kernel: [97F] Bonding Type 97FS, PKG1
Jan  1 00:00:05 kernel: [97F] RFE type 0 PHY paratemters: DEFAULT
Jan  1 00:00:05 kernel: clock 25MHz
Jan  1 00:00:05 kernel: load efuse ok
Jan  1 00:00:05 kernel: rom_progress: 0x200006f
Jan  1 00:00:05 kernel: rom_progress: 0x400006f
Jan  1 00:00:05 kernel: [GetHwReg88XX][PHY_REG_PG_8197Fmp_Type0] size
Jan  1 00:00:05 kernel: [GetHwReg88XX][PHY_REG_PG_8197Fmp_Type0]
Jan  1 00:00:05 kernel: [GetHwReg88XX][rtl8197Ffw]
Jan  1 00:00:05 kernel: [GetHwReg88XX][rtl8197Ffw size]
Jan  1 00:00:05 kernel: [97F] Default BB Swing=30
Jan  1 00:00:06 kernel: Wan link is up!
Jan  1 00:00:06 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jan  1 00:00:08 kernel: Wan link is down!
Jan  1 00:00:08 kernel: Add PERMIT ACL(br0) for CPU packets - OK
Jan  1 00:00:08 kernel: Add TOCPU ACL(eth1) for DHCP packets - OK
Jan  1 00:00:08 kernel: Add TOCPU ACL(br0) for DNS packets - OK
Jan  1 00:00:08 dnsmasq[998]: started, version 2.78 cache disabled
Jan  1 00:00:08 dnsmasq[998]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth no-DNSSEC no-loop-detect no-inotify
Jan  1 00:00:08 dnsmasq[998]: warning: interface br0 does not currently exist
Jan  1 00:00:08 dnsmasq-dhcp[998]: DHCP, IP range 192.168.0.100 -- 192.168.0.200, lease time 1d
Jan  1 00:00:08 dnsmasq-dhcp[998]: DHCPv6 stateless on fd01::
Jan  1 00:00:08 dnsmasq-dhcp[998]: router advertisement on fd01::
Jan  1 00:00:08 dnsmasq-dhcp[998]: IPv6 router advertisement enabled
Jan  1 00:00:08 dnsmasq[998]: read /tmp/hosts - 5 addresses
Jan  1 00:00:10 kernel: d-link channel[1+2+3+4+5] = 1560
Jan  1 00:00:10 kernel: d-link channel[2+3+4+5+6] = 1570
Jan  1 00:00:10 kernel: d-link channel[3+4+5+6+7] = 1530
Jan  1 00:00:10 kernel: d-link channel[4+5+6+7+8] = 1450
Jan  1 00:00:10 kernel: d-link channel[5+6+7+8+9] = 1300
Jan  1 00:00:10 kernel: d-link channel[6+7+8+9+10] = 1130
Jan  1 00:00:10 kernel: d-link channel[7+8+9+10+11] = 950
Jan  1 00:00:10 kernel: d-link select channel = 11 + 7
Jan  1 00:00:10 kernel: Add PERMIT ACL(br0) for CPU packets - OK
Jan  1 00:00:10 kernel: Add TOCPU ACL(eth1) for DHCP packets - OK
Jan  1 00:00:10 kernel: Add TOCPU ACL(br0) for DNS packets - OK
Jan  1 00:00:10 kernel: device eth0.2 entered promiscuous mode
Jan  1 00:00:11 kernel: device eth0 entered promiscuous mode
Jan  1 00:00:11 kernel: device wlan1 entered promiscuous mode
Jan  1 00:00:11 kernel: device wlan0 entered promiscuous mode
Jan  1 00:00:11 kernel: br0: port 3(wlan0) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 3(wlan0) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 2(wlan1) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 2(wlan1) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 1(eth0.2) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 1(eth0.2) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 3(wlan0) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 2(wlan1) entered forwarding state
Jan  1 00:00:11 kernel: br0: port 1(eth0.2) entered forwarding state
Jan  1 00:00:11 kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
 
Part 2:

Code: 
Jan  1 00:00:12 anweb[1035]: Starting...

Jan  1 00:00:12 kernel: d-link channel[36+40+44+48] = 0

Jan  1 00:00:12 kernel: d-link channel[52+56+60+64] = 0

Jan  1 00:00:12 kernel: d-link channel[100+104+108+112] = 0

Jan  1 00:00:12 kernel: d-link channel[149+153+157+161] = 0

Jan  1 00:00:12 kernel: d-link select channel = 36 + 48

Jan  1 00:00:12 kernel: d-link channel[36] = 0

Jan  1 00:00:12 kernel: d-link channel[40] = 0

Jan  1 00:00:12 kernel: d-link channel[44] = 0

Jan  1 00:00:12 kernel: d-link channel[48] = 0

Jan  1 00:00:12 kernel: d-link select main channel = 36

Jan  1 00:00:12 kernel: d-link offset_2nd_chan = ABOVE

Jan  1 00:00:14 dnsmasq-dhcp[998]: DHCPREQUEST(br0) 192.168.0.117 ac:e2:d3:08:00:c6

Jan  1 00:00:14 dnsmasq-dhcp[998]: Ignoring domain ant.amazon.com for DHCP host name MININT-RB4J6FA

Jan  1 00:00:14 dnsmasq-dhcp[998]: DHCPACK(br0) 192.168.0.117 ac:e2:d3:08:00:c6 MININT-RB4J6FA

Jan  1 00:00:14 dnsmasq-dhcp[998]: DHCPSOLICIT(br0) 00:01:00:01:24:1d:cc:cc:ac:e2:d3:08:00:c6

Jan  1 00:00:14 dnsmasq-dhcp[998]: DHCPREQUEST(br0) 192.168.0.105 ac:e2:d3:07:82:9d

Jan  1 00:00:14 dnsmasq-dhcp[998]: Ignoring domain ant.amazon.com for DHCP host name MININT-I42PLI8

Jan  1 00:00:14 dnsmasq-dhcp[998]: DHCPACK(br0) 192.168.0.105 ac:e2:d3:07:82:9d MININT-I42PLI8

Jan  1 00:00:14 dnsmasq-dhcp[998]: DHCPSOLICIT(br0) 00:01:00:01:24:2f:0e:21:ac:e2:d3:07:82:9d

Jan  1 00:00:15 dnsmasq-dhcp[998]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:24:1d:cc:cc:ac:e2:d3:08:00:c6

Jan  1 00:00:15 dnsmasq-dhcp[998]: DHCPSOLICIT(br0) 00:01:00:01:24:2f:0e:21:ac:e2:d3:07:82:9d

Jan  1 00:00:15 kernel: Wan link is up!

Jan  1 00:00:15 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Jan  1 00:00:15 dnsmasq-dhcp[998]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:24:2f:0e:21:ac:e2:d3:07:82:9d

Jan  1 00:00:15 miniupnpd[1047]: could not open lease file: /tmp/upnp.leases

Jan  1 00:00:15 miniupnpd[1047]: HTTP listening on port 34852

Jan  1 00:00:15 miniupnpd[1047]: Listening for NAT-PMP traffic on port 5351

Jan  1 00:00:17 link_watcher_start[863]: link watcher start with status 1

Jan  1 00:00:17 kernel: monitor task is initialized pid= 1070

Jan  1 00:00:17 anweb[1035]: anweb sighandler signal = 126

Jan  1 00:00:18 anweb[1035]: HTTP main server started on 80,443s port (ports).

Jan  1 00:00:18 anweb[1035]: HTTP intercept server started on 81,4445s port (ports).

Jan  1 00:00:18 udhcpc[1111]: started, v1.26.2

Jan  1 00:00:18 udhcpc[1111]: sending DHCPDISCOVER

Jan  1 00:00:19 kernel: wlan1: A wireless client is associated - 24:DA:33:FF:CB:E2

Jan  1 00:00:19 kernel: wlan1: (Family SSHZ Fibre) STA: 24:da:33:ff:cb:e2 Status: Successful[0]

Jan  1 00:00:19 kernel: wlan1: WPA2-AES PSK authentication in progress...

Jan  1 00:00:19 kernel: wlan1: A wireless client is associated - 24:DA:33:FF:CB:E2

Jan  1 00:00:19 kernel: wlan1: Open and authenticated

Jan  1 00:00:19 dnsmasq-dhcp[998]: DHCPREQUEST(br0) 192.168.0.104 24:da:33:ff:cb:e2

Jan  1 00:00:19 dnsmasq-dhcp[998]: DHCPACK(br0) 192.168.0.104 24:da:33:ff:cb:e2 HUAWEI_P30_lite-f43da891b

Jan  1 00:00:19 dnsmasq-dhcp[998]: DHCPREQUEST(br0) 192.168.0.104 24:da:33:ff:cb:e2

Jan  1 00:00:19 dnsmasq-dhcp[998]: DHCPACK(br0) 192.168.0.104 24:da:33:ff:cb:e2 HUAWEI_P30_lite-f43da891b

Jan  1 00:00:20 stop_process_t[1075]: not found pid process 'igmpx'

Jan  1 00:00:20 dms_reset_uptime[1075]: enter key eth1_2

Jan  1 00:00:20 dms_reset_uptime[1075]: unable to remove file /tmp/stat.eth1_2
Jan  1 00:00:21 dnsmasq[998]: read /tmp/hosts - 5 addresses
Jan  1 00:00:21 dnsmasq[998]: read /tmp/hosts - 5 addresses
Jan  1 00:00:21 syslog: libmtd (_mtd_write_ex): to "/dev/mtd2", size: 0x443, offset: 0x4000, buffer: 0x7f9ff620
Jan  1 00:00:21 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 00:00:24 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 00:00:47 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 00:00:51 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 00:00:54 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:01:17 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:01:20 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:01:23 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:01:46 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:01:49 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:01:52 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:02:21 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:02:24 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:02:27 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:02:56 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:02:59 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:03:02 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:03:25 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:03:28 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:03:31 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:03:54 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:03:58 udhcpc[1111]: sending DHCPDISCOVER
Jan  1 02:04:01 udhcpc[1111]: sending DHCPDISCOVER
 
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 think those are reboots because the connection duration shows 24 hours.

It's funny, because I tried 2 brand new routers that Afrihost sent to me (same model) and both have the reboot issue.
 
You guys who don't want this router, please sell it to me. I want to put DD-WRT on it.
 
SadIvyParrot said:
I have the same router from Afrihost, stupid Russian dogegg device, it was rebooting constantly, no idea why, but out of boredom I decided to try my macbook pro on the 5ghz, and the HP on ethernet, and rock solid, not a single reboot, longest online was about 17 days, only time a reboot, when the power goes out...I suspect the 2.6ghz transciever is faulty..
Click to expand...

Only saw this now. Will try this out.

Did you disable the 2.4ghz band completely, and connected all wireless devices to 5ghz?
 
I left the 2.6Ghz running, but all my major devices, laptop, phone, ipad are on the 5ghz and no issues, I suspect that living surrounded by dozens of networks and probebly hundreds of devices, 2.6ghz is crowded, as I understand 5ghz has a shorter range, so maybe being shorter range, less outside corruption...apart from that nothing has changed, same everything and no issues to report...
 
SadIvyParrot said:
I left the 2.6Ghz running, but all my major devices, laptop, phone, ipad are on the 5ghz and no issues, I suspect that living surrounded by dozens of networks and probebly hundreds of devices, 2.6ghz is crowded, as I understand 5ghz has a shorter range, so maybe being shorter range, less outside corruption...apart from that nothing has changed, same everything and no issues to report...
Click to expand...

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.
 
I am not a wifi expert, I had issues, and to be honest, Afrihost raiding my bank account for R99, then sending me a router, whilst my old router is in transit for testing, then if it found to be "in working order" a further R99 to send it back..the whole time I am off the air so to speak, could be as long as 5 or more days...Out of desperation, I tried the 5GHZ solution, and it seems to work...I live surrounded by high rise complexes, over a dozen named networks, but I strongly suspect the 5Ghz is working only as it is short range..
 
SadIvyParrot said:
I am not a wifi expert, I had issues, and to be honest, Afrihost raiding my bank account for R99, then sending me a router, whilst my old router is in transit for testing, then if it found to be "in working order" a further R99 to send it back..the whole time I am off the air so to speak, could be as long as 5 or more days...Out of desperation, I tried the 5GHZ solution, and it seems to work...I live surrounded by high rise complexes, over a dozen named networks, but I strongly suspect the 5Ghz is working only as it is short range..
Click to expand...

Nice. How long have you been online now without any reboots? What about your devices that don't support 5Ghz?
 
Yeah, that is a problem, seems there are rogue devices that are not 5ghz compliant, but in my case, the ones that work on 5ghz are fine, and the ones that only work on the 2.4ghz do not seem to cause conflcts, maybe it was the mac laptop, I don't know, nothing has changed apart from moving the mac laptop from 2.4ghz to 5ghz..Is the router, mine and yours faulty, I would almost say yes, nothing good as come out of Russia..
 
There is an a setting in your wifi. Disable the feature that indicates you can use more/extended channels. Once complete let me know if you still have the reboots or wifi drops.
 
We have had modems for close on many years, and I am sure there are competent coders out there, could we please have an interface on a router that actually does what it says on the tin... 99% of the interface is pure Kanji, I have no idea what it means, and really I just need 2 things, 1, a way to monitor the volume of traffic through the router, assign names to devices, so and so's phone, Joe's ipad, Mary's tablet, and a simple one click assign guest network...I had hoped that the change from adsl to fibre and a fancy looking 4 spike router, I would get a pretty interface, I got pretty alright, pretty ugly and pretty useless... Not even Afrihost knows all the settings...
 
SadIvyParrot said:
Yeah, that is a problem, seems there are rogue devices that are not 5ghz compliant, but in my case, the ones that work on 5ghz are fine, and the ones that only work on the 2.4ghz do not seem to cause conflcts, maybe it was the mac laptop, I don't know, nothing has changed apart from moving the mac laptop from 2.4ghz to 5ghz..Is the router, mine and yours faulty, I would almost say yes, nothing good as come out of Russia..
Click to expand...

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, this time a refurbished one. So I'll test this one out this weekend, with the 5ghz workaround and without it.
 
I feel your pain. It is nigh impossible to pin the problem to 1 exact failure point, could it be congestion on 2.4ghz, ie too many devices in the region, is the 2.4ghz transciever faulty, faulty internal code? Honestly I was at my wits end, desperation is the grandmother of invention, why not try 5ghz...to date, nothing has changed, same devices, same router, same ISP, same same, only changed the laptop to 5ghz, as to why this solved the tripping/resetting.. It is being used as much on 5ghz as it was on 2.4ghz, usage patterns have not changed, my only observation, the change to 5ghz donnu took strain off a weaker overcrowded 2.4ghz system...who knows...I would bet a months subs that Afrihost tested all 3 of your routers and found no faults...

Makes me wonder about the testing/certifying of the product..if you live in a busy wifi region, and we all do, with dozens of networks with many on 2.4ghz, etc, was the routers tested under the same? With 12 or more devices attached to a router, using wifi, ethernet etc?? In other words a real life test, and not a sterile wifi free zone in a lab...Curious...
 
SadIvyParrot said:
I feel your pain. It is nigh impossible to pin the problem to 1 exact failure point, could it be congestion on 2.4ghz, ie too many devices in the region, is the 2.4ghz transciever faulty, faulty internal code? Honestly I was at my wits end, desperation is the grandmother of invention, why not try 5ghz...to date, nothing has changed, same devices, same router, same ISP, same same, only changed the laptop to 5ghz, as to why this solved the tripping/resetting.. It is being used as much on 5ghz as it was on 2.4ghz, usage patterns have not changed, my only observation, the change to 5ghz donnu took strain off a weaker overcrowded 2.4ghz system...who knows...I would bet a months subs that Afrihost tested all 3 of your routers and found no faults...

Makes me wonder about the testing/certifying of the product..if you live in a busy wifi region, and we all do, with dozens of networks with many on 2.4ghz, etc, was the routers tested under the same? With 12 or more devices attached to a router, using wifi, ethernet etc?? In other words a real life test, and not a sterile wifi free zone in a lab...Curious...
Click to expand...

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 model, and hopefully Dlink is aware of this.

But I'll test your method over the weekend and let you know if it worked. Thanks.
 
SadIvyParrot said:
Makes me wonder about the testing/certifying of the product..if you live in a busy wifi region, and we all do, with dozens of networks with many on 2.4ghz, etc, was the routers tested under the same? With 12 or more devices attached to a router, using wifi, ethernet etc?? In other words a real life test, and not a sterile wifi free zone in a lab...Curious...
Click to expand...
Actually, a lot of routers that actually send deauth packets to neighboring wifi in order to clear up some channels for better signal. WPA3 solves the problem, but not many routers support it.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X