From: "Liu Zhiyong" <liuzhiyo@comp.nus.edu.sg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] to classify non-IP packet???
Date: Thu, 06 Feb 2003 15:23:48 +0000 [thread overview]
Message-ID: <marc-lartc-104454526824754@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104441554705677@msgid-missing>
I have successfully classified QRoute packet from IP packet by adding
{0x8000, "qroute"} to /iproute2/lib/ll_protocol.c, and make iproute2
again,then use: "tc filter add dev eth0 parent 1: prio 5 protocol qroute u32
match u8 0x00 0x00 at 0 flowid 1:10". It will classify the all the qroute
packet to flow 1:10. Now I want to further classify QRoute packet according
to the first 2 bytes of the packet, I have tried to use tc filter add dev
eth0 parent 1: prio 6 protocol qroute u32 match u8 0x40 0xff at 0 flowid
1:20", but it doesn't work! anyone know how to do it?
----- Original Message -----
From: "Liu Zhiyong" <liuzhiyo@comp.nus.edu.sg>
To: <lartc@mailman.ds9a.nl>
Sent: Wednesday, February 05, 2003 11:24 AM
Subject: [LARTC] to classify non-IP packet???
> I implemented a new network protocol(called QRoute), the Eth protocol code
> is 0x8000(for unicast) and 0x8001(for multicast), and there are 2 kind of
> QRoute packets: data packet( the first 2 bytes is 0x40), and control
> packet(the fist 2 bytes is 0x00, 0x10,0x20 or 0x30). There are 3 kinds of
> packets in the network: IP packets, Qroute(including unicast and
> multicast) data packets, and Qroute control packet. I want to classify
> these 3 kinds of packets, how can I do it? I tried to use: "tc filter add
> dev eth0 parent 1:0 protocol ip prio 1 u32 match u16 0x8000 0xffff at -2
> flowid 1:10" to classfiy the Qroute unicast packet, but it doesn't work.
> There is a protocol called "802.1Q" whose Eth protocol code is 0x8001(It
> can be found in "iproute2/lib/lI_proto.c"), so I tried to use "tc filter
> add dev eth0 parent 1:0 protocol 802.1Q prio 1 u32 match u16 0x8000 0xffff
> at -2 flowid 1:10", and it works. but it can't further classify the
> packets according to the first 2 bytes! And I tried to add protocol
> {0x8000, "QRoute"} in "iproute2/lib/lI_proto.c and compiled the iproute2
> packet again, then tried " tc filter add dev eth0 parent 1:0 protocol
> QRoute prio 1 u32 match u16 0x8000 0xffff at -2 flowid 1:10", it still
> doesn't work! anyone can help me ? Thanks very much
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-02-06 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 3:24 [LARTC] to classify non-IP packet??? Liu Zhiyong
2003-02-06 15:23 ` Liu Zhiyong [this message]
2003-02-06 15:23 ` Liu Zhiyong
2003-02-10 14:50 ` Liu Zhiyong
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-104454526824754@msgid-missing \
--to=liuzhiyo@comp.nus.edu.sg \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox