All of lore.kernel.org
 help / color / mirror / Atom feed
From: Morgon.J.Kanter@Dartmouth.edu
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: PROBLEM: raw sockets rewriting IP ID in rare cases.
Date: Sun, 15 Aug 2010 20:43:50 -0400	[thread overview]
Message-ID: <20100815204350.4amjt1lngg0s0048@webmail.dartmouth.edu> (raw)
In-Reply-To: <1281905220.2942.57.camel@edumazet-laptop>

Quoting Eric Dumazet <eric.dumazet@gmail.com>:
> Le dimanche 15 août 2010 à 13:13 -0700, David Miller a écrit :
>> From: Morgon.J.Kanter@Dartmouth.edu
>> Date: Sun, 15 Aug 2010 13:57:41 -0400
>>
>> > Is there a way to turn this behavior off, then, with raw sockets? Zero
>> > is the desired ID value.
>>
>> No, there isn't.
>
> Just a note about IP_DF (Dont Fragment) bit.
>
> If set, ID stay 0.
>
> Not sure it can help Morgon.
>
> Jiri Olsa added IP_NODEFRAG option some weeks ago (commit 7b2ff18e),
> we probably could implement IP_NOIDENT option for RAW sockets ?

Thanks for the information. I was thinking of adding it in as a socket  
option as well, similar to that one you pointed out -- but seeing that  
makes me wonder, perhaps an "as-is" option would be more appropriate,  
instead of a different option for each field you want to leave as-is?

Thanks,
-- Morgon

  reply	other threads:[~2010-08-16  0:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 17:07 PROBLEM: raw sockets rewriting IP ID in rare cases Morgon J. Kanter
2010-08-15  5:35 ` David Miller
2010-08-15 17:57   ` Morgon.J.Kanter
2010-08-15 20:13     ` David Miller
2010-08-15 20:47       ` Eric Dumazet
2010-08-16  0:43         ` Morgon.J.Kanter [this message]
2010-08-16  6:26         ` Eric Dumazet
2010-08-16  6:50           ` Jiri Olsa

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=20100815204350.4amjt1lngg0s0048@webmail.dartmouth.edu \
    --to=morgon.j.kanter@dartmouth.edu \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@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 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.