Re: iptables in 2.4.10, 2.4.11pre6 problems

Darrell A Escola
2001-10-19T13:18:22Z

I have been running 2.4.10-ac11 for 7 days now with
TCP_CONNTRACK_CLOSE_WAIT set to 120 seconds - this has stopped nearly
all firewall activity on established connections.

I use "mc" extensively for ftp, and previously would get numerous blocks
after closing a session or starting another ftp session with the same
instance of "mc".

What would we need to do to make these values tuneable either via
insmod/modprobe or /proc?

Darrell

On Wed, Oct 10, 2001 at 01:55:03PM +1000, Rusty Russell wrote:

> On Tue, 9 Oct 2001 10:07:05 -0700 (PDT)
> "Jeffrey W. Baker" <jwbaker@acm.org> wrote:

> > On 9 Oct 2001, Trever L. Adams wrote:

> > > I am seeing messages such as:
> > > Oct 9 12:52:51 smeagol kernel: Firewall:IN=ppp0 OUT= MAC=
> > > SRC=64.152.2.36 DST=MY_IP_ADDRESS LEN=52 TOS=0x00 PREC=0x00 TTL=246
> > > ID=1093 DF PROTO=TCP SPT=80 DPT=33157 WINDOW=34752 RES=0x00 ACK FIN
> > > URGP=0
> > >
> > > In my firewall logs. I see them for ACK RST as well. These are valid
> > > connections. My rules follow for the most part (a few allowed
> > > connections to the machine in question have been removed from the
> > > list). This often leaves open connections in a half closed state on
> > > machines behind this firewall. It also some times kills totally open
> > > connections and I see packets rejected that should be allowed through.
> >
> > I see this too. iptables is refusing packets on locally-initiated TCP
> > connections when the RELATED,ESTABLISHED rule should be letting them
> > through.
>
> Yes, but it has forgotten them. Play with the TCP timeout numbers in
> net/ipv4/netfilter/ip_conntrack_proto_tcp.c. Especially the 60 seconds for
> TCP_CONNTRACK_CLOSE_WAIT for the ACK FIN case. These numbers were stolen
> from the 2.0 and 2.2 masq code, which had real world testing (but didn't
> report failures, so...)
>
> Given some actual feedback on appropriate numbers, this can be fed as a
> patch to Linus...
>
> Hope that helps,
> Rusty.