WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Traffic Shaping: Ingress qdisc not working in Dom0 - sol

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Traffic Shaping: Ingress qdisc not working in Dom0 - solved (3.0.4-1)
From: Timo Benk <timo.benk@xxxxxx>
Date: Sun, 04 Feb 2007 20:34:28 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 04 Feb 2007 11:34:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1EBA3E4.8D82%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=67E2E5E9; url=http://m28s01.vlinux.de/timo_benk_gpg_key.asc
References: <C1EBA3E4.8D82%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20061206)
Keir Fraser wrote:
> On 4/2/07 13:32, "Timo Benk" <timo.benk@xxxxxx> 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@xxxxxxxxxxxx - ICQ ID: #414944731
PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>