Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Rob <rob00si@fastmail.fm>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wshaper syntax, edonkey
Date: Sun, 17 Nov 2002 16:58:36 +0000	[thread overview]
Message-ID: <marc-lartc-103755267620870@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103752292106628@msgid-missing>

try: 

# low priority source ports
NOPRIOPORTSRC='4661 4662 4665 1214'

# low priority destination ports
NOPRIOPORTDST='4661 4662 4665 1214'

the ticks are the key :)

-Rob

On Sun, 17 Nov 2002 03:46:58 -0500 (EST)
war_pig <war_pig@toddallen.mine.nu> wrote:

> hi
> i had wshaper working fine to keep kazza and DC from eating up
> everything, but im having some troubles getting edonkey/emule under
> control.
> 
> part of it is, i cant figure out how to pass multiple ports to the vars
> in the script
> 
> everything i have tried gets an illegal match error, and i see a "for $a
> do" in there...
> 
> also, im not familiar with edonkeys ports, beyond one port that I set,
> and a number of other varialbe ports in the 3000-3500 range it seems to
> listen and make connections on
> 
> i know this is a n00b question...
> 
> -- 
> 
> 
> But it was all right, everything was all right, the struggle was
> finished. He had won the victory over himself. He loved Big Brother. 
> 
> 
> 
> 
> _______________________________________________
> 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/

      reply	other threads:[~2002-11-17 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17  8:46 [LARTC] wshaper syntax, edonkey war_pig
2002-11-17 16:58 ` Rob [this message]

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-103755267620870@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox