Hello - just wanted to report a little (easily reproducable) problem: I’m experimenting with BIRD 2.0.2 on a lab-router (Ubiquiti Edgerouter, MIPS platform) and RPKI. In my attempts to examine ROA tables more closely I entered „show route table r4 all“ into birdc and bird immediately segfaulted and died. Is there any „official“ way to examine the contents of ROA tables other than „eval roa_check(r4, 186.255.72.0/24, 204777)“? I would have assumed „show route table r4 all 186.255.72.0/24“ or something like that would work, but it doesn’t (gives empty output). At least „show route table r4 count“ gives useful information, though. Thanks, Clemens
Hello! Before I try to get some MIPS to check this issue, could you please send me your binary and core file? It should be analyzable on my amd64 desktop. Anyway, inspecting the ROA table by show route command should work and this is definitely a bug. Thank you for the report! Maria On November 5, 2018 2:47:36 AM GMT+01:00, Clemens Schrimpe <clemens.schrimpe@gmail.com> wrote:
Hello -
just wanted to report a little (easily reproducable) problem: I’m experimenting with BIRD 2.0.2 on a lab-router (Ubiquiti Edgerouter, MIPS platform) and RPKI.
In my attempts to examine ROA tables more closely I entered „show route table r4 all“ into birdc and bird immediately segfaulted and died.
Is there any „official“ way to examine the contents of ROA tables other than „eval roa_check(r4, 186.255.72.0/24, 204777)“?
I would have assumed „show route table r4 all 186.255.72.0/24“ or something like that would work, but it doesn’t (gives empty output). At least „show route table r4 count“ gives useful information, though.
Thanks,
Clemens
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Mon, Nov 05, 2018 at 08:47:36AM +0700, Clemens Schrimpe wrote:
Hello -
just wanted to report a little (easily reproducable) problem: I’m experimenting with BIRD 2.0.2 on a lab-router (Ubiquiti Edgerouter, MIPS platform) and RPKI.
In my attempts to examine ROA tables more closely I entered „show route table r4 all“ into birdc and bird immediately segfaulted and died.
Hello Does it crash without 'all'? Works for me: bird> show route table rtab4 Table rtab4: 212.1.128.0/19-19 AS9105 [rpki1 13:28:00.854] * (150) 213.129.152.0/21-21 AS47834 [rpki1 13:28:00.851] * (150) 202.3.160.0/20-24 AS17408 [rpki1 13:28:00.786] * (150) 88.132.72.0/21-21 AS35311 [rpki1 13:28:00.841] * (150) 157.100.182.0/24-24 AS27947 [rpki1 13:28:00.839] * (150) ... Attached patch should fix the crash.
Is there any „official“ way to examine the contents of ROA tables other than „eval roa_check(r4, 186.255.72.0/24, 204777)“?
Currently ROA has to be specified as a whole, including maxlen and ASN, not just its prefix. Confusingly, it uses slightly different syntax to enter ROAs and to print ROAs: bird> show route 212.1.128.0/19 max 19 as 9105 table rtab4 Table rtab4: 212.1.128.0/19-19 AS9105 [rpki1 13:28:00.854] * (150) -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
In my attempts to examine ROA tables more closely I entered „show route table r4 all“ into birdc and bird immediately segfaulted and died.
Hello
Does it crash without 'all'? Works for me:
No. It’s just the „all“ keyword bringing it to its knees.
Attached patch should fix the crash.
Thanks. Will try that sometime this week.
Currently ROA has to be specified as a whole, including maxlen and ASN, not just its prefix. Confusingly, it uses slightly different syntax to enter ROAs and to print ROAs:
bird> show route 212.1.128.0/19 max 19 as 9105 table rtab4 Table rtab4: 212.1.128.0/19-19 AS9105 [rpki1 13:28:00.854] * (150)
Hmmm … good to know. But stuff like „show route table r4 as 4711“ would be useful too - at some point … *hint*hint* :-) Clemens
On Tue, Nov 06, 2018 at 08:28:00AM +0700, Clemens Schrimpe wrote:
Currently ROA has to be specified as a whole, including maxlen and ASN, not just its prefix. Confusingly, it uses slightly different syntax to enter ROAs and to print ROAs:
bird> show route 212.1.128.0/19 max 19 as 9105 table rtab4 Table rtab4: 212.1.128.0/19-19 AS9105 [rpki1 13:28:00.854] * (150)
Hmmm … good to know. But stuff like „show route table r4 as 4711“ would be useful too - at some point … *hint*hint*
You can use filters: show route table r4 where net.asn = 4711 -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
You can use filters: show route table r4 where net.asn = 4711
That indeed works. And now I also found what I was looking for in the documentation:
NET_ROA4 and NET_ROA6 prefixes hold an IP prefix range together with an ASN. They support the same special operators as IP prefixes, and also .maxlen which extracts maximal prefix length, and .asnwhich extracts the ASN.
Thanks for the pointer! Clemens PS: Any of your crew here at IETF-103 in Bangkok?
On November 6, 2018 7:52:09 AM GMT+01:00, Clemens Schrimpe <clemens.schrimpe@gmail.com> wrote:
You can use filters: show route table r4 where net.asn = 4711
That indeed works. And now I also found what I was looking for in the documentation:
NET_ROA4 and NET_ROA6 prefixes hold an IP prefix range together with an ASN. They support the same special operators as IP prefixes, and also .maxlen which extracts maximal prefix length, and .asnwhich extracts the ASN.
Thanks for the pointer!
Clemens
PS: Any of your crew here at IETF-103 in Bangkok?
No. We'll be there at least for a while at IETF-104 in Prague as we are based there so it is just several minutes far from our office. Maria
participants (3)
-
Clemens Schrimpe -
Maria Jan Matějka -
Ondrej Zajicek