From: miller69@gmx.net
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problem with tc filter
Date: Mon, 05 May 2003 19:15:07 +0000 [thread overview]
Message-ID: <marc-lartc-105216220124781@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105215831420329@msgid-missing>
> On Monday 05 May 2003 20:10, miller69@gmx.net wrote:
> > That works very well but at some point of my project i need to switch
> over
> > just using one mark (or more exact using just one firewall-rule) for
> both
> > filters. So i tried to change the second filter:
> >
> > tc filter add dev eth0 parent 1:0 protocol ip prio 4 handle 12 fw
> classid
> > 1:12
> > tc filter add dev eth1 parent 2:0 protocol ip prio 4 handle 12 fw
> classid
> > 2:22
> >
> > That did not work, just the first filter was used but the other never
> > catched a paket. My question: is there a way to handle this by a mask
> for
> > the handle for example? Any hints are very much appreciated!
> Why not doing
> tc filter add dev eth1 parent 1:0 protocol ip prio 4 handle 12 fw classid
> 2:22
I've tried it and the answer was:
RTNETLINK answers: Invalid argument
So that did not work. Any other ideas? I really need this going!
Thanks,
Mike.
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
_______________________________________________
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-05-05 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 18:10 [LARTC] problem with tc filter miller69
2003-05-05 18:39 ` Stef Coene
2003-05-05 19:15 ` miller69 [this message]
2003-05-05 19:20 ` Stef Coene
2003-05-05 21:04 ` miller69
2003-05-06 18:35 ` Stef Coene
2003-05-07 9:39 ` miller69
2003-05-07 16:58 ` Stef Coene
2003-11-23 2:38 ` raz
2003-11-23 10:19 ` Stef Coene
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-105216220124781@msgid-missing \
--to=miller69@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox