sraustein
commented
7 years ago I suspect that the prefix/len-maxlen syntax doesn't work in the GUI, and that the error you're seeing in the second test is really left over from the first (GUI) test.
The exception BadIPResource is raised when parsing a prefix, not when parsing a ROA request per se, which says that something is passing a string that is not really a prefix to the prefix parser. Presumably this should have been caught somewhere earlier in the call chain, like when you pressed the submit button on the form. I don't see a code path by which the ROA request parser (rpki.resource_set.roa_prefix.parse_str()) can raise this error (it would raise BadROAPrefix if it were unhappy), so I don't see a path by which the rpkic code would do this.
Assuming that something managed to stuff a bad ROA request into the IRDB, I would expect that to persist until something else removed that request. Which is a little puzzling if you ran rpkic load_roa_requests after getting into trouble with the GUI, because I would expect the rpkic command to delete all ROA requests then recreate the ones it wants to keep.
fendemann
Using the GUI to create a roa I can provide a prefix and a "Max len". Using it results in a roa (listed in the GUI) with the values
Prefix Max Length AS 49.20.0.0/19-24 24 4920
BUT also in an error in rpkid.log _2017-01-10 21:25:39 rpkid[1362]: <rpki.rpkidtasks.UpdateROAsTask {LAB-DTAG}>: Could not update <ROA: LAB-DTAG 4920 49.20.0.0/19-24>, skipping: BadIPResource: Bad IP resource "49.20.0.0/19-24"
Using the rpkic roa import with my old roa.csv 49.10.0.0/19-24 4910 DTAG 49.20.0.0/19-24 4920 DTAG 49.20.100.0/24 4920 DTAG ...
it results in the same error message _2017-01-10 21:38:33 rpkid[1362]: <rpki.rpkidtasks.UpdateROAsTask {LAB-DTAG}>: Could not update <ROA: LAB-DTAG 4920 49.20.0.0/19-24>, skipping: BadIPResource: Bad IP resource "49.20.0.0/19-24"
I
ve looked in my old installation documentation for my lab szenario and found that roa.csv that Ive used in the past to create the roas for my testbed. This file worked fine with the old version of your software but not with the actual one.