From: "Daniel" <daniel-gson@telia.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Confusion about MTU
Date: Sat, 14 Dec 2002 15:21:58 +0000 [thread overview]
Message-ID: <marc-lartc-103987942806488@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103980574728979@msgid-missing>
Ok, I found it out by myself, it is 1514b.
I set up two length matches in the PREROUTING chain in the mangle table, one
set to match on packets >\x1500b and one >\x1501b. The latter rule never
matched so I thought that the max packet really was 1500b. However I then
decided to put all packets matching the first rule in a separate class.
From there the answer was obvious, I simply divided the byte-count with the
packet-count and voila, I got 1514. So I guess the length match doesn't
count for the 14b's of ethernet encap.
This led me to change another thing in my setup, I no longer match small TCP
packets by matching them by <db but rather <Pb.
Well... this prolly seem real newbie like to most of you but hey we all are
at first.
// Daniel
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-14 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 18:54 [LARTC] Confusion about MTU Daniel
2002-12-14 15:21 ` Daniel [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=marc-lartc-103987942806488@msgid-missing \
--to=daniel-gson@telia.com \
--cc=lartc@vger.kernel.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.