|
On Wed, 2007-08-08 at 15:47 +0200, Matthias Saou wrote:
> I don't know if I'll be able to figure out why. It does seem like a
> connection tracking problem somewhere on the Xen Host (dom0), or maybe
> the Xen guests (domU), but I doubt it.
Humo(u)r me. If the following isn't set to 0 already, try it:
echo 0 > /proc/sys/net/ipv4/tcp_sack
It's possible that you're hitting a bug which was fixed in 2.6.12... you
shouldn't have it in 2.6.18, but anything is possible. Especially
regressions.
For more details around this, see
https://lists.netfilter.org/pipermail/netfilter/2005-June/061101.html
and
http://linuxgazette.net/116/tag/6.html
Graeme
|
