Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: Antony Stone <Antony@Soft-Solutions.co.uk>,
	netfilter ML <netfilter@lists.samba.org>
Subject: Re: ethernet headers and iptables counters
Date: Tue, 11 Nov 2003 10:37:40 -0300	[thread overview]
Message-ID: <003f01c3a858$fbf212c0$8effa8c0@ESTACAO> (raw)
In-Reply-To: 200311102321.hAANLsj17218@agate.rockstone.co.uk

>
> It does occur to me to wonder whether the ISP counts IP headers, but I
really
> would expect them to do so, and even so, an IP header is only 24 bytes,
with
> up to 1452 bytes of data inside the packet (assuming an MTU of 1500).
For
> 24 bytes to make 12% difference your data would be only 200 bytes on
average,
> and this is far too low to be plausible.

    Your affirmation 'IP header is only 24 bytes' is wrong. IP header has,
at least, 20 bytes and can have up to 60 bytes if you use IP Options. But,
in almost all cases, you'll have IP with no options, which means 20 bytes
for the IP headers. It can have 24 bytes in some cases, no doubt, but it's
not right that is always will have 24 and only 24 bytes.

    There also Transport Layer (4) headers. Using TCP, for example, you'll
have at least 20 bytes on the TCP headers, being able to reach 64 bytes if
all TCP options are enabled.

    This small error cannot explain the 12% difference ....... but we should
notice it :)


    Sincerily,
    Leonardo Rodrigues



      parent reply	other threads:[~2003-11-11 13:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10  9:14 ethernet headers and iptables counters Marc Lucke
2003-11-10  9:40 ` Antony Stone
2003-11-10 23:21   ` Antony Stone
2003-11-10 23:34     ` Simon Kitching
2003-11-10 23:45       ` Antony Stone
2003-11-11 13:37     ` Leonardo Rodrigues Magalhães [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='003f01c3a858$fbf212c0$8effa8c0@ESTACAO' \
    --to=leolistas@solutti.com.br \
    --cc=Antony@Soft-Solutions.co.uk \
    --cc=netfilter@lists.samba.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