From: Arindam Haldar <ahiam@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] icmp bandwidth restriction !!
Date: Thu, 07 Mar 2002 07:19:53 +0000 [thread overview]
Message-ID: <marc-lartc-101548468505283@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101543446311355@msgid-missing>
Arindam Haldar wrote:
> eth wrote:
>
>> Arindam Haldar wrote:
>>
>>> i want help in managing icmp traffic. this is what i tried -->
>>> iptables -t mangle -A PREROUTING -d 10.0.0.0/8 -p 1 -j MARK
>>> --set-mark 4001
>>>
>>> tc filter add dev eth4 parent 5:0 match protocol ip 1 prio 2 handle
>>> 4001 fw classid 5:105
>>>
>>> i tried permutaion of >> match protocol ip 1 << but always getting
>>> different errors.
>>> i want to know whats the syntax for tc when i mark packets with
>>> iptables of icmp type !
>>> iptables -nvL PREROUTING -t mangle does shows figures indicating icmp
>>> packets r inded being marked !
>>
>>
>> If only ICMP is the criterion why bother with iptables? Afterwall the
>> u32 filter of tc can match pretty anything in terms of tcp/ip...
>>
>> If I'm not wrong for example
>>
>> tc filter add dev eth1 protocol ip parent 5:0 prio 2 match ip dst
>> 10.0.0.0/8 match ip protocol 1 0xff flowid 5:105
>>
>> ... would create a filter to match all ICMP traffic destined to 10.0.0.0
>>
>
> # tc filter add dev eth4 parent 5:0 protocol ip prio 2 match ip dst
> 10.0.0.0/8 match ip protocol 1 0xff flowid 5:105
> Unknown filter "match", hence "ip" is unparsable
>
> A.H
>
I AM EXTREMLY SORRY !! ... didnt add u32 to the above !.. :-(
thanx 4 ur help !
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-03-07 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 17:24 [LARTC] icmp bandwidth restriction !! Arindam Haldar
2002-03-07 6:34 ` Arindam Haldar
2002-03-07 7:19 ` Arindam Haldar [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-101548468505283@msgid-missing \
--to=ahiam@yahoo.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.