On 2024-01-25 18:23, Alexander Zubkov wrote:
On Thu, Jan 25, 2024 at 6:11 PM Maria Matejka wrote:
On 2024-01-25 17:08, Alexander Zubkov wrote:
But I think the problem with no filters is bigger when the RTR server is out.
It is not just the short period of time when the peer can announce
On Thu, Jan 25, 2024 at 6:11 PM Maria Matejka wrote:
>
> On 2024-01-25 17:08, Alexander Zubkov wrote:
>
> But I think the problem with no filters is bigger when the RTR server is out.
> It is not just the short period of time when the peer can announce anything.
> If rpki autoreload is on it
On 2024-01-25 17:08, Alexander Zubkov wrote:
But I think the problem with no filters is bigger when the RTR server
is out. It is not just the short period of time when the peer can
announce anything. If rpki autoreload is on it will cause all bad
announces that was rejected before to pass the
But I think the problem with no filters is bigger when the RTR server is
out. It is not just the short period of time when the peer can announce
anything. If rpki autoreload is on it will cause all bad announces that was
rejected before to pass the filter now. And if we turn rpki autoreload off,
AFAIK in RPKI AS0 means implicit invalid.
On Thu, Jan 25, 2024, 14:31 Maria Matejka via Bird-users <
bird-users@network.cz> wrote:
> On 2024-01-25 11:55, Erin Shepherd wrote:
>
> Spitballing slightly here, but could you avoid this problem by adding
> 0.0.0.0/0+ ::0/0+ AS0 RoAs to the table and
On 2024-01-25 11:55, Erin Shepherd wrote:
Spitballing slightly here, but could you avoid this problem by adding
0.0.0.0/0+ ::0/0+ AS0 RoAs to the table and accepting ROA Unknowns?
Obviously the disadvantage here is that if your IRR RTR server goes
down you're basically unfiltered, but it at
On Thu, Jan 25, 2024 at 11:55:14AM +0100, Erin Shepherd wrote:
> Spitballing slightly here, but could you avoid this problem by adding
> 0.0.0.0/0+ ::0/0+ AS0 RoAs to the table and accepting ROA Unknowns?
>
> Obviously the disadvantage here is that if your IRR RTR server goes
> down you're
On Thu, Jan 25, 2024 at 11:41:25AM +0100, Job Snijders wrote:
> On Thu, Jan 25, 2024 at 11:13:51AM +0100, Jeroen Massar via Bird-users wrote:
> > a quick stab at generating the slurm file:
>
> why use SLURM though? SLURM doesn't have a 'maxLength' field like the
> regular JSON input formatted in
Spitballing slightly here, but could you avoid this problem by adding
0.0.0.0/0+ ::0/0+ AS0 RoAs to the table and accepting ROA Unknowns?
Obviously the disadvantage here is that if your IRR RTR server goes down you're
basically unfiltered, but it at least avoids the availability problem
- Erin
On Thu, Jan 25, 2024 at 11:13:51AM +0100, Jeroen Massar via Bird-users wrote:
> a quick stab at generating the slurm file:
why use SLURM though? SLURM doesn't have a 'maxLength' field like the
regular JSON input formatted in this style has:
https://console.rpki-client.org/rpki.json - which might
10 matches
Mail list logo
