No IPv6 traffic

Jim mickeyboa at sbcglobal.net
Sun Aug 30 01:16:52 UTC 2009


On 08/29/2009 08:15 PM, Michael Fleming wrote:
> On Sat, 29 Aug 2009 11:26:06 -0400
> Jim<mickeyboa at sbcglobal.net>  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 at home can't connect.
>>> When I disable IPv6 in the system the applet connects but Yum
>>> behaves the same (multiple tries) and still folding at 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
>>>
>>> I have another machine, F11, behind the same ADSL router, Dlink DSL
>>> 500B, without problems.
>>>
>>> Any ideas?
>>>
>>> Regards, Clodoaldo
>>>
>>>
>>>        
>> This IPV6 thing is a problem in FC11 , FC10, everyone of the of the
>> 12 boxes I have setup in FC11 I have had to do the below setup to
>> even connect to rpmfusion.org.
>>      
> Turning IPv6 related DNS lookups off (even in firefox) is NOT fixing the
> issue - will people please stop posting this utter trash as helpful
> information please? There's enough myths around IPv6 as it is and this
> isn't helping.
>
> (plus such people might want to look at how the getaddrinfo() call
> works..)
>
> The problem is the OP has *enabled* IPv6 - loaded the module etc. but
> hasn't *configured* it. It won't magically set up a tunnel / 6to4 /
> native connection, you have to do a little more tweaking
>
> See ipv6-6to4.howto in the initscripts documentation
> (/usr/share/doc/initscripts-<version>/) for a brief primer on 6to4,
> which will get you up and going without having to sign up for a tunnel
> broker etc.
>
> I have two IPv6 tunnels running - one on a Fedora 10 server (qbert,
> served by my ISP here in Australia) and a CentOS VM (gyruss) through
> Hurricane Electric - both work OK
>
> [root at qbert ~]# traceroute6 fedoraproject.org
> traceroute to fedoraproject.org (2610:28:200:1::fed0:1), 30 hops max,
> 80 byte packets
> 1  2001:44b8:61::62 (2001:44b8:61::62)  61.238 ms
> 63.470 ms  65.738 ms
> 2  vl67.cor1.adl6.internode.on.net
> (2001:44b8:8060:8000::1)  67.064 ms  69.794 ms  70.104 ms
> 3 gi0-0.bdr1.adl6.internode.on.net (2001:44b8:8060:14::1)  72.050 ms * *
> 4  pos4-2.bdr1.syd7.internode.on.net (2001:44b8:b070:2::1)  98.805 ms *
> *
> 5  pos1-3-0.bdr2.nrt1.internode.on.net (2001:44b8:f0a0:2::1)  217.948
> ms  219.611 ms  221.365 ms
>
> 6  equinix-tyo.he.net (2001:de8:5::6939:1) 223.472 ms  197.651 ms
> 198.828 ms
> 7  2001:470:0:119::1 (2001:470:0:119::1)  310.388 ms
> 310.695 ms  309.959 ms
> 8 10gigabitethernet3-2.core1.pao1.he.net
> (2001:470:0:32::2)  286.479 ms 286.684 ms  283.265 ms
> 9
> snvang.abilene.ucaid.edu (2001:504:d::bd) 318.081 ms  318.509 ms
> 318.226 ms
> 10  * * *
> 11  * * *
> 12 2001:468:ffff:155::2
> (2001:468:ffff:155::2)  358.482 ms  358.215 ms 357.666 ms
> 13 2610:28:10e:2::1 (2610:28:10e:2::1)  393.498 ms  393.133 ms  392.833
> ms
> 14  2610:28:105:13::2 (2610:28:105:13::2)  360.110 ms 360.089 ms
> 360.863 ms
> 15  2610:28:200:1::fed0:1 (2610:28:200:1::fed0:1)  361.113
> ms !X 360.678 ms !X  361.396 ms !X
>
> [mfleming at gyruss ~]$ traceroute6 fedoraproject.org
> traceroute to fedoraproject.org (2610:28:200:1::fed0:1), 30 hops max, 40 byte packets
>   1  dotprofile-1.tunnel.tserv8.dal1.ipv6.he.net (2001:470:1f0e:16f::1)  8.000 ms  8.000 ms  8.000 ms
>   2  gige-g2-14.core1.dal1.he.net (2001:470:0:78::1)  8.000 ms  8.000 ms  8.000 ms
>   3  10gigabitethernet1-4.core1.chi1.he.net (2001:470:0:c4::1)  36.002 ms  36.002 ms  36.002 ms
>   4  ge-2-2-0.11.rtr.chic.net.internet2.edu (2001:504:0:4:0:1:1537:1)  56.003 ms  56.003 ms  56.003 ms
>   5  * * *
>   6  2001:468:ffff:155::2 (2001:468:ffff:155::2)  68.004 ms  60.003 ms  60.004 ms
>   7   (2610:28:10e:2::1)  64.004 ms  64.004 ms  64.004 ms
>   8   (2610:28:105:13::2)  64.004 ms  64.004 ms  64.004 ms
>   9   (2610:28:200:1::fed0:1)  68.004 ms !X  68.004 ms !X  68.004 ms !X
>
> Michael.
>
>    
Well Mr Fleming it takes care of the problem until someone figures out 
the real problem.




More information about the fedora-list mailing list