OpenWrt Forum Archive

Topic: It seemed like bufferbloat but can't be fixed by SQM QoS, pls help

The content of this topic has been archived on 24 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Post #1
Neubulae
25 Aug 2017, 17:17

Sat Aug 26 00:02:56 2017 daemon.info pppd[5707]: CHAP authentication failed
Sat Aug 26 00:02:56 2017 daemon.err pppd[5707]: CHAP authentication failed
Sat Aug 26 00:02:56 2017 daemon.notice pppd[5707]: Modem hangup
Sat Aug 26 00:02:56 2017 daemon.notice pppd[5707]: Connection terminated.
Sat Aug 26 00:02:56 2017 daemon.info pppd[5707]: Sent PADT
Sat Aug 26 00:02:56 2017 daemon.info pppd[5707]: Exit.
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Interface 'wan' is now down
Sat Aug 26 00:02:57 2017 kern.info kernel: [ 2432.170000] eth1: link down
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Interface 'wan' is disabled
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Interface 'wan' is enabled
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Interface 'wan' is setting up now
Sat Aug 26 00:02:57 2017 kern.info kernel: [ 2432.180000] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Network device 'eth1' link is down
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sat Aug 26 00:02:57 2017 kern.debug kernel: [ 2432.920000] ar71xx: pll_reg 0xb8050014: 0x1099
Sat Aug 26 00:02:57 2017 kern.info kernel: [ 2432.920000] eth1: link up (100Mbps/Full duplex)
Sat Aug 26 00:02:57 2017 kern.info kernel: [ 2432.920000] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Network device 'eth1' link is up
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Aug 26 00:02:57 2017 daemon.notice netifd: Interface 'wan' is setting up now
Sat Aug 26 00:02:57 2017 daemon.info pppd[5765]: Plugin rp-pppoe.so loaded.
Sat Aug 26 00:02:57 2017 daemon.info pppd[5765]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sat Aug 26 00:02:57 2017 daemon.notice pppd[5765]: pppd 2.4.7 started by root, uid 0
Sat Aug 26 00:02:58 2017 daemon.info pppd[5765]: PPP session is 24731
Sat Aug 26 00:02:58 2017 daemon.warn pppd[5765]: Connected to 00:e0:fc:b3:da:04 via interface eth1
Sat Aug 26 00:02:58 2017 daemon.info pppd[5765]: Using interface pppoe-wan
Sat Aug 26 00:02:58 2017 daemon.notice pppd[5765]: Connect: pppoe-wan <--> eth1
Sat Aug 26 00:02:58 2017 kern.info kernel: [ 2433.100000] pppoe-wan: renamed from ppp0
Sat Aug 26 00:03:01 2017 daemon.info pppd[5765]: CHAP authentication succeeded: Authentication success,Welcome!
Sat Aug 26 00:03:01 2017 daemon.notice pppd[5765]: CHAP authentication succeeded
Sat Aug 26 00:03:01 2017 daemon.notice pppd[5765]: peer from calling number 00:E0:FC:B3:DA:04 authorized
Sat Aug 26 00:03:01 2017 daemon.notice pppd[5765]: local  IP address 100.64.207.52
Sat Aug 26 00:03:01 2017 daemon.notice pppd[5765]: remote IP address 100.64.0.1
Sat Aug 26 00:03:01 2017 daemon.notice pppd[5765]: primary   DNS address 218.85.152.99
Sat Aug 26 00:03:01 2017 daemon.notice pppd[5765]: secondary DNS address 218.85.157.99
Sat Aug 26 00:03:01 2017 daemon.notice netifd: Network device 'pppoe-wan' link is up
Sat Aug 26 00:03:01 2017 daemon.notice netifd: Interface 'wan' is now up
Sat Aug 26 00:03:01 2017 user.notice SQM: /usr/lib/sqm/start-sqm: Starting pppoe-wan
Sat Aug 26 00:03:01 2017 user.notice SQM: /usr/lib/sqm/start-sqm: Queue Setup Script: piece_of_cake.qos
Sat Aug 26 00:03:01 2017 daemon.err modprobe: act_ipt is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: sch_sfq is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: sch_ingress is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: act_mirred is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: cls_fw is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: cls_flow is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: cls_u32 is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: sch_htb is already loaded
Sat Aug 26 00:03:01 2017 daemon.err modprobe: sch_hfsc is already loaded
Sat Aug 26 00:03:01 2017 user.notice SQM: QDISC cake is NOT useable.
Sat Aug 26 00:03:01 2017 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)

The system log looked like this when the problem happens...
I am using IDM to download files and every few seconds the speed would suddenly frop to 0, and the connection will be throttled for a few moment until the modem reconnects or the router reboots.
Speedtest looked like this
dslreports.c*m/speedtest/20774057
Please help(too bad I can't use links...)
I am using that WNDR3800, please help

(Last edited by Neubulae on 25 Aug 2017, 17:27)

Post #2
adri
25 Aug 2017, 21:06

Did you install the cake qdisk (kmod-sched-cake package)?
Looking at your logs, it seems the qdisc isn't installed!

Post #3
Neubulae
25 Aug 2017, 22:33
adri wrote:

Did you install the cake qdisk (kmod-sched-cake package)?
Looking at your logs, it seems the qdisc isn't installed!

How can I install cake package? opkg update 'ed but I can't find it.
Is cake far more better than fql?

Post #4
moeller0
26 Aug 2017, 23:49
Neubulae wrote:
adri wrote:

Did you install the cake qdisk (kmod-sched-cake package)?
Looking at your logs, it seems the qdisc isn't installed!

How can I install cake package? opkg update 'ed but I can't find it.
Is cake far more better than fql?

I would ask you to try the current stable LEDE distribution, as lede does include cake in its packet repository, so it should be easy to install; also a future re-merged Openwrt/lede distribution will be based on current lede so that will already hoist your router into the present and will prepare you well for the future.
I have no idea what fql is, but cake tries to offer what fqcodel + HTB offer, and IMHO it over-achieve its goals. Have a look at https://lede-project.org/docs/howto/sqm for what cake can offer...

Best Regards

(Last edited by moeller0 on 26 Aug 2017, 23:50)

The discussion might have continued from here.