public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/799] New: Resolver on GNU/kFreeBSD fails with IPv4 nameservers
Date: Wed, 23 Mar 2005 17:07:00 -0000	[thread overview]
Message-ID: <20050323170736.799.aurelien@aurel32.net> (raw)

When used on GNU/kFreeBSD (Debian GNU/kFreeBSD), the resolver fails if the
nameserver are IPv4 nameservers, but works if the nameserver are IPv6 nameservers. 

The problem is that the socklen argument of connect() is always the length of an
IPv6 socket address, even if the socket address is an IPv4 one. It does not hurt
the Linux kernel, but it does hurt the FreeBSD kernel.

Patch will follow. Please note that this patch doesn't break resolver on GNU/Linux.

-- 
           Summary: Resolver on GNU/kFreeBSD fails with IPv4 nameservers
           Product: glibc
           Version: 2.3.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: aurelien at aurel32 dot net
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i386-kfreebsd-gnu
  GCC host triplet: i386-kfreebsd-gnu
GCC target triplet: i386-kfreebsd-gnu


http://sources.redhat.com/bugzilla/show_bug.cgi?id=799

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2005-03-23 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 17:07 aurelien at aurel32 dot net [this message]
2005-03-23 17:08 ` [Bug libc/799] " aurelien at aurel32 dot net
2005-03-23 17:10 ` aurelien at aurel32 dot net
2005-03-23 17:11 ` aurelien at aurel32 dot net
2005-03-23 23:02 ` aurelien at aurel32 dot net

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=20050323170736.799.aurelien@aurel32.net \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).