From: Timo Benk <timo.benk@gmx.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: Traffic Shaping: Ingress qdisc not working in Dom0 - solved (3.0.4-1)
Date: Sun, 04 Feb 2007 20:34:28 +0100 [thread overview]
Message-ID: <45C63544.8040700@gmx.de> (raw)
In-Reply-To: <C1EBA3E4.8D82%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 4/2/07 13:32, "Timo Benk" <timo.benk@gmx.de> wrote:
>
>> The ingress qdisc on peth0 gets no traffic somehow.
>>
>> If i stop the bridge via 'network-bridge stop', the ingress qdisc
>> works as expected. But as far as the bridge is created, the
>> ingress qdisc stops working on peth0.
>
> My guess would be that this is unlikely to be a Xen-specific issue, and that
> something has changed in packet delivery that causes packets picked up by a
> bridge to not be checked for ingress filtering. This is fairly plausible
> because bridged packets are stolen from the normal packet-reception path
> quite early on, and it's very believable that changes in that area of the
> code wouldn't have been tested for tc/etherbridge interactions. I've cc'ed
> Herbert Xu just in case he has any ideas, since he's often aware of goings
> on in the Linux networking code.
I found the reason :-)
there was some problem rebuilding the kernel. After i have done a 'make clean'
in the xen-kernel directory and rebuilt the whole kernel, the ingress qdisc is
working like before again.
Greetings,
-timo
--
Timo Benk - Jabber ID: fry@downtempo.de - ICQ ID: #414944731
PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc
prev parent reply other threads:[~2007-02-04 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 13:32 Traffic Shaping: Ingress qdisc not working in Dom0 (3.0.4-1) Timo Benk
2007-02-04 14:53 ` Keir Fraser
2007-02-04 19:34 ` Timo Benk [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=45C63544.8040700@gmx.de \
--to=timo.benk@gmx.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=herbert@gondor.apana.org.au \
--cc=xen-devel@lists.xensource.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 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.