From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Connection problems on large high speed connections.
Date: Thu, 28 Apr 2005 17:24:13 -0400 [thread overview]
Message-ID: <20050428212413.GA31194@bender.817west.com> (raw)
In-Reply-To: <1114719380.14301.4.camel@zepto.barmen.nu>
On Thu, Apr 28, 2005 at 10:16:20PM +0200, Stian B. Barmen wrote:
> Just to satisfy my couriosity, I logged in ulog the invalig packets, and
> there are quite a few. How many should I expect to see and count as
> normal?
>
> For instance I downloaded a file from a reasonably fast FTP server at
> about 7 MB, and during I logged three invalid TCP packets.
>
> Apr 28 22:07:25 fire Invalid: IN=eth1 OUT=
> MAC=00:d0:b7:1d:cc:7d:00:90:69:f0:b0:20:08:00 SRC=156.56.247.195
> DST=217.199.xx.18 LEN=1500 TOS=00 PREC=0x00 TTL=53 ID=47468 CE DF
> PROTO=TCP SPT=80 DPT=33553 SEQ=985943197 ACK=497088462 WINDOW=6432 ACK
> URGP=0
> Apr 28 22:07:43 fire Invalid: IN=eth1 OUT=
> MAC=00:d0:b7:1d:cc:7d:00:90:69:f0:b0:20:08:00 SRC=156.56.247.195
> DST=217.199.xx.18 LEN=1500 TOS=00 PREC=0x00 TTL=53 ID=52274 CE DF
> PROTO=TCP SPT=80 DPT=33553 SEQ=989439897 ACK=497088462 WINDOW=6432 ACK
> URGP=0
> Apr 28 22:07:47 fire Invalid: IN=eth1 OUT=
> MAC=00:d0:b7:1d:cc:7d:00:90:69:f0:b0:20:08:00 SRC=156.56.247.195
> DST=217.199.xx.18 LEN=1500 TOS=00 PREC=0x00 TTL=53 ID=53186 CE DF
> PROTO=TCP SPT=80 DPT=33553 SEQ=990104197 ACK=497088462 WINDOW=6432 ACK
> URGP=0
the only thing that jumps out at me is that all those packets have the
CE bit set (Congestion Experienced). care to share with us the rule
that creates those log entries? is it just "-m state --state INVALID -j
LOG"? i would be very surprised if setting CE caused a packet to
identified as INVALID...
-j
--
"Stewie: I'll wait until you're finished. Are you done? Because
I thought this show was called "Kids Say the Darndest Things," not
"Old Black Comedians Who Never Shut The Hell Up.""
--Family Guy
next prev parent reply other threads:[~2005-04-28 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 22:50 Connection problems on large high speed connections Stian B. Barmen
2005-04-27 5:03 ` Taylor, Grant
2005-04-27 6:46 ` Stian B. Barmen
2005-04-27 7:00 ` Jozsef Kadlecsik
2005-04-27 7:10 ` Stian B. Barmen
2005-04-27 7:20 ` Stian B. Barmen
2005-04-27 9:44 ` Stian B. Barmen
2005-04-27 13:36 ` Stian B. Barmen
2005-04-27 13:47 ` Jozsef Kadlecsik
2005-04-27 13:51 ` Stian B. Barmen
2005-04-27 13:58 ` Jozsef Kadlecsik
2005-04-27 14:25 ` Stian B. Barmen
2005-04-28 20:16 ` Stian B. Barmen
2005-04-28 21:24 ` Jason Opperisano [this message]
2005-04-28 22:56 ` Stian B. Barmen
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=20050428212413.GA31194@bender.817west.com \
--to=opie@817west.com \
--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 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.