From: "Tomasz Chilinski" <chilek@chilan.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] mark
Date: Tue, 26 Oct 2004 07:19:35 +0000 [thread overview]
Message-ID: <20041026071134.M25292@chilan.com> (raw)
In-Reply-To: <200403261656.21037.pandre@darkstar.nom.za>
On Tue, 26 Oct 2004 01:43:43 -0200, James Lista wrote
> folks,
Hello James.
> when marking a packet to band control , what is the diffent between:
>
> iptables -t mangle -A PREROUTING -m p2p --p2p all -j CONNMARK --set-mark
> $P2P_MARK
> iptables -t mangle -A PREROUTING -m connmark --mark $P2P_MARK -j
> CONNMARK --restore-mark
>
> and
>
> iptables -t mangle -A PREROUTING -m p2p --p2p all -j MARK --set-mark
> $P2P_MARK
Each p2p connection is composed of many ip packets. p2p match is sensible for
some specific data fields in some these packets. So if you mark only these
packets all other packets (with p2p application data) wont be marked and you
wont limit transfer. Second line in first example marks CONNECTIONs (not
packets) belonged to p2p connection (detected by p2p match). Using second
method has not effect as you would wish.
> ??????
>
> tried to "patch-o-matic" with connmark and didnot work out (kernel
> 2.6.9)... .. it works ok with 2.4.x
It works for me with 2.4.x too. I didnt tried with 2.6.x.
--
Kind regards,
Tomasz Chilinski
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-10-26 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 14:56 [LARTC] mark Paulo Andre
2004-10-26 3:43 ` James Lista
2004-10-26 7:19 ` Tomasz Chilinski [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=20041026071134.M25292@chilan.com \
--to=chilek@chilan.com \
--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.