This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] IPv6 auto-tagging failure?
- Previous message (by thread): [atlas] IPv6 auto-tagging failure?
- Next message (by thread): [atlas] New on RIPE Labs: Measuring Countries and IXPs in the SEE Region
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Tue Apr 21 11:33:47 CEST 2015
Dear Bjørn, This was caused by an issue with the particular controller that your probe was connected to. This issue affected 30 probes in total, and prevented their IPv6 capability from being properly detected. The problem has now been fixed, and you can see that your probe is now tagged as "IPv6 Capable". Within a few hours it will also be tagged as "IPv6 Works" as long as it carries out successful IPv6 measurement results. Sorry for the inconvenience, and thanks for pointing this out! Regards, Chris Amin RIPE NCC Developer On 21/04/2015 09:12, Bjørn Mork wrote: > Hello, > > I'm wondering a bit about the IPv6 auto-tagging. I recently reveived a > v3 probe and connected it to a dual-stack enabled network. The probe > was initially tagged as > > 2015-04-16 20:23 UTC Probe auto-tagged Your probe #22894 was automatically tagged as "system: IPv6 Capable" > > but then (on the next batch run?, after a couple of quick firmware > upgrades (3.3.8 => 4650 => 4680): > > 2015-04-17 08:23 UTC Probe auto-untagged Your probe #22894 was automatically untagged as "system: IPv6 Capable" > > and there it has been since. This wouldn't worry me too much if it > otherwise worked, but I noticed that the probe isn't listed with an "ASN > v6" either. So I assume the missing tag prevents it from being used for > v6 probing? > > AFAICS, the probe does take the announced prefix, and is actually *using* > the provided IPv6 connectivity. The "Connection History" shows that it > consistently uses its SLAAC address to connect to the controller. > > So why isn't it tagged as IPv6 capable/works etc? > > In desperation I tried different netwrok settings, static address, > adding v6 DNS, and fiddling with the managed/other flags along with > matching DHCPv6 config. Made no difference of course. If I understood > correctly, the probe firmware won't currently do any DHCPv6, and v6 DNS > is optional as long as there is a working v4 resolver available. > > > Bjørn > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2713 bytes Desc: S/MIME Cryptographic Signature URL: </ripe/mail/archives/ripe-atlas/attachments/20150421/606907ca/attachment.p7s>
- Previous message (by thread): [atlas] IPv6 auto-tagging failure?
- Next message (by thread): [atlas] New on RIPE Labs: Measuring Countries and IXPs in the SEE Region
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]