From: Alexey Talikov <alexey_talikov@texlab.com.uz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] U32 classifier filter
Date: Sat, 08 Jun 2002 14:43:48 +0000 [thread overview]
Message-ID: <marc-lartc-102354747121661@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102354388019810@msgid-missing>
http://www.linux.net.pl/cbq/selector.html
and Advanced Routing HOWTO
08.06.2002 18:43:32, Kim Oppalfens <kimoppalfens@freegates.be> wrote:
>Hi,
>
>I don't really know if this is the correct list for asking this, if not a
>referral to the correct list would
>be very much appreciated.
>
>Ok here it goes. I would like to create a u32 filter for tcp packets that
>are larger then 1480 bytes
>but I am not really sure how of if this can be done. I know about the
>pattern and mask thing but
>I am not terribly familiar with the masking thing. I think my ip basics are
>good enough though.
>
>Second question I have is another rule I would like to create for packets
>that are destined for the ports 441,412&413.
>Can I create one rule for that or should I create 3 separate rules?
>
>Last question accept for the linux advanced routing & traffic shaping how
>to is there a place where I can get
>more info & examples on the u32 classifier??
>
>Thanks in advance
>Kim
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
-----------------------------------
mailto:alexey_talikov@texlab.com.uz
BR
Alexey Talikov
FORTEK
-----------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-06-08 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 13:43 [LARTC] U32 classifier filter Kim Oppalfens
2002-06-08 14:43 ` Alexey Talikov [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-102354747121661@msgid-missing \
--to=alexey_talikov@texlab.com.uz \
--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.