public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spam at messir dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10083] IPV6 getaddrinfo and AI_ADDRCONFIG
Date: Tue, 21 Apr 2009 11:51:00 -0000	[thread overview]
Message-ID: <20090421115105.18493.qmail@sourceware.org> (raw)
In-Reply-To: <20090419085937.10083.spam@messir.net>


------- Additional Comments From spam at messir dot net  2009-04-21 11:51 -------
Here two test cases with describe problem(I hope). glibc info: http://
dpaste.com/36218/
I'm afraid it could be ubuntu-specific bug. Unfortunally I can't check on 
another distro (I'm surrounded by ubuntu and freebsd).

First test case:
===========
/tmp$ ./a.out 
getaddrinfo: Address family for hostname not supported
$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
qlen 1000
    link/ether 00:18:f3:02:2f:31 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.42/24 brd 192.168.0.255 scope global eth0
    inet6 fe80::218:f3ff:fe02:2f31/64 scope link 
       valid_lft forever preferred_lft forever
17: tun_exelap: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc 
pfifo_fast state UNKNOWN qlen 100
    link/[65534] 
    inet 172.16.1.20 peer 172.16.1.1/32 scope global tun_exelap
===========


Second case:
===========
/tmp$ sudo ip addr add 7777:7777:7777:7777:7777:7777:7777:7777/32 dev eth0
/tmp$ ./a.out 
address resolved!
/tmp$ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
qlen 1000
    link/ether 00:18:f3:02:2f:31 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.42/24 brd 192.168.0.255 scope global eth0
    inet6 7777:7777:7777:7777:7777:7777:7777:7777/32 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::218:f3ff:fe02:2f31/64 scope link 
       valid_lft forever preferred_lft forever
17: tun_exelap: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc 
pfifo_fast state UNKNOWN qlen 100
    link/[65534] 
    inet 172.16.1.20 peer 172.16.1.1/32 scope global tun_exelap
===========


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10083

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


  parent reply	other threads:[~2009-04-21 11:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  8:59 [Bug libc/10083] New: " spam at messir dot net
2009-04-19 20:59 ` [Bug libc/10083] " pasky at suse dot cz
2009-04-20  9:09 ` spam at messir dot net
2009-04-20 22:08 ` pasky at suse dot cz
2009-04-21 11:51 ` spam at messir dot net [this message]
2009-04-21 20:02 ` pasky at suse dot cz
     [not found] <bug-10083-131@http.sourceware.org/bugzilla/>
2014-07-01  7:07 ` 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=20090421115105.18493.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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).