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/db-wg@ripe.net/
[db-wg] Route(6) objects
- Previous message (by thread): [db-wg] Route(6) objects
- Next message (by thread): [db-wg] Route(6) objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kaupo Ehtnurm
kaupo at wavecom.ee
Fri Jul 7 08:57:05 CEST 2023
Hello By doing this the internet will always (also under normal circumstances) prefer that one provider. My goal is for internet only prefer the traffic via this provider only when there is DDoS attack. And if I would have to do this manually, then it beats the purpose of automatic DDoS protection service. And in this case I would still have to create all the 65536 /48 route6 objects but instead of pointing to provider AS they would be pointing to my AS. Lugupidamisega / Best regards, Kaupo Ehtnurm Network & System administrator WaveCom AS ISO 9001 & 27001 Certified DC and verified VMware Cloud kaupo at wavecom.ee | +372 5685 0002 Endla 16, Tallinn 10142 Estonia | [ http://www.wavecom.ee/ | www.wavecom.ee ] ----- Original Message ----- From: "Randy Bush via db-wg" <db-wg at ripe.net> To: "Kaupo Ehtnurm via db-wg" <db-wg at ripe.net> Sent: Thursday, July 6, 2023 8:28:24 PM Subject: Re: [db-wg] Route(6) objects you can do it yourself announce the more specifics to the provider who gives ddos mediation, and the less specific, /32, to the non-protecting provider be sure that any IRR and RPKI data are good for both the aggregate and the specifics randy -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- Previous message (by thread): [db-wg] Route(6) objects
- Next message (by thread): [db-wg] Route(6) objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]