All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadtec <vadtec@vadtec.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: LARTC Digest, Vol 31, Issue 25
Date: Tue, 18 Sep 2007 15:02:52 +0000	[thread overview]
Message-ID: <46EFE89C.2090003@vadtec.net> (raw)

>
> Message: 6 Date: Tue, 18 Sep 2007 10:44:42 +0200 From: Michal Soltys 
> <nozo@ziu.info> Subject: Re: [LARTC] I'm having an issue with u32 
> masking To: lartc@mailman.ds9a.nl Message-ID: 
> <46EF8FFA.6070707@ziu.info> Content-Type: text/plain; 
> charset=ISO-8859-1; format=flowed Vadtec wrote:
>> > Is this how tc is supposed to work? Does it only match on the value it 
>> > is given based on whether or not the mask matches? IE: u16 0x1a00 0x1a0f 
>> > at 22 (dest port 6656 ONLY), u16 0x1a0b 0x1a0f at 22 (dest port 6667 ONLY)
>> > 
>> > If so, how can you match a range of ports (in my example, or a range of 
>> > anything for that matter) in tc?
>> > 
>>     
>
> Try:
>
> match u16 0x1a00 0xfff0
>
> Mask is first applied to the value in the packet, then it's tested 
> against your (0x1a00) value
Can you please explain this further?

You are saying that its ORed with the value? Or is it ANDed? Or maybe 
XORed? What operation are they applying to the value? Working from what 
I have done with other bit masking operations, I am assuming that the 
mask is ANDed with the value in the packet. Then I would assume you OR 
the check with the resulting value. But I am not sure.

I would expect the mask to be applied to the value. It doesn't make 
sense to apply it to the check, because then you would simply match the 
highest possible value of the check+mask.


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

                 reply	other threads:[~2007-09-18 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=46EFE89C.2090003@vadtec.net \
    --to=vadtec@vadtec.net \
    --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.