Robert Elz wrote:
>   | (K4) IPv6 auto didn't work, and required redoing everything.
> 
> ?   Didn't work how?   (Bill you know better than to say "didn't work"
> as a bug report...)   Was there an IPv6 router sending RA packets?
> 
OK, I installed on another, well-connected, system at umich, and it 
still didn't work, so I took more notes: 

1) On the disconnected system, the prompt came by, I thought, "sure, 
I'll try IPv6, it says 'auto'"....

It came back and asked for a IPv6 DNS, I thought, "Oh, any one will do," 
and picked the 2nd, just to not pick the 1st.

The installer went away and thought for about 10 minutes.  Eventually, 
it gave me a failure message.  I didn't write it down. 

After that, it went back to the network configuration prompt, but 
nothing I did seemed to GET RID of the IPv6 information, and so it 
infinite looped between 10 minute non-message uninformative period, and 
sending me back to network menu. 

I had to choose to abort (I cannot remember whether that's the 1st or 
2nd "No").

2) OK, I tried on a network at citi.umich.edu, connected to multiple 
NAPs, and Internet2. 

Same problem.

It seems that the stickler is the local router isn't doing IPv6, and 
without that the IPv6 DNS is unreachable, and the autoconfig doesn't 
just do link local, and once the IPv6 DNS is entered it never goes away, 
and is therefore ping6 tested. 

That's all speculation, as the error messages are completely 
uninformative!

-- 
William Allen Simpson
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32