Topic: QoS : Packet marking doesn't work by default on boot.

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

Page 1 of 1

Post #1

zorxd

25 Nov 2009, 20:42

I use kamikaze 8.09 r15845 on my WL-500gP v1, braodcom CPU, Atheros wifi router.
I use the qos-script package. I am not sure that QoS is working after reboot

When I look at /proc/net/ip_conntrack, I only see mark=0. If I do "/etc/init.d/qos restart", then packets get marked (I get a lot of mark=4 when using bittorrent). I am not sure but it might have to do with the fact that qos is probably starting before the pppoe connection is established (so the ppp0 device doesn't exist at this stage on boot).

Could anyone using QoS and PPPoE tell me if you have the same problem?

(Last edited by zorxd on 25 Nov 2009, 20:43)

Post #2

Nilfred

26 Nov 2009, 03:12

r17427 here, no problems. Heavy bittorrent ongoing.
qos-scripts 1.2.1-2
ppp 2.4.4-1
ppp-mod-pppoe 2.4.4-1
Uptime: 22 days, 14:25

Post #3

zorxd

26 Nov 2009, 03:13

thanks, but could you check

 grep mark=4 /proc/net/ip_conntrack -c

just to make sure that it is >0?
Also, make sure that you did not modify QoS setting or restart the service since last reboot.
I guess your version is post 8.09.1?

(Last edited by zorxd on 26 Nov 2009, 03:16)

Post #4

Nilfred

26 Nov 2009, 18:41

Using username "root".
Authenticating with public key "..."


BusyBox v1.13.4 (2009-08-27 13:47:21 CDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge, r17427) -------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
# grep mark=4 /proc/net/ip_conntrack -c
108
# uptime # Last reboot, last modify
 14:30:36 up 23 days,  5:48, load average: 0.00, 0.00, 0.00
# cat /proc/version
Linux version 2.6.30.5 (buildbot@localhost.localdomain) (gcc version 4.1.2) #5 Fri Aug 28 11:26:22 CDT 2009
# ls -li /var/run
   1334 -rw-r--r--    1 root     root            5 Dec 31  1969 crond.pid
   1759 -rw-r--r--    1 root     root            5 Dec 31  1969 dnsmasq.pid
   1340 -rw-r--r--    1 root     root            5 Dec 31  1969 dropbear.1.pid
 319326 -rw-r--r--    1 root     root           11 Nov 26 13:02 ppp-wan.pid
 319327 -rw-r--r--    1 root     root            6 Nov 26 13:02 ppp0.pid
 107219 -rw-r--r--    1 root     root           56 Nov 13 19:27 uci_trigger
   2937 -rw-r--r--    1 root     root            5 Nov  3 12:00 vnstat.pid

Don't know how to get Kamikaze version number, but sure is trunk version.
Don't know if QoS was (automatically) restarted. PPP do frequently (manually and due to lack of activity)

(Last edited by Nilfred on 26 Nov 2009, 18:52)

Post #5

zorxd

26 Nov 2009, 19:14

Ok yes your version is much newer, maybe it was fixed. I would like to know if it's fixed in 8.09.X or only in trunk (I woudn't upgrade to trunk without a good reason, last time I tried, the luci GUI was broken and there was a few other issues)

(Last edited by zorxd on 26 Nov 2009, 19:15)

The discussion might have continued from here.

Page 1 of 1