lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 21 Jul 2009 11:52:28 +0300 (EEST)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	Raphael Hertzog <raphael@...za.com>
cc:	Netdev <netdev@...r.kernel.org>
Subject: Re: Constantly varying download rate with a complex xen networking
 setup, why?

On Wed, 17 Jun 2009, Raphael Hertzog wrote:

> Le mercredi 17 juin 2009, Ilpo Järvinen a écrit :
>> On Wed, 17 Jun 2009, Raphael Hertzog wrote:
>>
>>> Le lundi 15 juin 2009, Ilpo Järvinen a écrit :
>>>> Maybe the proxy interferes there somehow... I don't know enough about the
>>>> details to say but I suppose the proxy at least breaks your tcp connection
>>>> to two parts.
>>>
>>> Indeed. Is there some processing done in a simple linux bridge where the
>>> reapperance of the same TCP packet that has been created and sent on another
>>> local interface could create problem?
>>
>> I thought out had a http proxy in between? I suppose it is certainly doing
>> more than bridging. Anyway, I'll be week away, so no quick responses are
>> to be expected from my part after this mail.
>
> Well, I have the problem when I don't use the proxy... if I use it, the
> download is split over two TCP connections and things are fine.
>
> Hence my question was if something could be confused by the fact that the
> same packet is seen twice on the same machine once (in output) via 
> eth2/xenbrD and once (in forward) via xenbrE (the routing between both 
> bridges is done by the domU independently of the dom0 network config).

Did you ever get tcpdumps btw? Looking into your setup it would probably 
be useful take it from all the interfaces where the packets are supposed 
to pass.


-- 
  i.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