All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkap@poczta.onet.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Problem with iptables with -j TOS and MARK
Date: Mon, 31 Jul 2006 06:23:40 +0000	[thread overview]
Message-ID: <eak7k5$fgv$1@sea.gmane.org> (raw)
In-Reply-To: <ead536$d62$1@sea.gmane.org>

On 28-07-2006 15:57, Jarek Poplawski wrote:
> On 28-07-2006 14:43, makevuy wrote:
>> Hy,
>>
>> I would want to mark the packets that are entering in a machine, with 
>> a mark for using diffserv with DSMARK.
>>
>> My machine has 2 interfaces, a ethernet and a wireless. The ethernet 
>> interface is eth1 and the other is wifi0.
>>
>> Firs, I would want to test that I would be able to mark the tos of the 
>> paquets that I would be receiving, for this I write in the console of 
>> my linux:
>>
>>
>> iptables -A PREROUTING -i eth1 -t mangle -p udp -j TOS --set-tos 0x20
>>
>> But the TOS doesn't change (I see this with ethereal)
>>
>> Waht could be the problem?
> 
> If I can remember, TOS is inserted for real some time later, so try to 
> investigate on forward or postrouting.

After short weekend testing my memory turned out to be faulty 
again - it can remember only every second bit (because it's old!).

Iptables -j TOS and -j DSCP should change a tos field of ip 
headers at once (this could be seen with -j LOG everywhere after 
this setting). This field can influent the way a packet is 
classified by some qdisc like prio, but not directly - inner 
priority field is taken for this. And this priority is computed 
from tos only in forward.

So probably ethereal showed packets before changes or you have 
some problem with iptables.

Jarek P.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2006-07-31  6:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 13:57 [LARTC] Re: Problem with iptables with -j TOS and MARK Jarek Poplawski
2006-07-31  6:23 ` Jarek Poplawski [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='eak7k5$fgv$1@sea.gmane.org' \
    --to=jarkap@poczta.onet.pl \
    --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.