Bug 310406 - IPv6: Resolving breaks when changing nameserver from IPv6 to IPv4
Summary: IPv6: Resolving breaks when changing nameserver from IPv6 to IPv4
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Petr Baudis
QA Contact: E-mail List
URL:
Whiteboard: gnome-wrong-out-of-the-box
Keywords: should_go_upstream
Depends on:
Blocks:
 
Reported: 2007-09-13 20:48 UTC by Petr Baudis
Modified: 2008-12-07 22:21 UTC (History)
5 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Baudis 2007-09-13 20:48:52 UTC 
Set nameserver in /etc/resolv.conf to IPv6 address, work in Firefox, then have NetworkManager reconnect and reset the nameserver to IPv4 address, Firefox breaks:

socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 24
connect(24, {sa_family=AF_INET6, sin6_port=htons(53), inet_pton(AF_INET6, "::ffff:172.16.0.1", &sin6_addr), sin6_flowinfo=16781484, sin6_scope_id=0}, 28) = -1 EAFNOSUPPORT (Address family not supported by protocol)

I'm actually not sure if the connect() should work or not... Maybe it's kernel fault?
Comment 1 JP Rosevear 2007-09-14 00:07:45 UTC 
Not just NetworkManager presumably but regular ifup/ifdown if the nameserver changes via dhcp as well.
Comment 2 Petr Baudis 2007-09-14 09:23:29 UTC 
Yes, NetworkManager was just an example real-world scenario.
Comment 3 Wolfgang Rosenauer 2007-09-26 07:35:29 UTC 
Hmm, Firefox is using libc resolver stuff. So the connect is initiated from the glibc resolver. I'm not sure if that is supposed to work. Would be nice to get some input from glibc guys.
Is Firefox really the only network application which fails in that case?
Comment 4 Donavan Pantke 2008-03-17 19:11:13 UTC 
I can verify that this also fails when using a simple ping.
Comment 5 Wolfgang Rosenauer 2008-04-01 13:55:34 UTC 
AFAICS there is no Mozilla code involved here.
Reassigning
Comment 6 Petr Baudis 2008-12-07 22:21:54 UTC 
Works for me in 11.0 and newer.