netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syrius.ml@no-log.org
To: hadi@cyberus.ca
Cc: netdev@oss.sgi.com
Subject: Re: IMQ / new Dummy device post.
Date: Wed, 21 Apr 2004 03:43:13 +0200	[thread overview]
Message-ID: <wazza.87fzayw1fy.fsf@message.id> (raw)
In-Reply-To: <1082427350.1034.70.camel@jzny.localdomain> (hadi@cyberus.ca's message of "19 Apr 2004 22:15:50 -0400")

jamal <hadi@cyberus.ca> writes:

[...]
>> $TC qdisc add dev ppp0 root handle 1: prio
>> $TC filter add dev ppp0 parent 1:0 protocol ip prio 10 u32 \
>>     match u32 0 0 flowid 1:1 action mirred egress redirect dev dummy0
> Note: this will do for ipv4; if you want ipv6 add a new rule,
> in addition to above if you want ipv4, with "protocol ip" replaced by
> "protocol ipv6"

>> $TC qdisc add dev tun0 root handle 1: prio
>> $TC filter add dev tun0 parent 1:0 protocol ip prio 10 u32 \
>>     match u32 0 0 flowid 1:1 action mirred egress redirect dev dummy0
>> $TC qdisc add dev sit1 root handle 1: prio
>> $TC filter add dev sit1 parent 1:0 protocol ipv6 prio 10 u32 \
>>     match u32 0 0 flowid 1:1 action mirred egress redirect dev dummy0
> not sure if you need the above but i dont know your setup sufficiently
> to be 100%

using 'protocol ipv6' on ppp0 rather than sit1 did the trick.
It's even simplier ! I don't have to create filters for each ipv6 tunnel.

Considering the ipv4 over udp tun0 tunnel, i guess i should prevent
those udp packets to be matched by the filter on ppp0.
I'll optimize it later.

Cheers
                                                        
-- 

  reply	other threads:[~2004-04-21  1:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 14:22 IMQ / new Dummy device post syrius.ml
2004-04-20  2:15 ` jamal
2004-04-21  1:43   ` syrius.ml [this message]
2004-04-21 12:49     ` syrius.ml
2004-04-21 20:19       ` syrius.ml
2004-04-22 13:16         ` jamal
2004-04-22 17:43           ` syrius.ml
2004-04-23 11:29             ` jamal
2004-04-24 14:14               ` tun device - bug or feature? WAS(Re: " jamal
2004-04-26  4:38                 ` David S. Miller
2004-04-26 19:31                 ` Max Krasnyansky
2004-04-27  2:22                   ` jamal
2004-05-08 11:55                   ` jamal
2004-05-10 17:18                     ` Max Krasnyansky
2004-06-05 13:24                       ` PATCH: " jamal
2004-06-05 21:42                         ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2004-04-15  9:42 Andy Furniss
2004-04-15 12:15 ` jamal
2004-04-15 19:35   ` Andy Furniss
2004-04-16  3:52     ` jamal
2004-04-16 19:35       ` Andy Furniss
     [not found]         ` <1082145341.1026.125.camel@jzny.localdomain>
2004-04-17 10:39           ` Andy Furniss
2004-04-17 12:09             ` jamal
2004-04-17 21:56               ` Andy Furniss
2004-04-18 14:28                 ` jamal
2004-04-18 16:35                   ` Andy Furniss
2004-04-18 20:34                     ` Andy Furniss
2004-04-18 21:07                       ` jamal
2004-04-18 21:31                         ` Andy Furniss
2004-04-18 21:45                           ` Andy Furniss
2004-04-18 20:53                     ` jamal
2004-04-18 21:23                       ` Martin Josefsson
2004-04-18 21:58                         ` Andy Furniss
2004-04-19  8:14                           ` Martin Josefsson
2004-04-19 12:33               ` syrius.ml

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=wazza.87fzayw1fy.fsf@message.id \
    --to=syrius.ml@no-log.org \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).