From: "Patrik Karén" <patrik.karen@home.se>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Dropped fin acks (iptables + lvs)
Date: Thu, 25 Jan 2007 22:30:14 +0100 [thread overview]
Message-ID: <45B92166.4000400@home.se> (raw)
In-Reply-To: <Pine.LNX.4.61.0701242315170.32656@yvahk01.tjqt.qr>
Jan Engelhardt skrev:
>> I am running iptables and lvs on two boxes loadbalancing http[s] and ssh traffic to two real servers.
>> Everything is working just fine from the users point of view. However,
>> I keep seeing a lot of dropped packets of type ack/fin and ack/rst in
>> my iptables log. Seems like the connection tracking isn't working the
>> way I expect it to. The iptables config in short is:
>>
>
> RST-ACK is received as a response to SYN to a closed port, and hence, is
> not part of a connection.
>
>
>> #This is the rule that should allow established connections, right?
>> $IPTABLES -A Firewall-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
>>
>
>
>> Jan 24 16:46:11 10.0.1.107 kernel: drop: IN=eth0 OUT=
>> MAC=00:15:c5:ee:48:a7:00:04:de:18:18:00:08:00 SRC=<CLIENTIP>
>> DST=<$VIP1_e> LEN=52 TOS=0x00 PREC=0x00 TTL=49 ID=28407 PROTO=TCP
>> SPT=48404 DPT=443 WINDOW=65535 RES=0x00 ACK FIN URGP=0
>>
>
> The FIN-ACK case however looks worth looking into. I'd say do it without
> -m limit and see if _every_ connection ends up that way. Also use
> tcpdump to match sessions.
>
>
> -`J'
>
Yes, the FIN-ACKs are the ones that bother me. There are lots of them,
but I don't know if they occur for every single tcp session.
I'm going to do some tcpdumping tomorrow on different interfaces to see
if I can find a pattern.
//Patrik
next prev parent reply other threads:[~2007-01-25 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 16:05 Dropped fin acks (iptables + lvs) Patrik Karén
2007-01-24 22:17 ` Jan Engelhardt
2007-01-25 21:30 ` Patrik Karén [this message]
2007-01-27 16:19 ` Pascal Hambourg
-- strict thread matches above, loose matches on Subject: below --
2007-03-14 13:57 Klaas Jan Wierenga
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=45B92166.4000400@home.se \
--to=patrik.karen@home.se \
--cc=jengelh@linux01.gwdg.de \
--cc=netfilter@lists.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