From: Harald Welte <laforge@netfilter.org>
To: Kostadin Karaivanov <larry@tamiweb.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: forward port of TTL.patch to 2.6.0-test9
Date: Fri, 7 Nov 2003 17:50:12 +0100 [thread overview]
Message-ID: <20031107165012.GV5741@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <3FA7CD65.6000804@tamiweb.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Tue, Nov 04, 2003 at 06:01:41PM +0200, Kostadin Karaivanov wrote:
> Hi list,
> I just forward ported TTL.patch (attached) from patch-o-matic-20031103
> to linux-2.6.0-test9 for fun and profit. It's rather mechanical port but
> it works at least build-in. I've veryfied this with tcpdump.
> But I have two questions. First of course is: is this the proper way to
> port things like this, couse AFAIC 2.4 and 2.5 networking code is quite
> different, if not why.
no, I don't see a problem with this 2.6 merge. However, we still don't
have a 2.6-ready patch-o-matic (I'm working on it), so I cannot really
integrate it somewhere.
> And second - where I can read about current > implementation ot linux
> networking excetp kernel sources.
I doubt there is any information apart from the netdev and linux-kernel
mailinglist archives.
> wwell Larry.
>
> P.S please cc me, I'm not subscribet to the list.
--
- 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: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-07 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 16:01 forward port of TTL.patch to 2.6.0-test9 Kostadin Karaivanov
2003-11-07 16:50 ` 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=20031107165012.GV5741@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=larry@tamiweb.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.