Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] action redirect and dummy interface
Date: Fri, 11 Nov 2005 14:05:27 +0000	[thread overview]
Message-ID: <4374A527.8040509@dsl.pipex.com> (raw)
In-Reply-To: <43740B06.5090104@artcom.pl>

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]

Paweł Staszewski wrote:
> Hello i have some problems on 2.6.14 kernel dummy and iproute :)
> 
> i have server with 2 nics :
> 
> eth0 <> inet
> eth1 <> lan
> 
> dummy0 (i want to shape incoming traffic from lan machine on this 
> interface)

OK but the script sends both egress and ingress on eth1 to dummy0.

> 
> my config:
> tc qdisc del dev dummy0 root
> 
> tc qdisc add dev dummy0 root handle 1: htb
> tc class add dev dummy0 parent 1: classid 1:1 htb rate 100kbit ceil 100kbit
> tc class add dev dummy0 parent 1: classid 1:2 htb rate 100kbit ceil 100kbit
> 
> 
> tc filter add dev dummy0 protocol ip pref 1 parent 1: handle 1 fw 
> classid 1:1
> tc filter add dev dummy0 protocol ip pref 2 parent 1: handle 2 fw 
> classid 1:2
> 
> ifconfig dummy0 up
> 
> 
> 
> tc qdisc del dev eth1 root
> tc qdisc add dev eth1 root handle 1: htb
> 
> tc filter add dev eth1 parent 1:0 protocol ip prio 10 u32 \
> match ip dst 0/0 flowid 1:1 \
> action ipt -j MARK --set-mark 2 \
> action mirred egress redirect dev dummy0
> 
> 
> 
> tc qdisc del dev eth1 ingress
> 
> tc qdisc add dev eth1 ingress
> 
> tc filter add dev eth1 parent ffff: protocol ip prio 10 u32 \
> match ip src 0/0 flowid 1:1 \
> action ipt -j MARK --set-mark 1 \
> action mirred egress redirect dev dummy0

Apart from adding a modprobe this works for me using the attached 
dummy.c on 2.6.12.


> 
> 
> and i have only tx-es on dummy0 interface no rx packets and lan machine 
> cannot comunicate with server and vice-versa
> 
> 
> any solutions ... i readed this post 
> http://oss.sgi.com/projects/netdev/archive/2004-04/msg00251.html
> and i have the same config ... but :)

That patch didn't go into kernel and was superseeded by another version 
which I attach - but AFAIK it's still not in kernel yet and jamal is 
still working on it.

Andy.

[-- Attachment #2: dummy.c.gz --]
[-- Type: application/x-gzip, Size: 2952 bytes --]

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-11-11 14:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11  3:07 [LARTC] action redirect and dummy interface Paweł Staszewski
2005-11-11  6:33 ` Paweł Staszewski
2005-11-11 12:58 ` Tomasz Paszkowski
2005-11-11 14:05 ` Andy Furniss [this message]
2005-11-11 14:44 ` Paweł Staszewski
2005-11-11 15:34 ` Andy Furniss
2005-11-11 20:01 ` Paweł Staszewski

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=4374A527.8040509@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox