On Sun, 2006-05-28 at 23:45 -0600, Darryl Gregorash wrote:
Install 9.0, do not install any updates; leave ipv6 enables, but do not do anything with it beyond allowing the LINKLOCAL ip to be assigned on the external interface. Then ftp (lukemftp package) to a known site that has a public ipv6 address (such as ftp.mozilla.org). Watch ftp wait forever for a response, because it is in a perennial loop, trying to send a SYN packet to an ipv6 address, originating from a LINKLOCAL ip.
Again, name resolution issue. If you mix IPv6 LINK LOCAL with IPv4 PUBLIC, without either providing a IPv6 PUBLIC (or old SITE LOCAL) -- or much easier -- just put in a router that handles such IPv4 to IPv6 issues, yes, you'll run into this. Is this any different than issues with IPv4? Nope. I'm _not_ against disabling IPv6. But I _am_ against _incorrect_ FUD being spread. Including what the problems are, that IPv6 is "broken," etc... -- Bryan J. Smith Professional, technical annoyance mailto:b.j.smith@ieee.org http://thebs413.blogspot.com ----------------------------------------------------------- Americans don't get upset because citizens in some foreign nations can burn the American flag -- Americans get upset because citizens in those same nations can't burn their own