|
My SixXS address not found by the SixXS looking glass
![[nz]](/s/countries/nz.gif) Shadow Hawkins on Sunday, 22 August 2010 10:40:58
Hi when I put my tunnel prefix 2001:4428:200:84::2/64 into the SixXS looking glass it comes back saying nothing can see it.
Also has the error:
Warning: Prefix doesn't have a route6 object! Add a route6 object to the relevant RIR's Routing Registry to make sure it gets accepted
Here is a link to the report:
GRH query for 2001:4428:200:84::2/64
Seems a bit strange that SixXS can't see itself!
My SixXS address not found by the SixXS looking glass
It is because you are doing it wrong(tm)! ;)
You are asking the system if "2001:4428:200:84::2/64" exists in BGP.
This is not the case, and thus the system reports that back to you.
If you would query for just the address, thus 2001:4428:200:84::2 you will get:
grh.sixxs.net> show bgp 2001:4428:200:84::2
BGP routing table entry for 2001:4428::/32
Paths: (127 available, best #11, table Default-IP-Routing-Table)
Not advertised to any peer
31383 12859 12859 12859 12859 12859 6939 4826 18119
2001:4038:: from 2001:4038:: (83.137.16.2)
....and a lot lot more...
This as the /64 does not exist, but only the /32 of the ISP, which thus covers the PoP's /40 and your tunnel's /40 is announced in BGP.
Do also note that SixXS itself does not run any routing infrastructure, the ISPs who provide the PoPs do that, as they run the PoPs. GRH is a bit special as it can be seen as a router, but it actually is just a looking glass.
|
![[ch]](/s/countries/ch.gif)
on Sunday, 22 August 2010 10:46:21
Posting is only allowed when you are