* packets rejected as invalid, why?
@ 2013-12-02 13:43 Olaf Zaplinski
2013-12-02 21:29 ` Pascal Hambourg
0 siblings, 1 reply; 2+ messages in thread
From: Olaf Zaplinski @ 2013-12-02 13:43 UTC (permalink / raw)
To: netfilter
Hello all,
since Dec. 1st I see 60 rejected packets from well known and "good"
SMTP hosts:
Dec 2 12:12:02 binky kernel: [873572.327219] iptables-INVALID IN=eth0
OUT= MAC=00:f1:70:00:58:f0:fc:fb:fb:2d:55:48:08:00 SRC=213.165.67.104
DST=109.75.188.214 LEN=40 TOS=0x00 PREC=0x00 TTL=58 ID=0 DF PROTO=TCP
SPT=25 DPT=37022 SEQ=3171195917 ACK=0 WINDOW=0 RES=0x00 RST URGP=0
Why are these logged and rejected?
The rules:
$IPTABLES -A INPUT -m conntrack --ctstate INVALID -m limit \
--limit 3/s -j LOG --log-prefix="iptables-INVALID " \
--log-tcp-sequence --log-tcp-options
$IPTABLES -A INPUT -m conntrack --ctstate INVALID -j DROP
I think this packet was part of the TCP closing handshake, so it should
have been ESTABLISHED and not INVALID. Am I wrong?
Olaf
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: packets rejected as invalid, why?
2013-12-02 13:43 packets rejected as invalid, why? Olaf Zaplinski
@ 2013-12-02 21:29 ` Pascal Hambourg
0 siblings, 0 replies; 2+ messages in thread
From: Pascal Hambourg @ 2013-12-02 21:29 UTC (permalink / raw)
To: netfilter
Hello,
Olaf Zaplinski a écrit :
>
> since Dec. 1st I see 60 rejected packets from well known and "good"
> SMTP hosts:
>
> Dec 2 12:12:02 binky kernel: [873572.327219] iptables-INVALID IN=eth0
> OUT= MAC=00:f1:70:00:58:f0:fc:fb:fb:2d:55:48:08:00 SRC=213.165.67.104
> DST=109.75.188.214 LEN=40 TOS=0x00 PREC=0x00 TTL=58 ID=0 DF PROTO=TCP
> SPT=25 DPT=37022 SEQ=3171195917 ACK=0 WINDOW=0 RES=0x00 RST URGP=0
>
> Why are these logged and rejected?
Because your rules below say so.
> The rules:
>
> $IPTABLES -A INPUT -m conntrack --ctstate INVALID -m limit \
> --limit 3/s -j LOG --log-prefix="iptables-INVALID " \
> --log-tcp-sequence --log-tcp-options
>
> $IPTABLES -A INPUT -m conntrack --ctstate INVALID -j DROP
>
> I think this packet was part of the TCP closing handshake, so it should
> have been ESTABLISHED and not INVALID. Am I wrong?
RST is not part of the normal TCP closing handshake (FIN+ACK, FIN+ACK,
ACK). My guess is that this packet is related to an old connection which
is considered already closed by conntrack.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-12-02 21:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-02 13:43 packets rejected as invalid, why? Olaf Zaplinski
2013-12-02 21:29 ` Pascal Hambourg
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.