Hi Guys,

Recently purchased this router for our company. Connected, configured, and updated the firmware to the latest version on Sunday and all seemed good. Managed to connect to our sister company VPN.
On Monday we had a few drops in our network and after some investigating, we noticed the router had rebooted about 3 times. On Tuesday the router would stay on for about 30minutes then reboot this happened all of Tuesday. This morning I reset the router to factory settings, connected 1 wan port and 1 LAN port and within 10 minutes the router was rebooting itself again. I have checked the log files and can't see what the issue can be. I have even tried to downgrade the firmware to see if that might work but the router reverts back to the latest version after installing.

The only thing I can think of is that the router is faulty and I should send it back.
Has anyone else had this issue and managed to get it resolved?
I do like Draytek but I'm worried if I buy another one I will have the same issue?
Cheers

If the router was restarting prior to the upgrade and is restarting more after the upgrade, it's tough to tell whether that's a hardware problem or a firmware issue. I recommend getting in touch with support, you can do "sys ver dbg" in the router's web console (sliders icon, top-right) and record that. Then see if it changes.
Also check whether the router's dbg matches the current firmware version, if it doesn't then it may be some other issue causing restarts.

This guide covers initial items to check: https://www.draytek.co.uk/support/guides/kb-troubleshoot-reboot

I see one open ticket for a restart issue right now with 3.9.7.1, which is specific to the customer's config / network. No general reports of restarts from what I can tell.

Thanks for the reply, I have tried all the troubleshooting in the guide you provided.
I will raise a ticket with their support team.
Cheers

Hi,
I have been doing some more research and can see in the syslogs what happens before the system reboots.
Here is what happens just before the router reboots itself:

Memsave Config addr 0x4af489d8 size 5673080
2021-12-17_14:02:49.75541 [0;35m
2021-12-17_14:08:35.05541 Fix me!!! sha1
[m[dpdk_get_ct_info] del portmap WARN t:1
2021-12-17_14:08:35.05557 CMD 192.168.1.67:1 ->52.97.208.34:9
2021-12-17_14:08:35.05872 MAP 192.168.1.67:50168 ->52.113.194.132:443 if=XXX.XXX.XXX.XXX:60504
2021-12-17_14:08:36.04971 [dpdk_get_ct_info] del portmap WARN t:1
2021-12-17_14:08:36.05297 CMD 192.168.1.67:1 ->52.113.194.132:10
2021-12-17_14:08:36.05628 MAP 192.168.1.67:50169 ->13.107.136.9:443 if=XX.XXX.XXX.XXX:60505
2021-12-17_14:14:34.77523 [dpdk_chk_resp_ipv4] 0 p:6 f:0 192.168.1.11:51050->172.217.16.227:443 err=9.201
2021-12-17_14:16:54.45048 [0;32;31m
2021-12-17_14:16:54.45181 [sync_trap_handler:26] !!!!! BUG !!!!! .sync exception, now dump debug information then reboot.........
2021-12-17_14:16:54.46295 ========================================================
2021-12-17_14:16:54.46921 CurrTaskPrio=25
2021-12-17_14:16:54.47116 DrayIntNestingLvl=0
2021-12-17_14:16:54.47357 DrayOSRunning=1
2021-12-17_14:16:54.47599 DrayLockNestingLvl=2
2021-12-17_14:16:54.48344 esr x20:0x96000021
2021-12-17_14:16:54.48346 far x21:0x4626a290
2021-12-17_14:16:54.48743 elr x22:0x401b3fd4
2021-12-17_14:16:54.48745 sp:0x4626a150[35m
2021-12-17_14:16:54.48757 dump_backtrace: fp:0x4626a130, pc:0x405f5910[0m
2021-12-17_14:16:54.49541 Call trace: 0x405f5910 0x40000398 0x40e09a78 0x401b0d8c 0x402082fc 0x401a6758 0x400bba14
2021-12-17_14:16:54.49758
2021-12-17_14:16:54.49783 ========================================================
2021-12-17_14:16:54.50412 [m
2021-12-17_14:16:54.50468

---

2021-12-17_14:16:54.51174 Current Task Prio=125 SP=4626a310, Name:CM_Task
2021-12-17_14:16:54.51703

---

2021-12-17_14:16:54.52421 ============Dump Running Tasks=============

Any Idea what might be causing this?

Thats interesting, I always use the Global firmware site and that shows 3.9.7.1/v17 - no issues whatsoever.

From the trace, it looks like a LAN PC tried to access that 172.217.x.x address via HTTPS. That caused the DPDK (packet accelerator process) to crash and it gave some debug information.

That is apparently a Google IP, so it could be related to a specific google service or just a google search. Next step would be to see what that 1.11 computer is doing that causes it to have this problem.
Hopefully support are helping you with this and it can be resolved quickly