Jump to content
Mxcone17

kill flow due to timeout is flooding logs with ill effect

Recommended Posts

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...

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

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.
1392263960_InkedAnnotation2019-08-08102349_LI.jpg.6a993feb1d1b698505e5ba232ade838e.jpg

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

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

×
×
  • Create New...