From: Ron Peterson <rpeterso@mtholyoke.edu>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: network/performance problem
Date: Sun, 14 Mar 2004 13:13:50 -0500 [thread overview]
Message-ID: <20040314181350.GB28180@mtholyoke.edu> (raw)
In-Reply-To: <20040314093358.26147c5f.davem@redhat.com>
On Sun, Mar 14, 2004 at 09:33:58AM -0800, David S. Miller wrote:
> On Sun, 14 Mar 2004 08:23:40 -0500
> Ron Peterson <rpeterso@mtholyoke.edu> wrote:
>
> > Don't think so. If I revert to 2.4.20 from 2.4.21, and change nothing
> > else, this problem goes away.
>
> That's right because a netfilter change during that time period
> makes certain auto-rule adding setups go berzerk and it's a bug
> in the netfilter userland bits not the kernel.
I may indeed be completely dense. That's not unheard of around these
parts. I'd certainly accept an explanation of my denseness in lieue of
any other explanation, as long as I can make this stop happening.
What is the nature of the auto-rule adding setups going berzerk problem?
Below are my current iptables rules on 'sam' (the only machine not
currently running 2.4.20). There are no jumps to user defined chains.
I have not installed any scripts that dynamically add/alter iptables
rules. I can't imagine what package I may have installed that might do
such a thing either. Even if there were such a script somehow, since
nothing below ever jumps anywhere else, it wouldn't be getting called,
right?
If I flush and expunge my rules as follows, the problem goes away. If
this was because a jump to user defined chain was being deleted, then I'd
understand. But there are no jumps out of INPUT, OUTPUT, FORWARD,
PREROUTING, or POSTROUTING, so I'm confused.
$IPTABLES -F
$IPTABLES -t nat -F
$IPTABLES -X
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -P FORWARD ACCEPT
FWIW, I compiled the latest 'iptables' code against my current running
2.4.21 kernel also..
1052# iptables -V
iptables v1.2.9
1045# iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT icmp -- 138.110.0.0/16 anywhere icmp echo-request
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
ACCEPT tcp -- anywhere anywhere tcp dpt:https
ACCEPT all -- anywhere localhost
Chain FORWARD (policy DROP)
target prot opt source destination
Chain OUTPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere state NEW,RELATED,ESTABLISHED
Sun Mar 14 12:57:25 root@sam /usr/src
1046# iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
--
Ron Peterson
Network & Systems Manager
Mount Holyoke College
http://www.mtholyoke.edu/~rpeterso
prev parent reply other threads:[~2004-03-14 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 15:27 Ron Peterson
2004-03-11 17:32 ` Ron Peterson
2004-03-11 23:15 ` Andrew Morton
2004-03-11 23:35 ` Ron Peterson
2004-03-12 10:11 ` Patrick McHardy
2004-03-12 16:10 ` Martin Josefsson
2004-03-12 16:47 ` Ron Peterson
2004-03-12 17:23 ` Ron Peterson
2004-03-12 22:56 ` Ron Peterson
2004-03-14 6:33 ` David S. Miller
2004-03-14 13:23 ` Ron Peterson
2004-03-14 17:33 ` David S. Miller
2004-03-14 18:13 ` Ron Peterson [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=20040314181350.GB28180@mtholyoke.edu \
--to=rpeterso@mtholyoke.edu \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®