Re: ROVv6 does not behave the same way as ROVv4: What rookie mistake(s) did I make?

2021-03-04 Thread heasley
Tue, Mar 02, 2021 at 09:18:06PM +0700, Pirawat WATANAPONGSE via NANOG: > For a “second validator”, which choice is better: second copy of the same > software, or different software altogether? Arrcus ArcIQ has a validator, RTR server, and has monitoring capabilities and support.

Re: ROVv6 does not behave the same way as ROVv4: What rookie mistake(s) did I make?

2021-03-03 Thread Lukas Tribus
Hello, On Tue, 2 Mar 2021 at 15:18, Pirawat WATANAPONGSE via NANOG wrote: > We just turned on our RPKI Route Origin Validation yesterday, then something > weird happened: > [Reference: We are running NLnet Labs’ Routinator 3000, feeding a > Cisco ASR 1000 Series router. I know, I know, we

Re: ROVv6 does not behave the same way as ROVv4: What rookie mistake(s) did I make?

2021-03-02 Thread Douglas Fischer
Based on the difficulties I have already experienced, I would bet on some default route (or for example 2001::/16) statically placed on your FIB pointing to an Upstream. Or even the simple absence of the default route (::/0) pointing to null. Em ter., 2 de mar. de 2021 às 11:21, Pirawat

ROVv6 does not behave the same way as ROVv4: What rookie mistake(s) did I make?

2021-03-02 Thread Pirawat WATANAPONGSE via NANOG
Dear all, We just turned on our RPKI Route Origin Validation yesterday, then something weird happened: [Reference: We are running NLnet Labs’ Routinator 3000, feeding a Cisco ASR 1000 Series router. I know, I know, we haven’t started a second validator yet.] When we tested against the two