All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
Cc: Henrik Nordstrom <hno@marasystems.com>,
	netfilter@lists.netfilter.org,
	Harald Welte <laforge@netfilter.org>,
	netfilter-devel@lists.netfilter.org
Subject: Re: TTL patch buggy?
Date: Wed, 7 Jan 2004 15:36:24 -0500	[thread overview]
Message-ID: <20040107203624.GA20346@cannon.eng.us.uu.net> (raw)
In-Reply-To: <1073502275.16972.10.camel@jasiiitosh.nexusmgmt.com>

On Wed, Jan 07, 2004 at 02:04:36PM -0500, John A. Sullivan III wrote:

> 
> Thank you very much but could you please explain this a bit more.

The whole TTL concept is meant to deal with the routing loops. Just
imagine what happens if there is a routing loop between your gateway
and the ISP's upstream router. The packets would be bouncing back and
forth forever (until your gateway is rebooted) and the throughput
of your bandwidth would drop to +-zerro.

Now if you anticipate no routing loop (which is extremely unlikely
in the current architecture of how the ISP's do business) you should
be fine. However, these routing loops could happen when people start
mixing the TTL-increments with MIRROR:

http://www.netfilter.org/security/2001-08-22-mirror.html

Ramin

  parent reply	other threads:[~2004-01-07 20:36 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
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 [this message]
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=20040107203624.GA20346@cannon.eng.us.uu.net \
    --to=ramin@cannon.eng.us.uu.net \
    --cc=hno@marasystems.com \
    --cc=john.sullivan@nexusmgmt.com \
    --cc=laforge@netfilter.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 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.