* [LARTC] fw and u32 together...
@ 2002-11-28 16:02 Michal Kustosik
2002-11-28 16:18 ` Stef Coene
2002-11-28 16:22 ` Michal Kustosik
0 siblings, 2 replies; 3+ messages in thread
From: Michal Kustosik @ 2002-11-28 16:02 UTC (permalink / raw)
To: lartc
hello...
1.
Is it possible using u32 to filter marked packets? I have found only documents to fw filter to filter marked packets...
2.
If u32 cannot filter marked packets is it possible to use fw and u32 together? I wanted to filter packets marked by iptables by fw, and packets depended on ip destination, src and others by u32, but something goes wrong :(
the filters configuration is:
$TC filter add dev $DEV_OUT parent 1: protocol ip prio 1 handle 2 fw flowid 1:10
$TC filter add dev $DEV_OUT parent 1: protocol ip prio 1 u32 \
match ip src 10.0.5.5 flowid 1:30
If I use one of them everything is ok, but they don't want to work together:
"RTNETLINK answers: Invalid argument"
thanks...
/michal
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [LARTC] fw and u32 together...
2002-11-28 16:02 [LARTC] fw and u32 together Michal Kustosik
@ 2002-11-28 16:18 ` Stef Coene
2002-11-28 16:22 ` Michal Kustosik
1 sibling, 0 replies; 3+ messages in thread
From: Stef Coene @ 2002-11-28 16:18 UTC (permalink / raw)
To: lartc
On Thursday 28 November 2002 17:02, Michal Kustosik wrote:
> hello...
>
> 1.
> Is it possible using u32 to filter marked packets? I have found only
> documents to fw filter to filter marked packets...
You need the fw filter.
> 2.
> If u32 cannot filter marked packets is it possible to use fw and u32
> together? I wanted to filter packets marked by iptables by fw, and packets
> depended on ip destination, src and others by u32, but something goes wrong
> :(
>
> the filters configuration is:
> $TC filter add dev $DEV_OUT parent 1: protocol ip prio 1 handle 2 fw flowid
> 1:10 $TC filter add dev $DEV_OUT parent 1: protocol ip prio 1 u32 \
> match ip src 10.0.5.5 flowid 1:30
>
> If I use one of them everything is ok, but they don't want to work
I never tried it so I don't know if it can be done. What if you give them a
different prio ??
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [LARTC] fw and u32 together...
2002-11-28 16:02 [LARTC] fw and u32 together Michal Kustosik
2002-11-28 16:18 ` Stef Coene
@ 2002-11-28 16:22 ` Michal Kustosik
1 sibling, 0 replies; 3+ messages in thread
From: Michal Kustosik @ 2002-11-28 16:22 UTC (permalink / raw)
To: lartc
On Thu, Nov 28, 2002 at 05:18:43PM +0100, Stef Coene wrote:
> On Thursday 28 November 2002 17:02, Michal Kustosik wrote:
[...]
> >
> > the filters configuration is:
> > $TC filter add dev $DEV_OUT parent 1: protocol ip prio 1 handle 2 fw flowid
> > 1:10 $TC filter add dev $DEV_OUT parent 1: protocol ip prio 1 u32 \
> > match ip src 10.0.5.5 flowid 1:30
> >
> > If I use one of them everything is ok, but they don't want to work
> I never tried it so I don't know if it can be done. What if you give them a
> different prio ??
>
it works good with different prio...
thanks...
/michal
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-11-28 16:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-28 16:02 [LARTC] fw and u32 together Michal Kustosik
2002-11-28 16:18 ` Stef Coene
2002-11-28 16:22 ` Michal Kustosik
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.