From: Harald Welte <laforge@netfilter.org>
To: Andras Kis-Szabo <kisza@securityaudit.hu>
Cc: Maciej So?tysiak <maciej.soltysiak@ae.poznan.pl>,
netfilter-devel@lists.netfilter.org
Subject: Re: [POM PATCHES] IPv6 ports of time and quota matches
Date: Tue, 6 Jan 2004 19:54:40 +0100 [thread overview]
Message-ID: <20040106185440.GA934@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <20040105121244.GB16171@sch.bme.hu>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
On Mon, Jan 05, 2004 at 01:12:44PM +0100, Andras Kis-Szabo wrote:
> Maciej So??tysiak ............................................................................ (2003. december 23.)
>
> Hi,
>
> > I noticed I have two patchsets left behind, never included in patch-o-matic
> > These are IPv6 ports of the time and quota matches.
> Please, be careful w/ the 'plain ports'.
> Rusty has changed the internal structure of the IPv4 parts (acording the skb
> linearization) - and these changes are missing from the IPv6 part. In IPv6
> every packets are linearized - in IPv4 you have to linearize the required
> parts avery time and in some higher-level protocols tha helper functions have
> benn changed.
yes, for consistency reasons we should forward-port those changes from
ipv4 to ipv6. any volunteers?
> Regards,
> kisza
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-06 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 15:52 [POM PATCHES] IPv6 ports of time and quota matches Maciej Sołtysiak
2004-01-05 12:12 ` Andras Kis-Szabo
2004-01-06 18:54 ` Harald Welte [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=20040106185440.GA934@obroa-skai.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=kisza@securityaudit.hu \
--cc=maciej.soltysiak@ae.poznan.pl \
--cc=netfilter-devel@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.