On Sat, 29 Aug 2009 21:16:52 -0400 Jim <mickeyboa@xxxxxxxxxxxxx> wrote: > On 08/29/2009 08:15 PM, Michael Fleming wrote: > > On Sat, 29 Aug 2009 11:26:06 -0400 > > Jim<mickeyboa@xxxxxxxxxxxxx> wrote: > > > > > >> On 08/29/2009 06:23 AM, Clodoaldo Pinto Neto wrote: > >> > >>> When capturing the traffic with Wireshark there is no IPv6 traffic > >>> at all. When I set network.dns.disableIPv6 to true I can see all > >>> IPv4 in Wireshark. This is Fedora 10 64. > >>> > >>> While it is easy to solve it for Firefox there are many services > >>> that can't connect even if I disable IPv6 in the system. One > >>> symptom is Yum has to try repetitively until it finds a suitable > >>> host: > >>> > >>> http://mirrors.ucr.ac.cr/fedora/releases/10/Everything/x86_64/os/repodata/repomd.xml: > >>> [Errno 4] IOError:<urlopen error (-2, 'Name or service not > >>> known')> Trying other mirror. > >>> > >>> Another is that the weather applet and folding@home can't connect. > >>> When I disable IPv6 in the system the applet connects but Yum > >>> behaves the same (multiple tries) and still folding@home can't > >>> connect. > >>> > >>> My name servers are set to opendns: > >>> > >>> # cat /etc/resolv.conf > >>> # Generated by NetworkManager > >>> nameserver 208.67.220.220 > >>> nameserver 208.67.222.222 > >>> nameserver 10.1.1.1 > >>> > >>> # cat /etc/sysconfig/network > >>> NETWORKING=yes > >>> HOSTNAME=d2.localdomain > >>> NETWORKING_IPV6=yes > >>> > >>> # cat /etc/sysconfig/network-scripts/ifcfg-eth0 > >>> # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express > >>> Gigabit Ethernet controller > >>> DEVICE=eth0 > >>> BOOTPROTO=none > >>> DNS1=208.67.220.220 > >>> DNS2=208.67.222.222 > >>> DNS3=10.1.1.1 > >>> GATEWAY=10.1.1.1 > >>> HWADDR=00:21:97:00:79:21 > >>> IPADDR=10.1.1.110 > >>> NETMASK=255.0.0.0 > >>> ONBOOT=yes > >>> TYPE=Ethernet > >>> USERCTL=no > >>> IPV6INIT=yes > >>> NM_CONTROLLED=yes > >>> PEERDNS=yes <snip > > > > Michael. > > > > > Well Mr Fleming it takes care of the problem until someone figures > out the real problem. > Except that it doesn't and you haven't read a single word I've written. Turning off IPv6 lookups for one application doesn't solve the issue at all, just acts as a placebo at the absolute best. Your "turn off lookups for AAAA/IPv6 records" so-called solution is in the long term worse than useless - and I'm being quite charitable here. The OP has loaded the IPv6 modules - this will ready the kernel for IPv6 traffic and allocate link-local IPv6, but does not connect the host to the public IPv6 network out of the box. This is normal behaviour for most if not all Linux distributions released in the last few years and even Windows XP and later for that matter. The workstation I'm sitting at for instance (F11/x86_64) has that precise configuration (my servers are fully IPv6 capable) You will get a globally routable address via a 6to4 tunnel (see the documentation reference I wrote earlier) or a tunnel broker like Sixxs or Hurricane Electric (he.net) - some network providers/ISPs even offer native connectivity; it never hurts to ask. As for the OP's issue I am very sure that it is a more general DNS resolution problem, given that (for example) mirrors.ucr.ac.cr has no AAAA record, and the single A record pointing to 163.178.174.25 from where I sit. If the OP is seeing differently then it confirms my theory. Michael. -- Michael Fleming <mfleming@xxxxxxxxxxxxxxxxxxx> - (EMail/XMPP/Jabber) WWW: http://www.thatfleminggent.com Fedora / Red Hat Packages: http://www.thatfleminggent.com/rpm-packages Twitter: http://twitter.com/thatfleminggent -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
