On 01/12/2010 11:35 AM, Michael Cronenworth wrote: > Robert Moskowitz on 01/12/2010 12:29 PM wrote: >> inet6 addr: fe80::21b:77ff:fe43:978/64 Scope:Link > > Your issue with "timeouts" have nothing at all to do with IPv6. > > Please note two things in your IPv6 address. > 1) fe80 prefix - This is local only - think 127.0.0.1 for IPv4. > 2) Scope: Link - Same as above. I disabled IPv6 in Firefox and the time delays went away. The fe80 prefix is local link. This is for accessing any IPv6 device on your subnet. In fact when I do a route -A inet6 -n Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface fe80::/64 :: U 256 0 0 wlan0 ::/0 fe80::2149:9a62:1185:fd1c UGDA 1024 399 0 wlan0 > > If you, or any program, attempted to connect to an IPv6 address they > would immediately return "no route to host" as you are not on an IPv6 > network and you do not have a global IPv6 address. host www.ietf.org www.ietf.org has address 64.170.98.32 www.ietf.org has IPv6 address 2001:1890:1112:1::20 www.ietf.org mail is handled by 0 mail.ietf.org. PING 2001:1890:1112:1::20(2001:1890:1112:1::20) 56 data bytes ^C --- 2001:1890:1112:1::20 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2199ms > > Instead of bad-mouthing IPv6, you should look for the real root of the > problem. Possibly that IEEE doesn't have IEEE network engineers. Well it is an IETF issue not IEEE issue :) And the guys here are the same engineers that do the IETF meeting sessions. They say that there is NO IPv6 advertisements here, and that does seem to be the case. No RA and no DHCPv6. So it is my FC12 setup that is busy setting up a local scope v6 addr to use over the subnet that is causing grief. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
