Jump to content
Chrisvw

XR 500 CPU Spikes and High CPU

Recommended Posts

Hi Chris - to max out the XR500 CPU is quite a feat. Most likely reason would be very high, sustained throughput (e.g. very large downloading / uploading. Are you doing this?

Other possible causes could be ventilation - make sure it's in a sensible place - and also having a LOT of tabs open to the user interface, 

Are any of these possible?

Share this post


Link to post
Share on other sites

Its not like a computer in that you can see a breakdown. Something is not right here. It should not stay that high. Could you try a factory reset - that may clear the problem

https://kb.netgear.com/000053098/How-do-I-perform-a-factory-reset-on-my-Nighthawk-Pro-Gaming-router

Share this post


Link to post
Share on other sites
4 hours ago, Chrisvw said:

It is a new router. Not a cosmetic issue it affects online gaming not able to sign in or stream either.

Hi, welcome to the forum! Yeh this seems like something you need to contact Netgear over. This could very well be hardware related, in which case they'll be able to replace your router. Make sure to provide all the evidence you've gathered so far (screenshots and a link to this thread should help).

Share this post


Link to post
Share on other sites
13 hours ago, Chrisvw said:

It is a new router. Not a cosmetic issue it affects online gaming not able to sign in or stream either.

Sounds like hardware, if you had mentioned this in the first thread that would have helped Still have you tried the troubleshooting steps? You would have to have upgraded firmware when you set the router up, so a factory reset is what Netgear will ask you to do, so I suggest that as your first port of call.

Share this post


Link to post
Share on other sites
3 hours ago, Chrisvw said:

Hi  Downgraded to 

Firmware Version

V2.3.2.22

 Seems stable now.

Interesting... Thanks for letting us know. We believe this might have happened to someone in the past, and if I remember rightly it's because something went wrong when you upgraded to the latest version. Could you try upgrading again? You should see that the issue has stopped.

Share this post


Link to post
Share on other sites

There you go and NeatGear support does not have a clue. Have to reboot every day just to play a game. Same issue when I downgrade CPU is not high but can not sign into PSN or any online game. This is a software issue from my point if view. Can stream and do all other things on the Web except gaming.

System.thumb.jpg.77fd768e34c7abe88e135b0c525b9d89.jpg

CPU.png

Share this post


Link to post
Share on other sites
2 hours ago, Chrisvw said:

There you go and NeatGear support does not have a clue. Have to reboot every day just to play a game. Same issue when I downgrade CPU is not high but can not sign into PSN or any online game. This is a software issue from my point if view. Can stream and do all other things on the Web except gaming.

Alright, not to worry! This is a really strange one - I've never seen an issue quite like it. I'm not sure whether this is software or hardware to blame here. Did Netgear not offer any kind of replacement or further options there?

I've forwarded this thread to a developer who will be able to take a look. In the mean time, could you let us know anything you think might help us to diagnose the cause? If there's anything - anything at all - that you're running in the background, network traffic or otherwise, that might be bugging out the router CPU then please let us know. It might also be worth screenshotting your Logs (on System Information) and dropping that screenshot here :)

Share this post


Link to post
Share on other sites

Will do I have now logged a separate call to replace the unit. No feedback in a week from them on the current case. I will try and get a screen shot of the logs but from what I can recall I don't see any strange logs only for my Neduma Support page allowed and some DHCP events. We have to PS4's in the house and both encounter the same problem. When the router is rebooted we can both play COD or Fortnite no issues but give it 24 hours and we have to reboot.

Share this post


Link to post
Share on other sites
15 hours ago, Netduma Jack said:

Alright, not to worry! This is a really strange one - I've never seen an issue quite like it. I'm not sure whether this is software or hardware to blame here. Did Netgear not offer any kind of replacement or further options there?

I've forwarded this thread to a developer who will be able to take a look. In the mean time, could you let us know anything you think might help us to diagnose the cause? If there's anything - anything at all - that you're running in the background, network traffic or otherwise, that might be bugging out the router CPU then please let us know. It might also be worth screenshotting your Logs (on System Information) and dropping that screenshot here :)

Jack didn't we see this on another XR500 and it was a corrupted GUI, to me that looks like a normal load but the graph is wrong like before, when another user had this issue. I would suggest factory resetting on the latest firmware to avoid the security warning on all firmware prior to 2.3.2.32 and setting the router up by hand, no use of backups. If that fails then Netgear should do a RMA but surely if the CPU was being taxed that much it would be spiking at 100% and the CPU cores would be all other the place, not a nice flat graph. This really does remind me of that other issue when the graph was actually showing a normal baseline but had got corrupted and was showing 80-90% instead of 10-20% I think the OP should do a full factory reset, just because its a new router does not mean firmware does not get corrupted.

here is the link to the other issue that was like this, worth having a look they both are quite similar.



 

Share this post


Link to post
Share on other sites
1 hour ago, Killhippie said:

Jack didn't we see this on another XR500 and it was a corrupted GUI, to me that looks like a normal load but the graph is wrong like before, when another user had this issue. I would suggest factory resetting on the latest firmware to avoid the security warning on all firmware prior to 2.3.2.32 and setting the router up by hand, no use of backups. If that fails then Netgear should do a RMA but surely if the CPU was being taxed that much it would be spiking at 100% and the CPU cores would be all other the place, not a nice flat graph. This really does remind me of that other issue when the graph was actually showing a normal baseline but had got corrupted and was showing 80-90% instead of 10-20% I think the OP should do a full factory reset, just because its a new router does not mean firmware does not get corrupted.

here is the link to the other issue that was like this, worth having a look they both are quite similar.

You're absolutely right. If I had a gold star I'd give it to you!

Chris, I imagine you've already tried a factory reset and setting up the router from scratch so I didn't suggest it. If you haven't tried that, definitely try it. Make sure to read the above, and let us know what Netgear say about a replacement unit as well :)

Share this post


Link to post
Share on other sites

Log file when CPU spike occured.

DHCP IP: 192.168.0.13] to MAC address cc:6e:a4:d4:40:00, Friday, November 30, 2018 06:44:07
[DumaOS] DHCP new event., Friday, November 30, 2018 06:44:07
[DumaOS] DHCP lease change., Friday, November 30, 2018 06:44:07
[site allowed: cdn.samsungcloudsolution.com] from source 192.168.0.13, Friday, November 30, 2018 06:44:07
[site allowed: init.ess.apple.com] from source 192.168.0.17, Friday, November 30, 2018 06:48:00
[site allowed: init-p01md.apple.com] from source 192.168.0.17, Friday, November 30, 2018 06:49:19
[UPnP set event: add_nat_rule] from source 192.168.0.18, Friday, November 30, 2018 06:55:53
[UPnP set event: add_nat_rule] from source 192.168.0.18, Friday, November 30, 2018 06:55:53
[site allowed: utclient.utorrent.com] from source 192.168.0.18, Friday, November 30, 2018 06:55:53
[site allowed: www.bt.co] from source 192.168.0.18, Friday, November 30, 2018 06:55:53
[site allowed: update.utorrent.com] from source 192.168.0.18, Friday, November 30, 2018 06:55:55
[site allowed: forum.netduma.com] from source 192.168.0.18, Friday, November 30, 2018 06:57:31
[site allowed: init.ess.apple.com] from source 192.168.0.14, Friday, November 30, 2018 07:03:17
[site allowed: init-p01md.apple.com] from source 192.168.0.14, Friday, November 30, 2018 07:03:21
[site allowed: forum.netduma.com] from source 192.168.0.18, Friday, November 30, 2018 07:03:32
[DHCP IP: 192.168.0.13] to MAC address cc:6e:a4:d4:40:00, Friday, November 30, 2018 07:06:06
[DumaOS] DHCP new event., Friday, November 30, 2018 07:06:06
[DumaOS] DHCP lease change., Friday, November 30, 2018 07:06:06
[site allowed: time.samsungcloudsolution.com] from source 192.168.0.13, Friday, November 30, 2018 07:06:07
[DHCP IP: 192.168.0.13] to MAC address cc:6e:a4:d4:40:00, Friday, November 30, 2018 07:06:07
[DumaOS] DHCP new event., Friday, November 30, 2018 07:06:07
[DumaOS] DHCP lease change., Friday, November 30, 2018 07:06:07
[DoS Attack: RST Scan] from source: 190.75.89.253, port 28087, Friday, November 30, 2018 07:06:23
[site allowed: init-p01md.apple.com] from source 192.168.0.20, Friday, November 30, 2018 07:06:56
[site allowed: init.ess.apple.com] from source 192.168.0.20, Friday, November 30, 2018 07:06:56
[site allowed: forum.netduma.com] from source 192.168.0.18, Friday, November 30, 2018 07:07:33
[site allowed: mybroadband.evlink9.net] from source 192.168.0.18, Friday, November 30, 2018 07:11:30
[site allowed: forum.netduma.com] from source 192.168.0.18, Friday, November 30, 2018 07:12:34
[site allowed: ocsp.digicert.com] from source 192.168.0.10, Friday, November 30, 2018 07:12:56
[site allowed: ocsp.int-x3.letsencrypt.org] from source 192.168.0.10, Friday, November 30, 2018 07:12:58
[site allowed: www.takealot.com] from source 192.168.0.10, Friday, November 30, 2018 07:14:34
[site allowed: forum.netduma.com] from source 192.168.0.18, Friday, November 30, 2018 07:15:34
[UPnP set event: del_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:08
[UPnP set event: del_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:12
[UPnP set event: del_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:13
[UPnP set event: add_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:34
[UPnP set event: add_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:35
[UPnP set event: add_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:37
[UPnP set event: del_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:43
[UPnP set event: del_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:45
[UPnP set event: del_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:18:47
[UPnP set event: add_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:19:33
[UPnP set event: add_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:19:35
[UPnP set event: add_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:19:36
[UPnP set event: del_nat_rule] from source 192.168.0.250, Friday, November 30, 2018 07:19:46

 

Share this post


Link to post
Share on other sites

New Router  delivered today and I must say ,this must be worst choice ever in a router for me. When 2 PlayStation's connect on the network well then unplayable and unusable. Play Blackops 4 then game starts to lag thent network message features not available unable to sign into PS network until router is rebooted.

 

See below logs.......

[admin login] from source 192.168.0.21, Wednesday, December 12, 2018 18:00:30
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 17:58:53
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:58:27
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:58:17
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:58:14
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:58:13
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:58:09
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:58:08
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:57:54
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:57:18
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:57:14
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:57:02
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:57:00
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:56:59
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:56:26
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 17:55:41
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:55:14
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:55:06
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:54:58
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:53:44
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:53:40
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:53:40
[DHCP IP: 192.168.0.23] to MAC address f8:46:1c:98:1b:bc, Wednesday, December 12, 2018 17:53:39
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:53:19
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:53:10
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:52:48
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:52:37
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:52:35
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:51:23
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:51:22
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:51:12
[UPnP set event: del_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 17:46:57
[UPnP set event: add_nat_rule] from source 192.168.0.29, Wednesday, December 12, 2018 17:42:28
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 17:42:27
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:42:26
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:42:26
[DHCP IP: 192.168.0.29] to MAC address a4:d1:8c:61:a4:d2, Wednesday, December 12, 2018 17:42:26
[DumaOS] applying qos for zone lan, Wednesday, December 12, 2018 17:42:26
[DumaOS] applying qos for zone wan, Wednesday, December 12, 2018 17:42:26
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 17:42:25
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:42:25
[DHCP IP: 192.168.0.29] to MAC address a4:d1:8c:61:a4:d2, Wednesday, December 12, 2018 17:42:25
[UPnP set event: add_nat_rule] from source 192.168.0.110, Wednesday, December 12, 2018 17:33:20
[UPnP set event: del_nat_rule] from source 192.168.0.110, Wednesday, December 12, 2018 17:33:18
[UPnP set event: add_nat_rule] from source 192.168.0.110, Wednesday, December 12, 2018 17:33:15
[UPnP set event: del_nat_rule] from source 192.168.0.23, Wednesday, December 12, 2018 17:32:10
[UPnP set event: add_nat_rule] from source 192.168.0.110, Wednesday, December 12, 2018 17:32:05
[UPnP set event: add_nat_rule] from source 192.168.0.110, Wednesday, December 12, 2018 17:31:22
[admin login] from source 192.168.0.21, Wednesday, December 12, 2018 17:25:55
[DoS Attack: SYN/ACK Scan] from source: 85.222.132.24, port 443, Wednesday, December 12, 2018 17:25:54
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:25:34
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:25:34
[DHCP IP: 192.168.0.21] to MAC address 6c:40:08:95:5f:3a, Wednesday, December 12, 2018 17:25:34
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:25:33
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:25:33
[DHCP IP: 192.168.0.21] to MAC address 6c:40:08:95:5f:3a, Wednesday, December 12, 2018 17:25:33
[DoS Attack: SYN/ACK Scan] from source: 85.222.132.24, port 443, Wednesday, December 12, 2018 17:21:25
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:15:25
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:15:25
[DHCP IP: 192.168.0.26] to MAC address a8:5c:2c:15:4f:c0, Wednesday, December 12, 2018 17:15:25
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:15:24
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:15:24
[DHCP IP: 192.168.0.26] to MAC address a8:5c:2c:15:4f:c0, Wednesday, December 12, 2018 17:15:24
[DoS Attack: SYN/ACK Scan] from source: 85.222.132.24, port 443, Wednesday, December 12, 2018 17:14:01
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 17:12:37
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:12:36
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:12:36
[DHCP IP: 192.168.0.28] to MAC address 3c:15:c2:34:c4:75, Wednesday, December 12, 2018 17:12:36
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 17:12:35
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:12:35
[DHCP IP: 192.168.0.28] to MAC address 3c:15:c2:34:c4:75, Wednesday, December 12, 2018 17:12:35
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:07:43
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:07:43
[DHCP IP: 192.168.0.26] to MAC address a8:5c:2c:15:4f:c0, Wednesday, December 12, 2018 17:07:43
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 17:07:41
[DumaOS] DHCP new event., Wednesday, December 12, 2018 17:07:41
[DHCP IP: 192.168.0.26] to MAC address a8:5c:2c:15:4f:c0, Wednesday, December 12, 2018 17:07:41
[DumaOS] applying qos for zone lan, Wednesday, December 12, 2018 16:50:44
[DumaOS] applying qos for zone wan, Wednesday, December 12, 2018 16:50:43
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 16:50:43
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 16:50:42
[DumaOS] DHCP new event., Wednesday, December 12, 2018 16:50:42
[DHCP IP: 192.168.0.27] to MAC address cc:6e:a4:d4:40:00, Wednesday, December 12, 2018 16:50:42
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 16:50:41
[DumaOS] DHCP new event., Wednesday, December 12, 2018 16:50:41
[DHCP IP: 192.168.0.27] to MAC address cc:6e:a4:d4:40:00, Wednesday, December 12, 2018 16:50:41
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 16:46:08
[DumaOS] DHCP new event., Wednesday, December 12, 2018 16:46:08
[DHCP IP: 192.168.0.26] to MAC address a8:5c:2c:15:4f:c0, Wednesday, December 12, 2018 16:46:08
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 16:46:08
[DumaOS] DHCP new event., Wednesday, December 12, 2018 16:46:08
[DHCP IP: 192.168.0.26] to MAC address a8:5c:2c:15:4f:c0, Wednesday, December 12, 2018 16:46:07
[DoS Attack: ARP Attack] from source: 197.91.170.200, Wednesday, December 12, 2018 16:27:38
[DoS Attack: SYN/ACK Scan] from source: 158.69.23.226, port 80, Wednesday, December 12, 2018 16:16:10
[UPnP set event: add_nat_rule] from source 192.168.0.23, Wednesday, December 12, 2018 15:56:23
[UPnP set event: add_nat_rule] from source 192.168.0.23, Wednesday, December 12, 2018 15:56:02
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:47:15
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:47:15
[DHCP IP: 192.168.0.25] to MAC address 68:db:ca:74:61:75, Wednesday, December 12, 2018 15:47:15
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 15:47:15
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:47:15
[DHCP IP: 192.168.0.25] to MAC address 68:db:ca:74:61:75, Wednesday, December 12, 2018 15:47:15
[DoS Attack: SYN/ACK Scan] from source: 85.222.132.24, port 443, Wednesday, December 12, 2018 15:43:57
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:37:58
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:37:58
[DHCP IP: 192.168.0.23] to MAC address f8:46:1c:98:1b:bc, Wednesday, December 12, 2018 15:37:58
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:37:57
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:37:57
[DHCP IP: 192.168.0.23] to MAC address f8:46:1c:98:1b:bc, Wednesday, December 12, 2018 15:37:57
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 15:35:07
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:35:06
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:35:06
[DHCP IP: 192.168.0.24] to MAC address 64:70:33:c0:d5:17, Wednesday, December 12, 2018 15:35:06
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:35:05
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:35:05
[DHCP IP: 192.168.0.24] to MAC address 64:70:33:c0:d5:17, Wednesday, December 12, 2018 15:35:05
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 15:34:11
[DumaOS] applying qos for zone lan, Wednesday, December 12, 2018 15:34:10
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:34:10
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:34:10
[DHCP IP: 192.168.0.24] to MAC address 64:70:33:c0:d5:17, Wednesday, December 12, 2018 15:34:10
[DumaOS] applying qos for zone wan, Wednesday, December 12, 2018 15:34:10
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 15:34:09
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:34:09
[DHCP IP: 192.168.0.24] to MAC address 64:70:33:c0:d5:17, Wednesday, December 12, 2018 15:34:09
[UPnP set event: add_nat_rule] from source 192.168.0.23, Wednesday, December 12, 2018 15:33:03
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:33:01
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:33:01
[DHCP IP: 192.168.0.23] to MAC address f8:46:1c:98:1b:bc, Wednesday, December 12, 2018 15:33:01
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 15:33:00
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:33:00
[DHCP IP: 192.168.0.23] to MAC address f8:46:1c:98:1b:bc, Wednesday, December 12, 2018 15:33:00
[DoS Attack: ACK Scan] from source: 185.60.219.52, port 443, Wednesday, December 12, 2018 15:32:59
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:32:44
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:32:44
[DHCP IP: 192.168.0.22] to MAC address 3c:15:c2:36:3f:77, Wednesday, December 12, 2018 15:32:44
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 15:32:44
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:32:44
[DHCP IP: 192.168.0.22] to MAC address 3c:15:c2:36:3f:77, Wednesday, December 12, 2018 15:32:44
[admin login] from source 192.168.0.21, Wednesday, December 12, 2018 15:32:42
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:32:33
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:32:33
[DHCP IP: 192.168.0.21] to MAC address 6c:40:08:95:5f:3a, Wednesday, December 12, 2018 15:32:33
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 15:32:33
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:32:33
[DHCP IP: 192.168.0.21] to MAC address 6c:40:08:95:5f:3a, Wednesday, December 12, 2018 15:32:33
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 15:32:25
[DumaOS] DHCP lease change., Wednesday, December 12, 2018 15:32:24
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:32:24
[DHCP IP: 192.168.0.20] to MAC address b8:27:eb:c9:69:f6, Wednesday, December 12, 2018 15:32:24
[DumaOS] DHCP new lease allocated., Wednesday, December 12, 2018 15:32:24
[DumaOS] DHCP new event., Wednesday, December 12, 2018 15:32:24
[DHCP IP: 192.168.0.20] to MAC address b8:27:eb:c9:69:f6, Wednesday, December 12, 2018 15:32:24
[DumaOS] applying qos for zone lan, Wednesday, December 12, 2018 15:32:21
[DumaOS] applying qos for zone wan, Wednesday, December 12, 2018 15:32:21
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 15:31:58
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' now bound, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:33
[DumaOS] applying qos for zone lan, Wednesday, December 12, 2018 15:31:27
[DumaOS] applying qos for zone wan, Wednesday, December 12, 2018 15:31:27
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 15:31:23
[DumaOS] applying qos for zone lan, Wednesday, December 12, 2018 15:31:23
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 15:31:23
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 15:31:23
[DumaOS] applying qos for zone wan, Wednesday, December 12, 2018 15:31:23
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 15:31:22
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, December 12, 2018 15:31:22
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 15:31:22
[UPnP set event: add_nat_rule] from source 192.168.0.250, Wednesday, December 12, 2018 15:31:22
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' now bound, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:19
[DumaOS] NSS delete root for interface 'br0', Wednesday, December 12, 2018 15:31:19
[DumaOS] applying qos for zone lan, Wednesday, December 12, 2018 15:31:19
[DumaOS] NSS delete root for interface 'brwan', Wednesday, December 12, 2018 15:31:19
[DumaOS] applying qos for zone wan, Wednesday, December 12, 2018 15:31:19
[DumaOS] Geo-Filter cloudsync result 'true','Geo-Filter is up to date', Wednesday, December 12, 2018 15:31:17
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' now bound, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:16
[DumaOS] All dependencies loaded, starting, Wednesday, December 12, 2018 15:31:16
[DumaOS] Dependency loaded 'com.netdumasoftware.devicemanager', Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] All dependencies loaded, starting, Wednesday, December 12, 2018 15:31:16
[DumaOS] Dependency loaded 'com.netdumasoftware.devicemanager', Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:16
[DumaOS] Cloudsync DPI result 'false','All mirrors are down', Wednesday, December 12, 2018 15:31:16
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' now bound, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:1
[DumaOS] App 'com.netdumasoftware.rappstore' initialised & starting., Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:15
[DumaOS] R-App store cloud sync failed, Wednesday, December 12, 2018 15:31:15
[DumaOS] HTTP download failed with code '404', Wednesday, December 12, 2018 15:31:15
[DumaOS] Resync R-App store cloud, Wednesday, December 12, 2018 15:31:14
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:1
[DumaOS] App 'com.netdumasoftware.autoadmin' initialised & starting., Wednesday, December 12, 2018 15:31:13
[DumaOS] Dependency loaded 'com.netdumasoftware.autoadmin', Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Dependency loaded 'com.netdumasoftware.autoadmin', Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pendin, Wednesday, December 12, 2018 15:31:1
[DumaOS] App 'com.netdumasoftware.desktop' initialised & starting., Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Wednesday, December 12, 2018 15:31:13

 

Share this post


Link to post
Share on other sites
3 hours ago, Chrisvw said:

No Geo-Filter can not get games then. No QOS settings not needed have 100 Meg Fibre link.

Could you just clarify your issue further? With two PS4's connected you say the 'game starts to lag'. What part of the game lags, the menu? Gameplay when you're online? At what point does it say 'features unavailable'?

Are both PS4's wired to the XR500? Do any issues occur with just one PS4 connected? Do both have an open NAT?

 

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

×