From: "Leonardo Rodrigues Magalhaes" <leolistas@solucoesip.net>
To: netfilter ML <netfilter@lists.samba.org>
Subject: Re: question on ip_conntrack log entries and behavior
Date: Fri, 21 Mar 2003 08:32:36 -0300 [thread overview]
Message-ID: <002201c2ef9d$932eb190$3201a8c0@ESTACAO> (raw)
In-Reply-To: Pine.LNX.4.33.0303201500280.17210-100000@blackhole.kfki.hu
OK ......... i downloaded latest patch-o-matic snapshot, get a new
kernel 2.4.20 source tree and tried to aplly the needed patchs. But, I got a
problem here ....
Seems I need submitted/10_confirm_fix.patch to fix the CLOSE stuff .....
but I also need tcp-window-tracking.patch for allowing deal with conntrack
timeouts in kernel runtime. But both patchs seems to change the SAME line in
two files. So, I cannot apply the two. I can only apply one of them ( any
one ) and it will apply correctly. The other will always fail.
Problem seems to be:
hunk from submitted/10_confirm_fix.patch
--- linux-2.4.20-base/net/ipv4/netfilter/ip_conntrack_proto_tcp.c Tue
Feb 18 17:07:26 2003
+++ linux-2.4.20-del/net/ipv4/netfilter/ip_conntrack_proto_tcp.c Fri
Feb 21 17:03:35 2003
@@ -192,7 +192,7 @@
have an established connection: this is a fairly common
problem case, so we can delete the conntrack
immediately. --RR */
- if (!(conntrack->status & IPS_SEEN_REPLY) && tcph->rst) {
+ if (!test_bit(IPS_SEEN_REPLY_BIT, &conntrack->status) && tcph->rst)
{
WRITE_UNLOCK(&tcp_lock);
if (del_timer(&conntrack->timeout))
conntrack->timeout.function((unsigned
long)conntrack);
in extra/tcp-window-tracking.patch file, I have, among several other
changes:
- if (!(conntrack->status & IPS_SEEN_REPLY) && tcph->rst) {
+ if (!(conntrack->status & IPS_SEEN_REPLY)) {
Question ...... and now, what should I do ?? :) It would be very
interesting to me having both patchs applied. Do the mainteners of these
patchs are subscribed to this list ? If yes, can you help me ?
Sincerily,
Leonardo Rodrigues
----- Original Message -----
From: "Jozsef Kadlecsik" <kadlec@blackhole.kfki.hu>
To: "Leonardo Rodrigues Magalhaes" <leolistas@solucoesip.net>
Cc: "netfilter ML" <netfilter@lists.samba.org>
Sent: Thursday, March 20, 2003 11:04 AM
Subject: Re: question on ip_conntrack log entries and behavior
On Thu, 20 Mar 2003, [iso-8859-1] Leonardo Rodrigues Magalhães wrote:
> I got a firewall running kernel 2.4.20 with some p-o-m patches,
> including tcp-window-tracking which allows me change timeout stuff in
> runtime.
>
> Well ...... my /proc/net/ip_conntrack log is PLENTY of CLOSE
> connections, just like:
This is a bug in 2.4.20. You need the submitted/10_confirm_fix.patch.help
patch from the most recent patch-o-matic.
Regards,
Jozsef
-
E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
H-1525 Budapest 114, POB. 49, Hungary
prev parent reply other threads:[~2003-03-21 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 13:22 question on ip_conntrack log entries and behavior Leonardo Rodrigues Magalhães
2003-03-20 14:04 ` Jozsef Kadlecsik
2003-03-21 11:32 ` Leonardo Rodrigues Magalhaes [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='002201c2ef9d$932eb190$3201a8c0@ESTACAO' \
--to=leolistas@solucoesip.net \
--cc=netfilter@lists.samba.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