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 ]
Thomas Schäfer
tschaefer at t-online.de
Tue Jun 25 14:26:32 CEST 2019
Am Dienstag, 25. Juni 2019, 12:47:57 CEST schrieb Bjørn Mork: > 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. I used the looking glasses at both sites. They don't see each other. I already contacted the peering guy at AS3320. He wrote me that zayo doesn't maintain a "AS-set" anymore, so DTAG cannot filter on it. I have no much clue about bgp, as-sets, peeringdb, rpki and so on. It's not my business. I am just a user/customer of the DTAG and other ISPs. Of course there are discussions about security filtering and money, even if bigger ISPs are involved. In this case it seems to me it's a security thing. For me it is just one connectivity failure. ( I am part of the costumer trial ipv6-only at DTAG) Regards, Thomas
- 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 ]