From: Matt Ayres <matta@tektonic.net>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Hard lock of server - saved history from serial consolewithin
Date: Wed, 19 Apr 2006 19:26:00 -0400 [thread overview]
Message-ID: <4446C708.4070802@tektonic.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA377@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> Yes, an iptable rule for each IP for bandwidth accounting.
>> Also 4 rules in the raw table and 4 rules in the nat table
>> for port redirection. I don't see how the actual iptables
>> rules could effect the kernel though.
>
> (!) iptables causes big changes to the way packets pass through the
> kernel.
>
> In particular, it sounds like you may be using connection tracking for
> NAT. There were lots of changes in this area for 2.6.16, one of which
> broke bridging for large UDP and ICMP datagrams.
>
> Seeing what iptables modules you have loaded may be interesting. It
> doesn't look much like a xen issue, but I wouldn't totally rule it out.
Most all are compiled in. I do use connection tracking. I doubt it is a
Xen problem anymore. I am upgrading all kernels to 2.6.16.9 to see if
that fixes it. If not I'll have to try 2.6.17-rcX (whatever is the
latest). I tried applying it and got many rejects so I don't know how
advanced of a kernel hacker I'd have to be to get that working.
Thanks,
Matt
next prev parent reply other threads:[~2006-04-19 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 23:12 Hard lock of server - saved history from serial consolewithin Ian Pratt
2006-04-19 23:26 ` Matt Ayres [this message]
2006-04-22 1:29 ` Christian Limpach
-- strict thread matches above, loose matches on Subject: below --
2006-04-19 23:14 Ian Pratt
2006-04-19 22:29 Ian Pratt
2006-04-19 22:35 ` Matt Ayres
2006-04-19 22:41 ` Matt Ayres
2006-04-19 22:19 Ian Pratt
2006-04-19 22:24 ` Matt Ayres
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=4446C708.4070802@tektonic.net \
--to=matta@tektonic.net \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.