All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Why my script doesn't work ???
Date: Sat, 07 Dec 2002 15:11:45 +0000	[thread overview]
Message-ID: <marc-lartc-103927397810261@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103926856707555@msgid-missing>

On Saturday 07 December 2002 14:44, Gabor Csuri wrote:
> Hi All,
>
>  I'm using iptables-1.2.7a on RedHat8 kernel 2.4.20.
> I wanted to limit the file-sharing traffic to the internet.
> I marked the packets with iptables:
>
> iptables -A FORWARD -t mangle -p tcp -s 192.168.1.1/24 -d !
> 192.168.1.1/24 --dport 1024:1862 -j MARK --set-mark 1
>
> iptables -A FORWARD -t mangle -p tcp -s 192.168.1.1/24 -d !
> 192.168.1.1/24 --dport 1864:65535 -j MARK --set-mark 1
>
> and I put some new lines to wondershaper 1.1a (before "#start filters"
> label) :
>
> tc class add dev $DEV parent 1:1 classid 1:40 cbq rate $[$UPLINK/10]kbit \
>    allot 1600 prio 2 avpkt 1000
> tc qdisc add dev $DEV parent 1:40 handle 40: sfq perturb 10
> tc filter add dev $DEV parent 1:0 protocol ip handle 1 fw flowid 1:40
>
> #start filters
> ...
>
> I realized there is a 80Kbit/s traffic to a site (port 2334) from inside.
> My $UPLINK is 80.
> How can be this?
Can you check the counters of iptables so you are sure you are marking the 
packets ???  And the same for tc : tc -s -d show class deb eth0.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  reply	other threads:[~2002-12-07 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-07 13:44 [LARTC] Why my script doesn't work ??? Gabor Csuri
2002-12-07 15:11 ` Stef Coene [this message]
2002-12-07 21:41 ` Gabor Csuri
2002-12-08 12:13 ` Stef Coene
2002-12-08 22:28 ` Gabor Csuri

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-103927397810261@msgid-missing \
    --to=stef.coene@docum.org \
    --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.