Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Report issues relating to bandwith monitoring, bandwidth quotas or QoS in this forum.

Moderator: Moderators

User avatar
labou
Posts: 14
Joined: Mon Feb 05, 2018 6:55 pm
Contact:

Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Postby labou » Tue Apr 10, 2018 4:30 pm

I've setup the Archer C7v2 and the WRT1200 with the same QoS classes and rules. When I run a dslreports test on both of them, the rules get captured in the class section differently. On the Archer C7v2 everything gets captured as it should. On the WRT1200 it seems to be unable to identify some of the traffic and dumps it into the default service class. The pictures below make it clearer.

Archer C7v2 Classes (As DSLReports Test is Downloading)
Image

WRT1200 Classes (As DSLReports Test is Downloading)
Image

Archer C7v2 Rules
Image

WRT1200 Rules
Image

If I make a rule that is simply port 80 on the WRT1200, it captures the dslreports test traffic. If I add a maximum or minimum packet rule to the same rule, it stops capturing the traffic from the test.

I've run the test with the stable 1.10 on both and I also tried the 1.10.X (Built 20180313-1844 git@68ce297) on the WRT1200 to see if that helped, but no luck.

Any ideas???
TP-Link Archer C7 v2
Linksys WRT1200AC

User avatar
labou
Posts: 14
Joined: Mon Feb 05, 2018 6:55 pm
Contact:

Re: Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Postby labou » Fri Apr 27, 2018 11:58 am

Bumping my post. I'm still curious about this and would be happy if someone could shed some light on it for me.
TP-Link Archer C7 v2
Linksys WRT1200AC

Lantis
Moderator
Posts: 4134
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Postby Lantis » Sat Apr 28, 2018 7:33 pm

Can you please provide a system log after saving qos settings on each one to compare please?
WRT1900AC V1 on 1.10.X
WNDR3800/WRT3200ACM in a constant state of flux
www.lantisproject.com for custom builds and other projects
www.lantisproject.com/gargoyle_ispyisail/ for the latest releases

User avatar
labou
Posts: 14
Joined: Mon Feb 05, 2018 6:55 pm
Contact:

Re: Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Postby labou » Fri May 04, 2018 11:24 pm

I had to matchup the settings again. I'm pretty sure they are matched up exactly on the last save on each of them.

Archer C7v2

Code: Select all

