Re: [db-wg] Time for new Announcements?
marcel, i think nick and cynthia answered your question. but there remains the question of where the heck one goes for day to day routing ops help. as cynthia pointed out, this wg is more for the policy and technical underpinnings, not actuall operations. what's strange is that it is not at all obvious where a relative newcomer goes for such discussion. in typical imperialist fashion, the North American Network Operators' Group mailing list [0] has become the default global ops list. i recommend it. there used to be the European Operators' Forum, but RIPE swollowed it about 2004 and now you can sign up for a glossy webinar from the NCC which will not actually answer your question if it even allowed you to ask it . and, because the nanog list has about 10,000 subscribers, the behavior is not always encouraging. you can safely just ignore snarky people such as i. [0] - https://mailman.nanog.org/mailman/listinfo/nanog randy --- ra...@psg.com `gpg --locate-external-keys --auto-key-locate wkd ra...@psg.com` signatures are back, thanks to dmarc header butchery
Re: [db-wg] Time for new Announcements?
Hi Marcel, I just want to start out by saying that the working groups are not a support channel and this more routing than anything db related. But with regards to your case, according to ripestat the prefixes are announced by 2 ASNs but overall have 100% visibility (99% for the v6). I am guessing any issues are most likely due to the other announcement. -Cynthia On Sat, Mar 13, 2021, 09:07 Marcel Zimmer via db-wg wrote: > Good morning dear community, > > > > it is an honor to be part of it :) > > > > We have applied for and been assigned our own AS at the beginning of the > year (AS212033). Since yesterday the link to the first peering partner > Lumen (AS3356) is available and the following networks should be announced: > > > > IPv4 193.3.45.0/24 > > IPv6 2a10:5dc0::/32 > > > > the corresponding routing objects sid created - so far so good :) > > > > Now yesterday I could observe the following: > > > > The first routers processed quite fast the Ipv4 routes and yesterday > evening we had the following picture while looking glass of the Ipv4 and > ipv6 network. > > > > https://www.bilder-upload.eu/bild-4a9957-1615622772.png.html > > https://www.bilder-upload.eu/bild-296f5c-1615622785.png.html > > > > Since then, somehow nothing happens. > > > > Do you have a tip for me where I should go troubleshooting? > > > > Greetings > > > > Marcel Zimmer >
Re: [db-wg] Time for new Announcements?
Marcel Zimmer via db-wg wrote on 13/03/2021 08:07: Do you have a tip for me where I should go troubleshooting? the prefixes are being originated by both as8422 and as212033. If you ask as8422 to stop announcing it, it should swing over to 212033. Nick
[db-wg] Time for new Announcements?
Good morning dear community, it is an honor to be part of it :) We have applied for and been assigned our own AS at the beginning of the year (AS212033). Since yesterday the link to the first peering partner Lumen (AS3356) is available and the following networks should be announced: IPv4 193.3.45.0/24 IPv6 2a10:5dc0::/32 the corresponding routing objects sid created - so far so good :) Now yesterday I could observe the following: The first routers processed quite fast the Ipv4 routes and yesterday evening we had the following picture while looking glass of the Ipv4 and ipv6 network. https://www.bilder-upload.eu/bild-4a9957-1615622772.png.html https://www.bilder-upload.eu/bild-296f5c-1615622785.png.html Since then, somehow nothing happens. Do you have a tip for me where I should go troubleshooting? Greetings Marcel Zimmer smime.p7s Description: S/MIME cryptographic signature
