All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: TTL patch buggy?
Date: Tue, 6 Jan 2004 19:56:13 +0100	[thread overview]
Message-ID: <20040106185613.GB934@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <1073055732.2995.4.camel@jasiiitosh.nexusmgmt.com>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

On Fri, Jan 02, 2004 at 10:02:13AM -0500, John A. Sullivan III wrote:
> I noticed a recent post on the netfilter list about the TTL patch
> being buggy.  

Could you please point me to that posting (either message-id or a URL
pointing to the archives?)

> We were planning to make extensive use of it in the ISCS
> project.  I've not seen anything recent about such a bug in a google
> search.  Is there currently a known problem with this patch? Thanks -

I (the author) am not aware of any current problem.

If there are bugs/problems, they should be submitted to
bugzilla.netfilter.org

> John

-- 
- 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 --]

  reply	other threads:[~2004-01-06 18:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 15:02 TTL patch buggy? John A. Sullivan III
2004-01-06 18:56 ` Harald Welte [this message]
2004-01-06 22:18   ` John A. Sullivan III
2004-01-07 16:16     ` Henrik Nordstrom
2004-01-07 19:04       ` John A. Sullivan III
2004-01-07 19:18         ` Antony Stone
2004-01-07 20:44           ` Ramin Dousti
2004-01-07 19:35         ` Harald Welte
2004-01-07 20:07           ` John A. Sullivan III
2004-01-07 21:38             ` Ramin Dousti
2004-01-08  8:02               ` Cedric Blancher
2004-01-08 16:25                 ` Ramin Dousti
2004-01-08 19:17                   ` Cedric Blancher
2004-01-07 21:19           ` Ramin Dousti
2004-01-07 20:54             ` Henrik Nordstrom
2004-01-07 20:54               ` Henrik Nordstrom
2004-01-07 22:16               ` Ramin Dousti
2004-01-08  7:14                 ` Henrik Nordstrom
2004-01-08  7:14                   ` Henrik Nordstrom
2004-01-08 20:56                   ` Ramin Dousti
2004-01-07 20:36         ` Ramin Dousti
2004-01-07 19:31       ` Harald Welte
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:32 bmcdowell
2004-01-02 13:13 John A. Sullivan III
2004-01-02 14:27 ` Antony Stone

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=20040106185613.GB934@obroa-skai.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=john.sullivan@nexusmgmt.com \
    --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.