public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sthomas at linux dot vnet.ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16154] New: resolv code not able to update resolv.conf for ipv6
Date: Mon, 11 Nov 2013 12:34:00 -0000	[thread overview]
Message-ID: <bug-16154-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16154

            Bug ID: 16154
           Summary: resolv code not able to update resolv.conf for ipv6
           Product: glibc
           Version: 2.17
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: sthomas at linux dot vnet.ibm.com
                CC: drepper.fsp at gmail dot com

If we call dhclient as follows in its not able to update resolv.conf even
though the tcpdump shows that the system receives ipv6 DNS namserver
information to be updated

dhclient -6 -nw -S eth0

-bash-4.2# tcpdump -i eth0
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

00:09:24.900136 IP6 localhost.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6
inf-req
00:09:25.951474 IP6 localhost.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6
inf-req
00:09:27.973827 IP6 localhost.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6
inf-req
00:09:31.868104 IP6 localhost.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6
inf-req
00:09:35.872764 IP6 fe80::200:ff:fe00:a0a0.dhcpv6-server >
localhost.dhcpv6-client: dhcp6 reply


I compiled the same dhclient with glibc version glibc-2.17 and it works just
fine. Therefore I am assuming here its problem in glibc code itself 

I tested this on Fedora 19 glibc-2.17 and dhclient-4.2.5(from ISC website)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-11-11 12:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 12:34 sthomas at linux dot vnet.ibm.com [this message]
2013-11-11 12:35 ` [Bug libc/16154] " sthomas at linux dot vnet.ibm.com
2013-11-12  5:43 ` sthomas at linux dot vnet.ibm.com
2013-11-12  5:44 ` sthomas at linux dot vnet.ibm.com
2013-11-12  5:44 ` sthomas at linux dot vnet.ibm.com
2014-01-08  9:56 ` sthomas at linux dot vnet.ibm.com
2014-01-08  9:57 ` sthomas at linux dot vnet.ibm.com
2014-01-08  9:58 ` sthomas at linux dot vnet.ibm.com
2014-01-08  9:58 ` sthomas at linux dot vnet.ibm.com
2014-06-13 12:19 ` fweimer at redhat dot com

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=bug-16154-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).