From: Patrick McHardy <kaber@trash.net>
To: Konsar <konsar@brod.pl>
Cc: netfilter-devel@lists.netfilter.org,
netfilter-devel-owner@lists.netfilter.org,
linux-kernel@vger.kernel.org,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
"David S. Miller" <davem@davemloft.net>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: ip_conntrack_tcp problem on kernel 2.4.28 !!! INVALID ?
Date: Sat, 25 Dec 2004 15:11:10 +0100 [thread overview]
Message-ID: <41CD74FE.3090202@trash.net> (raw)
In-Reply-To: <opsjkf9pg8or678w@localhost>
Konsar wrote:
> Hi !!!
>
> I have patches kernel 2.4.28 + patch-o-matic-ng-20040621 with
> iptables-1.2.11 on my router/NAT server.This islog from my server
>
> [...]
>
> Dec 25 14:15:47 gizmo kernel: ip_conntrack_tcp: INVALID: invalid RST
> (ignored) SRC=64.230.127.202 DST=22.22.22.22 LEN=40 TOS
> =0x00 PREC=0x00 TTL=111 ID=25587 PROTO=TCP SPT=46885 DPT=1804 SEQ=0
> ACK=881916807 WINDOW=0 RES=0x00 ACK RST URGP=0
> janek.log lines 17-47/47 (END)
>
> What is this and how close this log ? Where is problem ?
The problem is edonkey, you get all kinds of crap if you run
it or catch the IP of someone who did. Its about the biggest
sin for a network I've ever seen. The only funny part about
it are the crappy implementations, you just have to smile if
you see people do GUI refreshing in the UDP packet handler :)
Regards
Patrick
BTW: No need to CC tons of people for questions like these.
prev parent reply other threads:[~2004-12-25 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 13:40 ip_conntrack_tcp problem on kernel 2.4.28 !!! INVALID ? Konsar
2004-12-25 14:11 ` Patrick McHardy [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=41CD74FE.3090202@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=konsar@brod.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel-owner@lists.netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
/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