From: Valdis.Kletnieks@vt.edu
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>,
Netfilter Developer Mailing List
<netfilter-devel@lists.netfilter.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] xt_u32 - match arbitrary bits and bytes of a packet
Date: Sun, 03 Jun 2007 01:07:27 -0400 [thread overview]
Message-ID: <18087.1180847247@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 02 Jun 2007 23:46:46 +0200." <Pine.LNX.4.61.0706022322340.28357@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On Sat, 02 Jun 2007 23:46:46 +0200, Jan Engelhardt said:
> along comes xt_u32, a revamped ipt_u32,
+1 for doing this - I've been dragging along a local ipt_u32 patch for a while,
and been wishing it had ipv6 support.
> * Reduced the buffer size to 17 KB. I think that is quite ok since
> I added an overflow check, SHOULD THERE BE ANY device with an
> MTU larger than our loopback masterpiece (16436 bytes).
>
> Are there such devices that support Megasuperjumboframes?
IP over Infiniband? I think those have some outrageous MTU? Personally,
I wouldn't need it for anything bigger than 9K ethernet jumbograms, but
that one's a decision for others.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-06-03 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 21:46 Jan Engelhardt
2007-06-02 21:50 ` [PATCH 1/2] xt_u32 (kernel) " Jan Engelhardt
2007-06-02 21:51 ` [PATCH 2/2] xt_u32 (iptables) " Jan Engelhardt
2007-06-03 5:07 ` Valdis.Kletnieks [this message]
2007-06-03 8:20 ` [PATCH 0/2] xt_u32 " Jan Engelhardt
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=18087.1180847247@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®