MagnumRuger Posted February 17 Share Posted February 17 Hello all, new here and searching for a remedy for this issue brought me here. I am having intermittent connection for all devices on my XR1000V2. I’ve tried everything from a hard reset to changing some settings mentioned in another post that was created because of same/similar issues. I never had these issues prior to using this router…previous setup was just the Starlink router used in my shop while living there temporarily. Now I’m using that as an AP here at the house and the XR as my main router for expanded connectivity, adjustments, and connecting a Ubiquiti access point to beam internet to my shop. Very frustrating as this is a brand new house with intermittent high speed! Any help would be appreciated, happy to provide as much information as I need to get this resolved. Thank you! Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 17 Administrators Share Posted February 17 What is the model of the modem/router the XR is connected to and how have you set that to ensure all traffic flows to the XR? E.g. XR in its DMZ, modem/bridge mode Can you provide the logs from the System Information page when the issue happens please? Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 18 Author Share Posted February 18 I have the Starlink Gen 2 Router set to bypass mode. Here are the logs from a very recent attempt to load a web page. Please let me know what else I can provide to better help in your search for the issue. I sure appreciate it! [DoS attack: RST Scan] from source 142.251.178.188,port 5228 Monday, Feb 17,2025 20:43:38 [admin login] from source 192.168.0.29, Monday, Feb 17,2025 20:42:24 [DHCP IP: (192.168.0.29)] to MAC address 58:11:22:4C:64:25, Monday, Feb 17,2025 20:40:55 [DoS attack: ACK Scan] from source 216.239.36.131,port 5223 Monday, Feb 17,2025 20:38:46 [DHCP IP: (192.168.0.22)] to MAC address 80:B9:89:8D:47:6B, Monday, Feb 17,2025 20:36:40 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 20:30:22 [DHCP IP: (192.168.0.16)] to MAC address 1A:E9:FD:25:B4:E7, Monday, Feb 17,2025 20:15:43 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 19:55:54 [DoS attack: ACK Scan] from source 216.239.36.131,port 5223 Monday, Feb 17,2025 19:50:38 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 19:21:11 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 19:16:57 [DHCP IP: (192.168.0.26)] to MAC address 24:E5:0F:28:1D:4F, Monday, Feb 17,2025 18:45:20 [DHCP IP: (192.168.0.25)] to MAC address E4:38:83:AA:4E:EA, Monday, Feb 17,2025 18:45:19 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 18:42:30 [DoS attack: RST Scan] from source 3.167.176.199,port 443 Monday, Feb 17,2025 18:24:14 [DHCP IP: (192.168.0.11)] to MAC address 0C:70:43:06:98:04, Monday, Feb 17,2025 18:11:12 [DoS attack: RST Scan] from source 23.33.29.196,port 443 Monday, Feb 17,2025 18:10:38 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 18:08:20 [DoS attack: RST Scan] from source 23.33.29.196,port 443 Monday, Feb 17,2025 18:02:24 [DoS attack: RST Scan] from source 23.33.29.196,port 443 Monday, Feb 17,2025 18:02:23 [DoS attack: RST Scan] from source 23.64.114.60,port 443 Monday, Feb 17,2025 18:02:15 [DoS attack: ACK Scan] from source 52.89.219.164,port 80 Monday, Feb 17,2025 18:02:02 [DoS attack: ACK Scan] from source 34.117.13.33,port 443 Monday, Feb 17,2025 17:45:50 [DHCP IP: (192.168.0.22)] to MAC address 80:B9:89:8D:47:6B, Monday, Feb 17,2025 17:39:22 [DoS attack: RST Scan] from source 23.33.29.210,port 443 Monday, Feb 17,2025 17:36:30 [DoS attack: RST Scan] from source 23.33.29.197,port 443 Monday, Feb 17,2025 17:26:45 [DoS attack: RST Scan] from source 23.33.29.197,port 443 Monday, Feb 17,2025 17:25:48 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 18 Author Share Posted February 18 Outages have happened twice since the last post, hope this log helps in comparison to the last log posted. [admin login] from source 192.168.0.29, Monday, Feb 17,2025 21:49:15 [DHCP IP: (192.168.0.26)] to MAC address 24:E5:0F:28:1D:4F, Monday, Feb 17,2025 21:44:05 [DHCP IP: (192.168.0.25)] to MAC address E4:38:83:AA:4E:EA, Monday, Feb 17,2025 21:44:03 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 21:42:19 [DHCP IP: (192.168.0.22)] to MAC address 80:B9:89:8D:47:6B, Monday, Feb 17,2025 21:39:33 [DoS attack: ACK Scan] from source 34.120.24.208,port 443 Monday, Feb 17,2025 21:23:58 [admin login] from source 192.168.0.29, Monday, Feb 17,2025 21:10:31 [DoS attack: RST Scan] from source 142.251.178.188,port 5228 Monday, Feb 17,2025 20:43:38 [admin login] from source 192.168.0.29, Monday, Feb 17,2025 20:42:24 [DHCP IP: (192.168.0.29)] to MAC address 58:11:22:4C:64:25, Monday, Feb 17,2025 20:40:55 [DoS attack: ACK Scan] from source 216.239.36.131,port 5223 Monday, Feb 17,2025 20:38:46 [DHCP IP: (192.168.0.22)] to MAC address 80:B9:89:8D:47:6B, Monday, Feb 17,2025 20:36:40 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 20:30:22 [DHCP IP: (192.168.0.16)] to MAC address 1A:E9:FD:25:B4:E7, Monday, Feb 17,2025 20:15:43 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 19:55:54 [DoS attack: ACK Scan] from source 216.239.36.131,port 5223 Monday, Feb 17,2025 19:50:38 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 19:21:11 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 19:16:57 [DHCP IP: (192.168.0.26)] to MAC address 24:E5:0F:28:1D:4F, Monday, Feb 17,2025 18:45:20 [DHCP IP: (192.168.0.25)] to MAC address E4:38:83:AA:4E:EA, Monday, Feb 17,2025 18:45:19 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 18:42:30 [DoS attack: RST Scan] from source 3.167.176.199,port 443 Monday, Feb 17,2025 18:24:14 [DHCP IP: (192.168.0.11)] to MAC address 0C:70:43:06:98:04, Monday, Feb 17,2025 18:11:12 [DoS attack: RST Scan] from source 23.33.29.196,port 443 Monday, Feb 17,2025 18:10:38 [DHCP IP: (192.168.0.27)] to MAC address 70:2C:09:6D:E3:A6, Monday, Feb 17,2025 18:08:20 [DoS attack: RST Scan] from source 23.33.29.196,port 443 Monday, Feb 17,2025 18:02:24 [DoS attack: RST Scan] from source 23.33.29.196,port 443 Monday, Feb 17,2025 18:02:23 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 18 Administrators Share Posted February 18 In LAN Settings, set the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 4 minutes and see if that stops the disconnects. Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 19 Author Share Posted February 19 Thanks for that insight, I applied the requested changes am still getting the same result. Please see attached log to better help you find the issue. It dropped out 3-4 times during the time that the logs show. [DoS attack: RST Scan] from source 172.240.45.76,port 443 Wednesday, Feb 19,2025 00:54:29 [DoS attack: ACK Scan] from source 68.67.160.132,port 443 Wednesday, Feb 19,2025 00:52:56 [DHCP IP: (192.168.0.50)] to MAC address 80:B9:89:8D:47:6B, Wednesday, Feb 19,2025 00:37:16 [DHCP IP: (192.168.0.29)] to MAC address 58:11:22:4C:64:25, Wednesday, Feb 19,2025 00:29:57 [DHCP IP: (192.168.0.17)] to MAC address EC:71:DB:DD:63:C6, Wednesday, Feb 19,2025 00:29:56 [DHCP IP: (192.168.0.2)] to MAC address 0C:70:43:06:98:04, Wednesday, Feb 19,2025 00:29:55 [DoS attack: ACK Scan] from source 52.203.178.146,port 443 Wednesday, Feb 19,2025 00:29:54 [Time synchronized with NTP server] Wednesday, Feb 19,2025 00:29:46 [Internet connected] IP address: 100.68.65.147, Wednesday, Feb 19,2025 00:29:46 [Initialized, firmware version: V1.1.0.16_2.1.25] Wednesday, Feb 19,2025 00:29:20 [DHCP IP: (192.168.0.4)] to MAC address 80:B9:89:8D:47:6B, Wednesday, Feb 19,2025 00:25:32 [DHCP IP: (192.168.0.4)] to MAC address 80:B9:89:8D:47:6B, Wednesday, Feb 19,2025 00:24:52 [DHCP IP: (192.168.0.4)] to MAC address 80:B9:89:8D:47:6B, Wednesday, Feb 19,2025 00:22:28 [DHCP IP: (192.168.0.21)] to MAC address 7C:61:66:C7:6F:33, Wednesday, Feb 19,2025 00:22:21 [WLAN access rejected: incorrect security] from MAC address 7c:61:66:c7:6f:33, Wednesday, Feb 19,2025 00:22:10 [DHCP IP: (192.168.0.21)] to MAC address 7C:61:66:C7:6F:33, Wednesday, Feb 19,2025 00:21:47 [DHCP IP: (192.168.0.21)] to MAC address 7C:61:66:C7:6F:33, Wednesday, Feb 19,2025 00:21:43 [DHCP IP: (192.168.0.4)] to MAC address 80:B9:89:8D:47:6B, Wednesday, Feb 19,2025 00:20:51 [DHCP IP: (192.168.0.5)] to MAC address 1A:E9:FD:25:B4:E7, Wednesday, Feb 19,2025 00:17:57 [DoS attack: RST Scan] from source 13.216.196.139,port 8883 Wednesday, Feb 19,2025 00:17:55 [DHCP IP: (192.168.0.5)] to MAC address 1A:E9:FD:25:B4:E7, Wednesday, Feb 19,2025 00:17:55 [DHCP IP: (192.168.0.5)] to MAC address 1A:E9:FD:25:B4:E7, Wednesday, Feb 19,2025 00:16:23 [DHCP IP: (192.168.0.3)] to MAC address 74:E2:0C:ED:DB:DF, Wednesday, Feb 19,2025 00:16:17 [DHCP IP: (192.168.0.21)] to MAC address 7C:61:66:C7:6F:33, Wednesday, Feb 19,2025 00:16:12 [DHCP IP: (192.168.0.21)] to MAC address 7C:61:66:C7:6F:33, Wednesday, Feb 19,2025 00:16:10 [DHCP IP: (192.168.0.21)] to MAC address 7C:61:66:C7:6F:33, Wednesday, Feb 19,2025 00:16:07 [DHCP IP: (192.168.0.21)] to MAC address 7C:61:66:C7:6F:33, Wednesday, Feb 19,2025 00:16:05 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 20 Author Share Posted February 20 Good evening. Internet dropped again shortly before logging into NetDUMA. I waited for it to come back online before logging in to router. Hope this helps, still wanting to resolve this issue as it is affecting everything here. [admin login] from source 192.168.0.29, Wednesday, Feb 19,2025 22:31:59 [DoS attack: RST Scan] from source 23.221.245.14,port 443 Wednesday, Feb 19,2025 22:31:41 [DoS attack: RST Scan] from source 69.166.1.35,port 443 Wednesday, Feb 19,2025 22:31:41 [DHCP IP: (192.168.0.5)] to MAC address 1A:E9:FD:25:B4:E7, Wednesday, Feb 19,2025 22:31:40 [DoS attack: ACK Scan] from source 52.21.140.107,port 443 Wednesday, Feb 19,2025 22:31:29 [DoS attack: ACK Scan] from source 104.123.153.18,port 443 Wednesday, Feb 19,2025 22:26:55 [DHCP IP: (192.168.0.53)] to MAC address C8:09:A8:12:B6:BE, Wednesday, Feb 19,2025 22:25:03 [DoS attack: ACK Scan] from source 216.239.36.131,port 5223 Wednesday, Feb 19,2025 22:06:51 [DHCP IP: (192.168.0.29)] to MAC address 58:11:22:4C:64:25, Wednesday, Feb 19,2025 22:01:14 [DHCP IP: (192.168.0.20)] to MAC address D0:03:DF:4C:72:C0, Wednesday, Feb 19,2025 22:00:16 [DoS attack: RST Scan] from source 142.250.191.214,port 443 Wednesday, Feb 19,2025 21:53:48 [DHCP IP: (192.168.0.2)] to MAC address 0C:70:43:06:98:04, Wednesday, Feb 19,2025 21:45:11 [DoS attack: RST Scan] from source 23.64.114.76,port 443 Wednesday, Feb 19,2025 21:44:37 [DoS attack: RST Scan] from source 23.45.46.202,port 443 Wednesday, Feb 19,2025 21:42:04 [DoS attack: ACK Scan] from source 17.57.144.138,port 5223 Wednesday, Feb 19,2025 21:40:36 [UPnP set event: add_nat_rule] from source 192.168.0.2, Wednesday, Feb 19,2025 21:37:06 [UPnP set event: add_nat_rule] from source 192.168.0.2, Wednesday, Feb 19,2025 21:37:04 [DHCP IP: (192.168.0.2)] to MAC address 0C:70:43:06:98:04, Wednesday, Feb 19,2025 21:37:03 [DHCP IP: (192.168.0.19)] to MAC address 4C:B9:EA:96:A2:7C, Wednesday, Feb 19,2025 21:25:58 [DHCP IP: (192.168.0.5)] to MAC address 1A:E9:FD:25:B4:E7, Wednesday, Feb 19,2025 21:07:45 [DoS attack: RST Scan] from source 1.1.1.1,port 53 Wednesday, Feb 19,2025 20:45:22 [DoS attack: RST Scan] from source 1.1.1.1,port 53 Wednesday, Feb 19,2025 20:45:21 [DoS attack: RST Scan] from source 1.1.1.1,port 53 Wednesday, Feb 19,2025 20:45:20 [DoS attack: RST Scan] from source 1.1.1.1,port 53 Wednesday, Feb 19,2025 20:45:19 [DoS attack: RST Scan] from source 1.1.1.1,port 53 Wednesday, Feb 19,2025 20:45:17 [DoS attack: RST Scan] from source 1.1.1.1,port 53 Wednesday, Feb 19,2025 20:44:54 [DoS attack: RST Scan] from source 1.1.1.1,port 53 Wednesday, Feb 19,2025 20:44:53 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 20 Administrators Share Posted February 20 Still looks like DHCP, could you provide a screenshot of the DHCP page please? Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 20 Author Share Posted February 20 Sure! Please let me know if anything else is needed. e is needed. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 20 Administrators Share Posted February 20 It shouldn't make a difference in theory but we are dealing with an issue that shouldn't be happening in the first place but could you change the LAN IP back to 192.168.1.1 and see if it is better please? Also you do have some devices using IPs within the DHCP range still Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 21 Author Share Posted February 21 I changed the router IP as instructed and can confirm there are no devices within the .50-100 range, everything assigned is between .2 and .49 Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 21 Author Share Posted February 21 So changing that IP back to .1.1 caused a lost connection with the Ubiquiti Loco to my shop and still produced the dropped internet here at the house Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 21 Administrators Share Posted February 21 From the logs there is a device at .53, go ahead and disable the DHCP server then and see if the disconnects continue please. Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 22 Author Share Posted February 22 I have not seen the .53 again, not sure what it would be. I switched the DHCP off and the connection was so unstable and slow I had to turn it back on. I am attaching the log for right before I turned it back on. Hope it sheds some light on the situation. admin login] from source 192.168.0.29, Friday, Feb 21,2025 21:50:51 [DoS attack: ACK Scan] from source 34.160.10.162,port 443 Friday, Feb 21,2025 21:43:55 [DoS attack: ACK Scan] from source 146.75.82.73,port 443 Friday, Feb 21,2025 21:41:09 [DoS attack: ACK Scan] from source 34.36.225.0,port 443 Friday, Feb 21,2025 21:29:57 [DoS attack: RST Scan] from source 142.250.190.54,port 443 Friday, Feb 21,2025 21:22:41 [DoS attack: ACK Scan] from source 18.154.185.30,port 80 Friday, Feb 21,2025 21:14:05 [DoS attack: ACK Scan] from source 18.154.185.30,port 80 Friday, Feb 21,2025 21:14:04 [Time synchronized with NTP server] Friday, Feb 21,2025 21:14:03 [Internet connected] IP address: 100.68.65.147, Friday, Feb 21,2025 21:14:03 [Initialized, firmware version: V1.1.0.16_2.1.25] Friday, Feb 21,2025 21:13:16 [admin login] from source 192.168.0.29, Friday, Feb 21,2025 21:11:46 [DHCP IP: (192.168.0.29)] to MAC address 58:11:22:4C:64:25, Friday, Feb 21,2025 21:09:33 [DHCP IP: (192.168.0.3)] to MAC address 74:E2:0C:ED:DB:DF, Friday, Feb 21,2025 20:59:14 [DoS attack: ACK Scan] from source 3.22.228.224,port 443 Friday, Feb 21,2025 20:46:33 [DHCP IP: (192.168.0.5)] to MAC address 1A:E9:FD:25:B4:E7, Friday, Feb 21,2025 20:44:36 [DoS attack: ACK Scan] from source 17.57.144.246,port 5223 Friday, Feb 21,2025 20:37:54 [DoS attack: RST Scan] from source 17.253.49.202,port 443 Friday, Feb 21,2025 20:36:22 [DoS attack: ACK Scan] from source 104.18.19.218,port 443 Friday, Feb 21,2025 20:20:53 [DHCP IP: (192.168.0.2)] to MAC address 0C:70:43:06:98:04, Friday, Feb 21,2025 19:53:18 [DoS attack: RST Scan] from source 17.253.49.202,port 443 Friday, Feb 21,2025 19:38:51 [DoS attack: ACK Scan] from source 34.107.165.5,port 443 Friday, Feb 21,2025 19:14:18 [DoS attack: RST Scan] from source 142.250.190.1,port 443 Friday, Feb 21,2025 18:22:22 [DoS attack: ACK Scan] from source 3.18.184.171,port 443 Friday, Feb 21,2025 18:21:59 [DoS attack: RST Scan] from source 142.250.190.150,port 443 Friday, Feb 21,2025 17:22:16 [DoS attack: RST Scan] from source 142.250.190.150,port 443 Friday, Feb 21,2025 17:22:15 [DoS attack: RST Scan] from source 172.217.0.182,port 443 Friday, Feb 21,2025 17:22:08 [DHCP IP: (192.168.0.20)] to MAC address D0:03:DF:4C:72:C0, Friday, Feb 21,2025 17:21:59 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 23 Administrators Share Posted February 23 I think that was likely to be a conincedence, with DHCP off you would either have a connection or you wouldn't, it wouldn't affect the quality of the connection. By the looks of it the router thinks it's being attacked when it isn't. Try it again and reboot after you've disabled it and monitor. Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 27 Author Share Posted February 27 Please see attached log. Connection seems to be worse and less stable with DHCP switched off. Also, it is my iPhone that is fetching the IP address above .50 even though I have added it to the reserved list. DoS attack: ACK Scan] from source 142.250.190.35,port 80 Wednesday, Feb 26,2025 22:05:26 [DoS attack: ACK Scan] from source 35.161.246.92,port 443 Wednesday, Feb 26,2025 22:03:38 [Time synchronized with NTP server] Wednesday, Feb 26,2025 22:03:06 [Internet connected] IP address: 100.68.65.147, Wednesday, Feb 26,2025 22:03:06 [Initialized, firmware version: V1.1.0.22_2.1.34] Wednesday, Feb 26,2025 22:02:29 [DoS attack: RST Scan] from source 142.250.111.109,port 993 Wednesday, Feb 26,2025 22:01:38 [DoS attack: RST Scan] from source 34.120.195.249,port 443 Wednesday, Feb 26,2025 22:01:37 [DoS attack: RST Scan] from source 142.250.111.109,port 993 Wednesday, Feb 26,2025 22:01:37 [admin login] from source 192.168.0.29, Wednesday, Feb 26,2025 21:59:51 [DoS attack: ACK Scan] from source 23.60.131.209,port 80 Wednesday, Feb 26,2025 21:57:30 [DHCP IP: (192.168.0.29)] to MAC address 58:11:22:4C:64:25, Wednesday, Feb 26,2025 21:55:19 [DHCP IP: (192.168.0.20)] to MAC address D0:03:DF:4C:72:C0, Wednesday, Feb 26,2025 21:54:27 [DHCP IP: (192.168.0.26)] to MAC address 24:E5:0F:28:1D:4F, Wednesday, Feb 26,2025 21:52:52 [DoS attack: ACK Scan] from source 172.217.4.206,port 80 Wednesday, Feb 26,2025 21:45:05 [DoS attack: ACK Scan] from source 172.217.4.35,port 80 Wednesday, Feb 26,2025 21:01:03 [DHCP IP: (192.168.0.55)] to MAC address 1A:E9:FD:25:B4:E7, Wednesday, Feb 26,2025 20:56:49 [DHCP IP: (192.168.0.55)] to MAC address 1A:E9:FD:25:B4:E7, Wednesday, Feb 26,2025 20:28:17 [DoS attack: ACK Scan] from source 142.250.191.174,port 80 Wednesday, Feb 26,2025 20:24:01 [DHCP IP: (192.168.0.2)] to MAC address 0C:70:43:06:98:04, Wednesday, Feb 26,2025 20:14:31 [DoS attack: RST Scan] from source 23.33.29.198,port 443 Wednesday, Feb 26,2025 20:13:57 [DoS attack: ACK Scan] from source 23.227.38.74,port 443 Wednesday, Feb 26,2025 20:06:41 [DoS attack: RST Scan] from source 23.56.168.163,port 443 Wednesday, Feb 26,2025 19:55:07 [DoS attack: ACK Scan] from source 216.239.36.131,port 5223 Wednesday, Feb 26,2025 19:49:09 [DoS attack: RST Scan] from source 172.217.5.22,port 443 Wednesday, Feb 26,2025 19:47:59 [DoS attack: RST Scan] from source 17.248.210.64,port 443 Wednesday, Feb 26,2025 19:27:53 [DoS attack: RST Scan] from source 23.45.46.198,port 443 Wednesday, Feb 26,2025 19:25:07 [UPnP set event: add_nat_rule] from source 192.168.0.2, Wednesday, Feb 26,2025 19:20:05 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Wednesday, Dec 31,1969 19:00:00 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 27 Administrators Share Posted February 27 Did you reboot during the time frame of those logs? Link to comment Share on other sites More sharing options...
MagnumRuger Posted February 27 Author Share Posted February 27 Yes I did, was trying that to get more stability but had no luck Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 27 Administrators Share Posted February 27 Have you set a static/reserved IP on the phone itself? That could be why it's not following your reservation on the router. Do you have a smart device from both Amazon & Google? If so could you try disconnecting them until you'd normally have the issue and see if it still happens please? Link to comment Share on other sites More sharing options...
brianthedestroyer Posted February 27 Share Posted February 27 I'm having the same issue. Whenever this occurs, CPU0 and CPU1 are maxed out at 100% utilization. Eventually, CPU util starts to drop and internet/network traffic starts to flow again. This has been happening intermittently for about a week. Up until this time, I've had no issues with the router, I've made no changes (configuration or otherwise). I've got this firmware update waiting but every time I hit "update" it doesn't actually update. It reboots and acts like it is, but we wind up back here. I've hard rebooted the router multiple times. Update Firmware Current Version: 1.1.0.16 New Version: 1.1.0.16_2.1.25 log-1740695976811.txt Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 27 Administrators Share Posted February 27 1 hour ago, brianthedestroyer said: I'm having the same issue. Whenever this occurs, CPU0 and CPU1 are maxed out at 100% utilization. Eventually, CPU util starts to drop and internet/network traffic starts to flow again. This has been happening intermittently for about a week. Up until this time, I've had no issues with the router, I've made no changes (configuration or otherwise). I've got this firmware update waiting but every time I hit "update" it doesn't actually update. It reboots and acts like it is, but we wind up back here. I've hard rebooted the router multiple times. Update Firmware Current Version: 1.1.0.16 New Version: 1.1.0.16_2.1.25 log-1740695976811.txt 23.7 kB · 0 downloads After looking into it personally a bit more I would say it's highly likely to be a cloud update. As far as I can tell NG have auto updated people (we originally completed the DumaOS changes for that a very long time ago) but didn't mention they were doing it and so I think it's trying to use a cloud update it can't use or isn't using the one it should now be using. I've given my findings to the team so it should hopefully be a quick update once they identify the specific cause. Link to comment Share on other sites More sharing options...
brianthedestroyer Posted March 1 Share Posted March 1 On 2/27/2025 at 3:52 PM, Netduma Fraser said: After looking into it personally a bit more I would say it's highly likely to be a cloud update. As far as I can tell NG have auto updated people (we originally completed the DumaOS changes for that a very long time ago) but didn't mention they were doing it and so I think it's trying to use a cloud update it can't use or isn't using the one it should now be using. I've given my findings to the team so it should hopefully be a quick update once they identify the specific cause. In your experience working with the devs on this product, what is the anticipated timeline for a fix/patch? Days? Weeks? Months? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 2 Administrators Share Posted March 2 On 3/1/2025 at 12:12 AM, brianthedestroyer said: In your experience working with the devs on this product, what is the anticipated timeline for a fix/patch? Days? Weeks? Months? We pushed a cloud update on Friday that should fix it in theory, give your router a reboot, that will make it download the cloud automatically when it boots up then let us know if it continues please Link to comment Share on other sites More sharing options...
brianthedestroyer Posted March 3 Share Posted March 3 So far, so good. I would have had several drop/high CPU events at this point in the day. Looks like the fix addressed the issue. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 3 Administrators Share Posted March 3 That's great to hear, thanks for the update! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now