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/ripe-atlas@ripe.net/
[atlas] raspbian.net/raspbian.org ipv6 peering problems
- Previous message (by thread): [atlas] raspbian.net/raspbian.org ipv6 peering problems
- Next message (by thread): [atlas] raspbian.net/raspbian.org ipv6 peering problems
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bjørn Mork
bjorn at mork.no
Tue Jun 25 12:47:57 CEST 2019
Thomas Schäfer <tschaefer at t-online.de> writes: > Hello, > > I am not sure if I am right here with my question. > > Does someone measurements to the server of "raspbian"? > > Their hoster (bytemark, iomart, zayo?) seems not to be able to > establish correct peerings. At least the peering to AS3320 is broken. > I already contacted 3320. They say zayo doesn't fulfill the minimum > security requirements. The staff at Bytemark are both clueful and responsive in my experience. Did you try to contact them? In what way is the peering broken? Hmm.... I see at https://f-lga1.f.de.net.dtag.de/index.php?pageid=lg that AS3320 seems be missing all the Bytemark IPv6 routes. Looks like they don't have any connectivity to Bytemark's transit upstream, which is AS20860 according to the RIPE db. I believe this is a fault at AS3320. It's not just Bytemark they are filtering out here. You can look up for example 2001:1b40::/32 or 2a01:b040::/32. They are also missing in the AS3320 table. Bjørn
- Previous message (by thread): [atlas] raspbian.net/raspbian.org ipv6 peering problems
- Next message (by thread): [atlas] raspbian.net/raspbian.org ipv6 peering problems
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]