Fri May  4 23:08:49 2018 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0)
Fri May  4 23:08:51 2018 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Fri May  4 23:08:56 2018 kern.warn kernel: [   81.540000] ipt_bandwidth: timezone shift of 240 minutes detected, adjusting
Fri May  4 23:08:56 2018 kern.warn kernel: [   81.550000]                old minutes west=0, new minutes west=240
Fri May  4 23:09:01 2018 kern.info kernel: [   86.380000] IMQ driver unloaded successfully.
Fri May  4 23:09:01 2018 kern.info kernel: [   86.410000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:09:01 2018 kern.info kernel: [   86.410000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:09:01 2018 kern.info kernel: [   86.420000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:09:01 2018 kern.info kernel: [   86.420000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:09:01 2018 kern.info kernel: [   86.430000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:09:01 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:09:01 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:09:01 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:09:01 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:09:08 2018 local5.info qosmon[6121]: starting socketfd = 5, statusfd = 4
Fri May  4 23:09:12 2018 daemon.info hostapd: wlan1: STA a8:a1:98:76:20:7f IEEE 802.11: authenticated
Fri May  4 23:09:12 2018 daemon.info hostapd: wlan1: STA a8:a1:98:76:20:7f IEEE 802.11: associated (aid 2)
Fri May  4 23:09:12 2018 daemon.info hostapd: wlan1: STA a8:a1:98:76:20:7f RADIUS: starting accounting session 08E44805103AD80F
Fri May  4 23:09:12 2018 daemon.info hostapd: wlan1: STA a8:a1:98:76:20:7f WPA: pairwise key handshake completed (RSN)
Fri May  4 23:09:16 2018 daemon.info dnsmasq-dhcp[2700]: DHCPDISCOVER(br-lan) a8:a1:98:76:20:7f
Fri May  4 23:09:16 2018 daemon.info dnsmasq-dhcp[2700]: DHCPOFFER(br-lan) 192.168.1.29 a8:a1:98:76:20:7f
Fri May  4 23:09:16 2018 daemon.info dnsmasq-dhcp[2700]: DHCPREQUEST(br-lan) 192.168.1.29 a8:a1:98:76:20:7f
Fri May  4 23:09:16 2018 daemon.info dnsmasq-dhcp[2700]: DHCPACK(br-lan) 192.168.1.29 a8:a1:98:76:20:7f android-50a7610a19bfeb1f
Fri May  4 23:11:13 2018 local5.notice qosmon[6121]: terminated sigterm=15, sel_err=-1
Fri May  4 23:11:13 2018 kern.info kernel: [  218.520000] IMQ driver unloaded successfully.
Fri May  4 23:11:13 2018 kern.info kernel: [  218.560000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:11:13 2018 kern.info kernel: [  218.560000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:11:13 2018 kern.info kernel: [  218.570000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:11:13 2018 kern.info kernel: [  218.570000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:11:13 2018 kern.info kernel: [  218.580000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:11:13 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:11:13 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:11:13 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:11:13 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:11:17 2018 local5.info qosmon[8184]: starting socketfd = 6, statusfd = 4
Fri May  4 23:13:27 2018 local5.notice qosmon[8184]: terminated sigterm=15, sel_err=-1
Fri May  4 23:13:27 2018 kern.info kernel: [  352.810000] IMQ driver unloaded successfully.
Fri May  4 23:13:27 2018 kern.info kernel: [  352.830000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:13:27 2018 kern.info kernel: [  352.840000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:13:27 2018 kern.info kernel: [  352.840000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:13:27 2018 kern.info kernel: [  352.850000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:13:27 2018 kern.info kernel: [  352.860000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:13:27 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:13:27 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:13:27 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:13:27 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:13:30 2018 local5.info qosmon[10300]: starting socketfd = 6, statusfd = 4
Fri May  4 23:14:48 2018 local5.notice qosmon[10300]: terminated sigterm=15, sel_err=-1
Fri May  4 23:14:49 2018 kern.info kernel: [  434.150000] IMQ driver unloaded successfully.
Fri May  4 23:14:49 2018 kern.info kernel: [  434.170000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:14:49 2018 kern.info kernel: [  434.170000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:14:49 2018 kern.info kernel: [  434.170000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:14:49 2018 kern.info kernel: [  434.180000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:14:49 2018 kern.info kernel: [  434.190000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:14:49 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:14:49 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:14:49 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:14:49 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:14:51 2018 local5.info qosmon[12649]: starting socketfd = 6, statusfd = 4
Fri May  4 23:15:31 2018 local5.notice qosmon[12649]: terminated sigterm=15, sel_err=-1
Fri May  4 23:15:31 2018 kern.info kernel: [  476.950000] IMQ driver unloaded successfully.
Fri May  4 23:15:31 2018 kern.info kernel: [  476.980000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:15:31 2018 kern.info kernel: [  476.980000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:15:31 2018 kern.info kernel: [  476.990000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:15:31 2018 kern.info kernel: [  476.990000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:15:31 2018 kern.info kernel: [  477.000000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:15:31 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:15:31 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:15:31 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:15:32 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:15:34 2018 local5.info qosmon[14857]: starting socketfd = 6, statusfd = 4
Fri May  4 23:16:03 2018 daemon.err uhttpd[1632]: sh: write error: Broken pipe
Fri May  4 23:16:27 2018 local5.notice qosmon[14857]: terminated sigterm=15, sel_err=-1
Fri May  4 23:16:27 2018 kern.info kernel: [  532.510000] IMQ driver unloaded successfully.
Fri May  4 23:16:27 2018 kern.info kernel: [  532.550000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:16:27 2018 kern.info kernel: [  532.550000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:16:27 2018 kern.info kernel: [  532.560000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:16:27 2018 kern.info kernel: [  532.560000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:16:27 2018 kern.info kernel: [  532.570000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:16:27 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:16:27 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:16:27 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:16:27 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:16:29 2018 local5.info qosmon[17336]: starting socketfd = 6, statusfd = 4
Fri May  4 23:17:35 2018 daemon.err uhttpd[1632]: .........................................+++
Fri May  4 23:17:37 2018 daemon.err uhttpd[1632]: ...................................................+++
Fri May  4 23:17:38 2018 daemon.err uhttpd[1632]: Signature ok
Fri May  4 23:17:38 2018 daemon.err uhttpd[1632]: subject=/O=gargoyle-router.com/CN=Gargoyle Router Management Utility
Fri May  4 23:17:38 2018 daemon.err uhttpd[1632]: Getting Private key
Fri May  4 23:17:38 2018 daemon.err uhttpd[1632]: unable to write 'random state'
Fri May  4 23:17:38 2018 daemon.err uhttpd[1632]: chmod: uhttpd.key: No such file or directory
Fri May  4 23:17:38 2018 daemon.err uhttpd[1632]: chmod: uhttpd.crt: No such file or directory
Fri May  4 23:17:38 2018 daemon.err uhttpd[1632]: rm: can't remove '/etc/dropbear/authorized_keys': No such file or directory
Fri May  4 23:17:40 2018 local5.notice qosmon[17336]: terminated sigterm=15, sel_err=-1
Fri May  4 23:17:43 2018 kern.info kernel: [  608.590000] IMQ driver unloaded successfully.
Fri May  4 23:17:43 2018 kern.info kernel: [  608.620000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:17:43 2018 kern.info kernel: [  608.620000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:17:43 2018 kern.info kernel: [  608.630000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:17:43 2018 kern.info kernel: [  608.630000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:17:43 2018 kern.info kernel: [  608.640000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:17:43 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:17:43 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:17:43 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:17:43 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:17:45 2018 local5.info qosmon[20083]: starting socketfd = 6, statusfd = 4
Fri May  4 23:17:50 2018 authpriv.info dropbear[1596]: Early exit: Terminated by signal
Fri May  4 23:17:51 2018 authpriv.info dropbear[21505]: Not backgrounding
Fri May  4 23:18:09 2018 daemon.info hostapd: wlan1: STA b8:27:eb:db:32:15 WPA: group key handshake completed (RSN)
Fri May  4 23:18:09 2018 daemon.info hostapd: wlan1: STA a8:a1:98:76:20:7f WPA: group key handshake completed (RSN)
Fri May  4 23:18:13 2018 daemon.info hostapd: wlan0: STA 94:65:2d:db:5d:02 WPA: group key handshake completed (RSN)
Fri May  4 23:18:47 2018 local5.notice qosmon[20083]: terminated sigterm=15, sel_err=-1
Fri May  4 23:18:51 2018 kern.info kernel: [  676.110000] IMQ driver unloaded successfully.
Fri May  4 23:18:51 2018 kern.info kernel: [  676.140000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:18:51 2018 kern.info kernel: [  676.140000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:18:51 2018 kern.info kernel: [  676.140000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:18:51 2018 kern.info kernel: [  676.150000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:18:51 2018 kern.info kernel: [  676.160000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:18:51 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:18:51 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:18:51 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:18:51 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:18:53 2018 local5.info qosmon[22597]: starting socketfd = 6, statusfd = 4
Fri May  4 23:20:06 2018 local5.notice qosmon[22597]: terminated sigterm=15, sel_err=-1
Fri May  4 23:20:07 2018 kern.info kernel: [  752.380000] IMQ driver unloaded successfully.
Fri May  4 23:20:07 2018 kern.info kernel: [  752.400000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:20:07 2018 kern.info kernel: [  752.410000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:20:07 2018 kern.info kernel: [  752.410000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:20:07 2018 kern.info kernel: [  752.420000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:20:07 2018 kern.info kernel: [  752.430000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:20:07 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:20:07 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:20:07 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:20:07 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:20:09 2018 local5.info qosmon[25153]: starting socketfd = 6, statusfd = 4
Fri May  4 23:20:31 2018 local5.notice qosmon[25153]: terminated sigterm=15, sel_err=-1
Fri May  4 23:20:31 2018 kern.info kernel: [  776.790000] IMQ driver unloaded successfully.
Fri May  4 23:20:31 2018 kern.info kernel: [  776.820000]    Hooked IMQ after mangle on INPUT
Fri May  4 23:20:31 2018 kern.info kernel: [  776.820000]    Hooked IMQ after mangle on FORWARD
Fri May  4 23:20:31 2018 kern.info kernel: [  776.830000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 23:20:31 2018 kern.info kernel: [  776.830000]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 23:20:31 2018 kern.info kernel: [  776.840000]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 23:20:31 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 23:20:31 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 23:20:31 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 23:20:31 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 23:20:34 2018 local5.info qosmon[27269]: starting socketfd = 6, statusfd = 4
Success


WRT1200

Code: Select all

Fri May  4 22:18:40 2018 daemon.info hostapd: wlan1: STA b8:27:eb:db:32:15 WPA: group key handshake completed (RSN)
Fri May  4 22:18:40 2018 daemon.info hostapd: wlan1: STA a8:a1:98:76:20:7f WPA: group key handshake completed (RSN)
Fri May  4 22:18:40 2018 daemon.info hostapd: wlan0: STA d4:25:8b:6e:62:61 WPA: group key handshake completed (RSN)
Fri May  4 22:18:41 2018 daemon.info hostapd: wlan0: STA 94:65:2d:db:5d:02 WPA: group key handshake completed (RSN)
Fri May  4 22:28:40 2018 daemon.info hostapd: wlan1: STA b8:27:eb:db:32:15 WPA: group key handshake completed (RSN)
Fri May  4 22:28:40 2018 daemon.info hostapd: wlan1: STA a8:a1:98:76:20:7f WPA: group key handshake completed (RSN)
Fri May  4 22:28:40 2018 daemon.info hostapd: wlan0: STA d4:25:8b:6e:62:61 WPA: group key handshake completed (RSN)
Fri May  4 22:28:41 2018 daemon.info hostapd: wlan0: STA 94:65:2d:db:5d:02 WPA: group key handshake completed (RSN)
Fri May  4 22:33:27 2018 kern.info kernel: [255302.594419] IMQ driver unloaded successfully.
Fri May  4 22:33:27 2018 kern.info kernel: [255302.603969]    Hooked IMQ after mangle on INPUT
Fri May  4 22:33:27 2018 kern.info kernel: [255302.608468]    Hooked IMQ after mangle on FORWARD
Fri May  4 22:33:27 2018 kern.info kernel: [255302.613118] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 22:33:27 2018 kern.info kernel: [255302.622392]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 22:33:27 2018 kern.info kernel: [255302.627306]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 22:33:27 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 22:33:27 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 22:33:27 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 22:33:27 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 22:33:50 2018 kern.info kernel: [255326.093949] IMQ driver unloaded successfully.
Fri May  4 22:33:50 2018 kern.info kernel: [255326.102922]    Hooked IMQ after mangle on INPUT
Fri May  4 22:33:50 2018 kern.info kernel: [255326.107440]    Hooked IMQ after mangle on FORWARD
Fri May  4 22:33:50 2018 kern.info kernel: [255326.112119] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 22:33:50 2018 kern.info kernel: [255326.121416]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 22:33:50 2018 kern.info kernel: [255326.126394]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 22:33:50 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 22:33:50 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 22:33:50 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 22:33:50 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 22:34:30 2018 kern.info kernel: [255365.993126] IMQ driver unloaded successfully.
Fri May  4 22:34:30 2018 kern.info kernel: [255366.002056]    Hooked IMQ after mangle on INPUT
Fri May  4 22:34:30 2018 kern.info kernel: [255366.006551]    Hooked IMQ after mangle on FORWARD
Fri May  4 22:34:30 2018 kern.info kernel: [255366.011203] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 22:34:30 2018 kern.info kernel: [255366.020479]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 22:34:30 2018 kern.info kernel: [255366.025383]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 22:34:30 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 22:34:30 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 22:34:30 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 22:34:30 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 22:34:31 2018 local5.info qosmon[29743]: starting socketfd = 7, statusfd = 4
Fri May  4 22:34:47 2018 kern.info kernel: [255383.272775] IMQ driver unloaded successfully.
Fri May  4 22:34:47 2018 kern.info kernel: [255383.281671]    Hooked IMQ after mangle on INPUT
Fri May  4 22:34:47 2018 kern.info kernel: [255383.286161]    Hooked IMQ after mangle on FORWARD
Fri May  4 22:34:47 2018 kern.info kernel: [255383.290810] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 22:34:47 2018 kern.info kernel: [255383.300107]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 22:34:47 2018 kern.info kernel: [255383.305012]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 22:34:47 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 22:34:47 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 22:34:47 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 22:34:47 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 22:34:48 2018 local5.notice qosmon[29743]: terminated sigterm=15, sel_err=0
Fri May  4 22:34:48 2018 local5.info qosmon[31890]: starting socketfd = 7, statusfd = 4
Fri May  4 22:36:54 2018 kern.info kernel: [255510.190211] IMQ driver unloaded successfully.
Fri May  4 22:36:54 2018 kern.info kernel: [255510.198996]    Hooked IMQ after mangle on INPUT
Fri May  4 22:36:54 2018 kern.info kernel: [255510.203493]    Hooked IMQ after mangle on FORWARD
Fri May  4 22:36:54 2018 kern.info kernel: [255510.208137] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Fri May  4 22:36:54 2018 kern.info kernel: [255510.217419]    Hooking IMQ before NAT on PREROUTING.
Fri May  4 22:36:54 2018 kern.info kernel: [255510.222324]    Hooking IMQ after NAT on POSTROUTING.
Fri May  4 22:36:54 2018 daemon.err insmod: module is already loaded - cls_fw
Fri May  4 22:36:54 2018 daemon.err insmod: module is already loaded - cls_flow
Fri May  4 22:36:54 2018 daemon.err insmod: module is already loaded - sch_hfsc
Fri May  4 22:36:54 2018 daemon.err insmod: module is already loaded - sch_sfq
Fri May  4 22:36:55 2018 local5.notice qosmon[31890]: terminated sigterm=15, sel_err=0
Fri May  4 22:36:55 2018 local5.info qosmon[2100]: starting socketfd = 7, statusfd = 4
TP-Link Archer C7 v2
Linksys WRT1200AC

Lantis
Moderator
Posts: 4134
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Postby Lantis » Sun May 06, 2018 8:55 am

These are both connected in the exact same way?
I don’t have an explanation. I’ve not had time to try to reproduce.
WRT1900AC V1 on 1.10.X
WNDR3800/WRT3200ACM in a constant state of flux
www.lantisproject.com for custom builds and other projects
www.lantisproject.com/gargoyle_ispyisail/ for the latest releases

pbix
Developer
Posts: 1337
Joined: Fri Aug 21, 2009 5:09 pm

Re: Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Postby pbix » Mon May 07, 2018 12:47 pm

Look at the connection list and determine which connections are not classified the way you think they should be.

Post what you find.
Netgear WNDR3700v2
Buffalo WZR-HP-G300NH2
WRT54G-TM

User avatar
labou
Posts: 14
Joined: Mon Feb 05, 2018 6:55 pm
Contact:

Re: Same QoS settings on WRT1200 and Archer C7v2 with different classification/rule results

Postby labou » Tue May 15, 2018 2:43 pm

Thank you for the responses

They are setup the same. Modem -> Router. When I run the test on each I simply turn the one that I'm done with off, remove the ethernet cable from it, and plug the ethernet cable into the other router.

That is a good idea to look at the connection list. Here are the results:

Test 1 WRT1200
Image

Test 2 WRT1200
Image

Test 3 WRT1200
Image

I'm thinking it might be useful to connect the Archer C7 up and see if it is catching these same things differently.
TP-Link Archer C7 v2
Linksys WRT1200AC


Return to “Monitoring / Quota / QoS Issues”

Who is online

Users browsing this forum: No registered users and 4 guests