mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Alexandre Hautequest <hquest@fesppr.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: non-random IP IDs
Date: Thu, 25 Jan 2001 13:02:22 -0800 (PST)	[thread overview]
Message-ID: <14960.37982.739742.487042@pizda.ninka.net> (raw)
In-Reply-To: <980451650.3a7081428753c@webmail.fesppr.br>
In-Reply-To: <980451650.3a7081428753c@webmail.fesppr.br>


Alexandre Hautequest writes:
 > I was playing a bit on some of my machines with Nessus (www.nessus.org), and it
 > told me the following text:
 > 

Nessus is saying something bogus to you.

 > Is there some option to dinamically enable this random IP ID's, or I need to 
 > change something and recompile, or just "No way!"?

Ip IDs only matter when packets can be fragmented.  If the packet
cannot be fragmented, the Ip ID field serves no purpose.  Whatever the
nessus thing did to test this, it used a IP packet to/from the linux
box which had the "Don't Fragment" bit set in the IP header, which as
a consequence means the ID field is meaningless.

If the "don't fragment" bit were not set, and fragmentation was
possible, Linux will use a randomized ID field.  The nessus folks
need to fix their test.

Later,
David S. Miller
davem@redhat.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-25 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 19:40 Alexandre Hautequest
2001-01-25 21:02 ` David S. Miller [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=14960.37982.739742.487042@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=hquest@fesppr.br \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®