All of lore.kernel.org
 help / color / mirror / Atom feed
From: <bmcdowell@coxhealthplans.com>
To: netfilter@lists.netfilter.org
Subject: RE: TTL patch buggy?
Date: Thu, 8 Jan 2004 08:32:10 -0600	[thread overview]
Message-ID: <7A3B4AA360FDEF448F3390421FC8D731014BDF86@coxhpexg.coxhp.com> (raw)

Cedric wrote:
>If you want to prevent discovery based on the TTL of packets you send,
>reset TTL for outbound traffic to a default value such as 64.

I agree.  This is most useful for making it a tad more difficult to detect which OS you've chosen.

Also, incrementing the TTL is useful for obscuring NAT, as mentioned earlier.  This is helpful for HoneyPots where a single box/service is covering more than one IP/port.

For the interested, I can submit my own setup as an example.


Bob


             reply	other threads:[~2004-01-08 14:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 14:32 bmcdowell [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2004-01-07 19:31       ` Harald Welte
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=7A3B4AA360FDEF448F3390421FC8D731014BDF86@coxhpexg.coxhp.com \
    --to=bmcdowell@coxhealthplans.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.