All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob <rob00si@fastmail.fm>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: wondershaper kills eth0 :(
Date: Thu, 31 Oct 2002 04:46:18 +0000	[thread overview]
Message-ID: <marc-lartc-103603990320773@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103601373730922@msgid-missing>

Hi,

Ok, here is the output of the script w/ the '-x'

+ DOWNLINK\x1450
+ UPLINK\x180
+ DEV=eth0
+ NOPRIOHOSTSRC€
+ NOPRIOHOSTDST+ NOPRIOPORTSRC+ NOPRIOPORTDST+ '[' start = status ']'
+ tc qdisc del dev eth0 root
+ tc qdisc del dev eth0 ingress
+ '[' start = stop ']'
+ tc qdisc add dev eth0 root handle 1: cbq avpkt 1000 bandwidth 10mbit
+ tc class add dev eth0 parent 1: classid 1:1 cbq rate 180kbit allot 1500 prio 5 bounded isolated
+ tc class add dev eth0 parent 1:1 classid 1:10 cbq rate 180kbit allot 1600 prio 1 avpkt 1000
+ tc class add dev eth0 parent 1:1 classid 1:20 cbq rate 162kbit allot 1600 prio 2 avpkt 1000
+ tc class add dev eth0 parent 1:1 classid 1:30 cbq rate 144kbit allot 1600 prio 2 avpkt 1000
+ tc qdisc add dev eth0 parent 1:10 handle 10: sfq perturb 10
+ tc qdisc add dev eth0 parent 1:20 handle 20: sfq perturb 10
+ tc qdisc add dev eth0 parent 1:30 handle 30: sfq perturb 10
+ tc filter add dev eth0 parent 1:0 protocol ip prio 10 u32 match ip tos 0x10 0xff flowid 1:10
+ tc filter add dev eth0 parent 1:0 protocol ip prio 11 u32 match ip protocol 1 0xff flowid 1:10
+ tc filter add dev eth0 parent 1: protocol ip prio 12 u32 match ip protocol 6 0xff match u8 0x05 0x0f at 0 match u16 0x0000 0xffc0 at 2 flowid 1:10
+ tc filter add dev eth0 parent 1: protocol ip prio 16 u32 match ip src 80 flowid 1:30
+ tc filter add dev eth0 parent 1: protocol ip prio 18 u32 match ip dst 0.0.0.0/0 flowid 1:20
+ tc qdisc add dev eth0 handle ffff: ingress
+ tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src 0.0.0.0/0 police rate 1450kbit burst 10k drop flowid :1

================================

Do you see anything obvious?  The commands that kill the connection in the
last one... seems to drop all pacets instead of being selective... *sigh*

Anyway, thanks for ANY help you can give :)

-Rob
On Wed, 30 Oct 2002 19:34:30 -0800
Kenneth Porter <shiva@sewingwitch.com> wrote:

> --On Wednesday, October 30, 2002 10:07 PM -0500 Rob <rob00si@fastmail.fm>
> wrote:
> 
> ># low priority OUTGOING traffic - you can leave this blank if you want
> ># low priority source netmasks
> > NOPRIOHOSTSRC€
> 
> BTW, this looks like a bug in the script. The 80 should be the value for
> NOPRIOPORTSRC. (But this shouldn't kill the connection.)
> 
> You might try throwing a "set -x" at the top of the script to expand and
> echo commands before they execute, to see what's really getting issued.
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-10-31  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 21:35 [LARTC] Re: wondershaper kills eth0 :( Rob
2002-10-30 23:27 ` Kenneth Porter
2002-10-31  3:07 ` Rob
2002-10-31  3:34 ` Kenneth Porter
2002-10-31  4:46 ` Rob [this message]
2002-11-01  1:33 ` Kenneth Porter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-103603990320773@msgid-missing \
    --to=rob00si@fastmail.fm \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.