SIXSS not working?

I am seeing all IPv6 prefixes that are monitored by Sixxs as being down and unavailable.

Anyone know why?

Thanks,
Hank

Hmmm, I didn't see this on info@sixxs.net which would be the usual place
to report any issues with respect to SixXS, but there the same reply
would be given: which monitoring of which prefixes?

I can only assume you mean the GRH portion of SixXS:
http://www.sixxs.net/tools/grh/status/

But there most of it looks fine (ignoring the broken peering sessions)
thus I can only wonder what the issue might be. But maybe I am missing
something obvious :wink:

If you do see something that looks out of the ordinary, don't hesitate
to report it to info@sixxs.net as quite clearly stated on the contact
page and apparently needs repeating on the NANOG list...

Greets,
Jeroen

Ill report it to them but:
http://www.sixxs.net/tools/grh/tla/
Shows every country as V=0 (prefixes visible per country).

-Hank

It would appear that whatever was broken is now fixed.

-Hank

Good morning (at least on this side of the planet),

On 2012-06-20 02:14, Hank Nussbacher wrote:> On Wed, 20 Jun 2012, Jeroen
Massar wrote:

Ill report it to them but:

NANOG is afaik still not the "contact the people who run things" email
address...

Nevertheless, if issues, do not hesitate to report to info@sixxs.net

Ghost Route Hunter : IPv6 DFP visibility :: SixXS - IPv6 Deployment & Tunnel Broker
Shows every country as V=0 (prefixes visible per country).

That would mean that every prefix was not updated in the last day,
sounds odd to me.

It would appear that whatever was broken is now fixed.

The only thing I can think of is that you have noticed some weird glitch
of the kind there.

As mentioned above the "Visible" is basically the amount of prefixes
visible in the last 24 hours. For that to become 0 it would have meant
that no prefix would have been seen for the last 24 hours.

According to http://www.sixxs.net/tools/grh/status/ which just telnets
into grh.sixxs.net and asks for quagga's status, seems that even peering
sessions are connected for longer than that, thus I am puzzled to what
could have caused that then.

Greets,
Jeroen

http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-1820 possibly related?

Until such time that Sixxs responds as to what happened, it will all be conjecture.

-Hank

I pointed to the status page for a reason, the sessions are up for a
much longer time than that.

But yes, we are fully aware that the quagga and the rest of GRH needs to
be swapped out with a better bgpd etc, something with time etc though.

Greets,
Jeroen

(still wondering why this is on NANOG, but ala, seems it is important
enough to discuss here which is cool though :wink:

still wondering why this is on NANOG

maybe ipv6 is becoming relevant to operations?

randy