Mxcone17 Posted August 7, 2019 Posted August 7, 2019 So DumaOS QoS has not been working, speeds are crazy all over the place, high cpu usage randomly, etc. My cpu is at 20% idling, and maxes at 100% and restricts speed to less than 40% of my total bandwidth. My logs look like this: Wed Aug 7 04:55:01 2019 kern.info kernel: [ 101.204000] send: nf_ct_get failed Wed Aug 7 04:55:01 2019 kern.info kernel: [ 101.204000] recv: nf_ct_get failed Wed Aug 7 04:55:00 2019 kern.info kernel: [ 100.248000] send: nf_ct_get failed Wed Aug 7 04:55:00 2019 kern.info kernel: [ 100.248000] recv: nf_ct_get failed Wed Aug 7 04:54:51 2019 daemon.warn miniupnpd[1254]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:51 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 04:54:47 2019 kern.info kernel: [ 86.364000] send: nf_ct_get failed Wed Aug 7 04:54:47 2019 kern.info kernel: [ 86.364000] recv: nf_ct_get failed Wed Aug 7 04:54:42 2019 kern.info kernel: [ 81.672000] send: nf_ct_get failed Wed Aug 7 04:54:42 2019 kern.info kernel: [ 81.672000] recv: nf_ct_get failed Wed Aug 7 04:54:33 2019 kern.info kernel: [ 72.368000] send: nf_ct_get failed Wed Aug 7 04:54:33 2019 kern.info kernel: [ 72.368000] recv: nf_ct_get failed Wed Aug 7 04:54:28 2019 kern.info kernel: [ 67.720000] send: nf_ct_get failed Wed Aug 7 04:54:28 2019 kern.info kernel: [ 67.720000] recv: nf_ct_get failed Wed Aug 7 04:54:27 2019 kern.info kernel: [ 66.492000] send: nf_ct_get failed Wed Aug 7 04:54:27 2019 kern.info kernel: [ 66.492000] recv: nf_ct_get failed and again Wed Aug 7 05:51:17 2019 daemon.warn odhcpd[874]: Failed to send to ff02::1%br-lan (Operation not permitted) Wed Aug 7 05:51:17 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:51:16 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:51:00 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:59 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:58 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:45 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:45 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:45 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:45 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:42 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:41 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:40 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:40 2019 user.debug com.netdumasoftware.devicemanager: Marking device that is marked 192.168.88.56 3 16. Wed Aug 7 05:50:36 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:36 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:35 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:34 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:24 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:23 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:23 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:15 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:11 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:10 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 169.254.129.245:49152 not from a LAN, ignoring Wed Aug 7 05:50:06 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:06 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:05 2019 daemon.warn miniupnpd[9744]: SSDP packet sender 192.168.1.249:1900 not from a LAN, ignoring Wed Aug 7 05:50:00 2019 user.debug com.netdumasoftware.devicemanager: Marking device that is marked 192.168.88.56 3 16. Wed Aug 7 05:49:58 2019 kern.warn kernel: [ 582.804000] HTB: quantum of class 10001 is big. Consider r2q change. Before you ask... I have factory reset the router, tried changing all possible settings, downgraded to original R1 firmware with slightly better results, swapped ethernet cables, swapped ports, etc etc...
Administrators Netduma Fraser Posted August 7, 2019 Administrators Posted August 7, 2019 Hey, welcome to the forum! With the speed fluctuations does this occur on all devices both wired & wireless? When issue happens if you test direct to the ISP modem/router do you get full speeds? How often does it occur? Is it just during peak hours for example.
Mxcone17 Posted August 7, 2019 Author Posted August 7, 2019 Hey Fraser! It occurs on all devices both wired and wireless. I do get full speed from the modem, I also get full speeds using a different router too. It occurs 24/7 😣 Iv tried changing Qos to never and to always with no change. I have turned wifi off to no avail.
Administrators Netduma Fraser Posted August 7, 2019 Administrators Posted August 7, 2019 Thanks for the info, if you disable QoS fully from the Anti-Bufferbloat 3 line menu does that make any difference?
Administrators Netduma Fraser Posted August 7, 2019 Administrators Posted August 7, 2019 When you've done a factory reset do you make changes to your settings immediately and then the issue happens or do you leave it all default and it still occurs?
Mxcone17 Posted August 7, 2019 Author Posted August 7, 2019 I leave it at default for a while and issues still occur.
Administrators Netduma Fraser Posted August 7, 2019 Administrators Posted August 7, 2019 What is your exact physical setup? What modem model are you using - is it in router or modem mode? How are you connected e.g. PPPoE, VLAN, using DMZ?
Mxcone17 Posted August 7, 2019 Author Posted August 7, 2019 The physical setup is Modem (cm600, cable modem only) - netduma r1 - wired devices . The modem is NOT a modem/router combo, it is just a cable modem. No pppoe, dmz, etc.
Administrators Netduma Fraser Posted August 7, 2019 Administrators Posted August 7, 2019 Does your modem have any diagnostics at all on an interface that could potentially show if there are any minor disconnects happening between modem & router?
Mxcone17 Posted August 7, 2019 Author Posted August 7, 2019 It has an event log, but no reported disconnects.
Administrators Netduma Alex Posted August 8, 2019 Administrators Posted August 8, 2019 When you use a different router, do you use the same ethernet cable?
Administrators Netduma Alex Posted August 8, 2019 Administrators Posted August 8, 2019 What speeds are you expecting from your line? What speeds does the R1 drop to?
Mxcone17 Posted August 8, 2019 Author Posted August 8, 2019 The left is with a regular router, the right of the red line is with the r1. Without QoS I expect 95 or more , but with netduma I usually get 40 or less.
Administrators Netduma Fraser Posted August 8, 2019 Administrators Posted August 8, 2019 Could you try this please, modem > another router > R1 with no other devices connected just a PC wired to the R1 and see what your speeds are then please? Wondering if theres some weird incompatibility between modem and R1.
Mxcone17 Posted August 9, 2019 Author Posted August 9, 2019 Just tried it and getting the same results.
Administrators Netduma Alex Posted August 9, 2019 Administrators Posted August 9, 2019 How old is your R1?
Mxcone17 Posted August 9, 2019 Author Posted August 9, 2019 Um, not entirely sure... pretty old I believe.
Mxcone17 Posted August 9, 2019 Author Posted August 9, 2019 I got it back when I was actually gaming a lot. I checked my emails but I regularly clean it out so nothing email wise that goes far back.
Administrators Netduma Fraser Posted August 10, 2019 Administrators Posted August 10, 2019 On the R1 override the MAC address and use the MAC address of the other router you have instead then apply and reboot both modem and R1, does that help?
Administrators Netduma Fraser Posted August 11, 2019 Administrators Posted August 11, 2019 Change the bandwidth speeds in Anti-Bufferbloat to 1000/1000 and switch to never, does that enable you to get higher speeds?
Administrators Netduma Fraser Posted August 11, 2019 Administrators Posted August 11, 2019 I'll pass this onto the team as I cannot think of what could be causing this, they may have some ideas.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.