From: Bernhard Bock <mailinglists@bock.nu>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter@vger.kernel.org
Subject: Re: conntrackd failover works partially, was Re: conntrack performance test results in INVALID packets
Date: Tue, 02 Sep 2008 14:34:20 +0200 [thread overview]
Message-ID: <48BD32CC.5010203@bock.nu> (raw)
In-Reply-To: <48BD0DD6.9000803@netfilter.org>
Hi Pablo,
Pablo Neira Ayuso wrote:
> That's exactly the test that I do in my testbed and it works fine here,
> the problem must be elsewhere. The following line should help to see how
> the connection tracking is marking the traffic as invalid:
>
> echo 255 > /proc/sys/net/ipv4/netfilter/ip_conntrack_log_invalid
>
> However, please see the comment below before doing this and repeating
> the test.
I didn't know one can increase the verbosity. Now I get some (more)
helpful logs.
kernel: nf_ct_tcp: invalid packet ignored IN= OUT= SRC=10.5.0.101
DST=10.6.6.102 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=9977 DF PROTO=TCP
SPT=39101 DPT=80 SEQ=3381624888 ACK=0 WINDOW=5840 RES=0x00 SYN URGP=0 OPT
Invalid syn packet? Hm. And then:
kernel: nf_ct_tcp: killing out of sync session IN= OUT= SRC=10.6.6.102
DST=10.5.0.101 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80
DPT=41647 SEQ=3243074286 ACK=3280173284 WINDOW=5792 RES=0x00 ACK SYN
URGP=0 OPT
> Are you using a sane stateful rule-set similar to the described in the
> conntrack-tools website? What kernel version are you using? If your
> kernel is < 2.6.22 you have to disabled TCP window tracking on both nodes.
>
> echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal
I'm using 2.6.25, from Fedora 9.
And I have set /proc/sys/net/netfilter/nf_conntrack_tcp_be_liberal to 1.
Here are my rules:
-A FORWARD -m state --state INVALID -j LOG --log-prefix "Invalid:"
-A FORWARD -m state --state INVALID -j DROP
-A FORWARD -p tcp ! --syn -m state --state NEW -j LOG --log-prefix "New
not syn:"
-A FORWARD -p tcp ! --syn -m state --state NEW -j DROP
-A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -m state --state NEW -m tcp -p tcp --syn -d 10.6.6.0/24 -j ACCEPT
-A FORWARD -m state --state NEW -m udp -p udp -s 10.5.0.0/24 -d
10.6.6.0/24 -j ACCEPT
-A FORWARD -j LOG --log-prefix "Packet dropped:"
-A FORWARD -j DROP
> There is a new script `primary-backup.sh' that replaces the old
> script_master.sh and script_backup.sh. Although this is not directly
> related it would be worth to use that instead as it will be the standard
> in the upcoming release.
I'll replace it for future tests. For now, I don't want to mess around
at too many places at the same time unless it's related to the problem.
best regards
Bernhard
next prev parent reply other threads:[~2008-09-02 12:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 9:39 conntrack performance test results in INVALID packets Bernhard Bock
2008-07-18 10:13 ` Jan Engelhardt
2008-07-18 10:52 ` Bernhard Bock
2008-07-18 12:14 ` Pablo Neira Ayuso
2008-07-18 14:20 ` conntrackd failover works partially, was " Bernhard Bock
2008-07-21 0:37 ` Pablo Neira Ayuso
2008-07-21 14:22 ` conntrackd failover works partially Bernhard Bock
2008-07-23 8:51 ` Bernhard Bock
2008-07-23 12:50 ` Pablo Neira Ayuso
2008-07-23 15:20 ` Bernhard Bock
2008-08-08 8:47 ` conntrackd failover works partially, was Re: conntrack performance test results in INVALID packets Pablo Neira Ayuso
2008-08-08 12:58 ` Bernhard Bock
2008-09-02 9:39 ` Bernhard Bock
2008-09-02 9:56 ` Pablo Neira Ayuso
2008-09-02 12:34 ` Bernhard Bock [this message]
2008-09-02 12:48 ` Pablo Neira Ayuso
2008-09-02 15:18 ` Bernhard Bock
2008-09-02 16:22 ` Pablo Neira Ayuso
2008-09-02 16:55 ` Bernhard Bock
2008-09-03 9:13 ` Pablo Neira Ayuso
2008-09-03 11:26 ` Bernhard Bock
2008-09-04 12:29 ` Pablo Neira Ayuso
2008-09-04 13:27 ` Bernhard Bock
2008-09-05 10:55 ` Pablo Neira Ayuso
2008-09-04 11:40 ` Pablo Neira Ayuso
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=48BD32CC.5010203@bock.nu \
--to=mailinglists@bock.nu \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.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