[atlas] v6 support

Hi Randy,

On Tue, May 29, 2012 at 05:59:54AM +0900, Randy Bush wrote:
> >> this mailing list *really* works!  a few minutes after posting the
> >> above, the problem went away, the device got a global ipv6 addy after a
> >> couple of weeks without.
> 
> any idea about this magic?

from what i gather the probe got first RA around epoch 1337782688, and reported around 2012-05-23 14:20:09 UTC.
When the UI got updated, that is close to magic:) I can't explain!!

However, if you look at "Show last 25 connections" you see an entry for 2012-05-27 16:38:58 UTC from a v6 address.
that means, in the worst case, UI could have picked up V6 address change around that time.
Also, after this reconnection it sent/received v6 measurements.

> >>> and 2283 managed to get a v6 address but no gateway, and of course no
> >>> v6dns.
> >>                    IPv4           IPv6    
> >> Internet Address:  147.28.0.132   2001:418:1:0:220:4aff:fee0:246d
> >> Local Address:     147.28.0.132   2001:df9::220:4aff:fee0:246d/64
> >> Gateway:           147.28.0.1     Undetermined/Unknown
> > 
> > V6 Gateway is not reported in the UI.
> 
> any chance for a low priority cosmetic fix for this?

One day we shoule improve the UI; no idea when. To do it right we have to show multiple addresses and gateways. The probe can have multiple V6 addresses. When it receives multiple RA(different prefixes) and static IPv6 address it ends up with multiple V6 gateways too. Then it is a bit messy to show.

Just now you switched to static V6. Yes,there was some down time, but it is back now:) 
Now the fun begins, because the probe has two v6 address and two gateways, ::1 and the one it got via RA! 

regards,
-antony