public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Denenberg <adam@dberg.org>
To: Doug McNaught <doug@mcnaught.org>
Cc: linux-os@analogic.com, Jan Harkes <jaharkes@cs.cmu.edu>,
	Kyle Moffett <mrmacman_g4@mac.com>,
	linux-kernel@vger.kernel.org,
	Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: bind() udp behavior 2.6.8.1
Date: Wed, 15 Dec 2004 15:48:50 -0500	[thread overview]
Message-ID: <1103143730.6825.19.camel@sucka> (raw)
In-Reply-To: <87oegv5lz1.fsf@asmodeus.mcnaught.org>

but this would be an issue with glibc then correct?


On Wed, 2004-12-15 at 15:45, Doug McNaught wrote:
> Adam Denenberg <adam@dberg.org> writes:
> 
> > sorry for any confusion, but i am not referring to the Identification
> > field in the IP header but rather the "Transaction ID" field in the DNS
> > query portion of the packet.  I can reproduce this behavior on our linux
> > system where if i pump gethostbyname_r requests on the system at some
> > point it will reuse a transaction id in the DNS request.  This is my
> > lastest discovery in what is causing the requests to fail thru the
> > firewall.  So far my research has not turned up any reason as to why the
> > kernel would be re-using a transaction ID in the dns request.
> 
> That would be your DNS software reusing the transaction ID, since it's
> part of the packet data, not the UDP header.  The kernel has nothing
> to do with it.
> 
> -Doug
> 


  reply	other threads:[~2004-12-15 20:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 15:38 bind() udp behavior 2.6.8.1 Adam Denenberg
2004-12-14 16:04 ` Jan Engelhardt
2004-12-14 16:42   ` Adam Denenberg
2004-12-14 16:44     ` Jan Engelhardt
2004-12-14 17:01       ` Adam Denenberg
2004-12-14 17:10         ` Jan Engelhardt
2004-12-14 17:38           ` Adam Denenberg
2004-12-14 17:49             ` Jan Engelhardt
2004-12-15  0:43             ` Wichert Akkerman
2004-12-16  5:49             ` Willy Tarreau
2004-12-14 22:07         ` Kyle Moffett
2004-12-15  2:23           ` Adam Denenberg
2004-12-15  3:19             ` Kyle Moffett
2004-12-15 14:16               ` Adam Denenberg
2004-12-15 19:07                 ` Jan Harkes
2004-12-15 19:22                   ` Adam Denenberg
2004-12-15 20:06                     ` linux-os
2004-12-15 20:19                       ` Adam Denenberg
2004-12-15 20:45                         ` Doug McNaught
2004-12-15 20:48                           ` Adam Denenberg [this message]
2004-12-15 20:57                             ` Doug McNaught
2004-12-16  6:10                     ` Willy Tarreau
2004-12-16 14:24                   ` Adam Denenberg
2004-12-16 14:51                     ` Jan Harkes
2004-12-16 15:00                       ` Adam Denenberg
2004-12-16  6:03             ` Willy Tarreau
2004-12-16 14:17               ` Adam Denenberg

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=1103143730.6825.19.camel@sucka \
    --to=adam@dberg.org \
    --cc=doug@mcnaught.org \
    --cc=jaharkes@cs.cmu.edu \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=mrmacman_g4@mac.com \
    /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