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."