-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to work with max prefix length #853
Comments
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 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 |
I´ve tried the procedure once again. First I´ve loaded a roa.csv file with only one Class C Prefix to delete all other entries related to LAB-DTAG. After the import a roa was created and published, it was also shown in the GUI. ———————— fen@rpki-dtag-01:~$ date --utc fen@rpki-dtag-01:~$ more roas_play.csv fen@rpki-dtag-01:~$ sudo rpkic load_roa_requests roas_play.csv fen@rpki-dtag-01:~$ sudo rpkic show_published_objects 2017-01-11 07:18:50 rpkid[1362]: Sending <Element {http://www.hactrn.net/uris/rpki/publication-spec/}publish at 0x7fe0fffd1b48> hash = None uri = rsync://rpki-root-01.lab.dtag.de/rpki/LAB-DTAG/S7iEwdcoQ0DaG15eLlJw7VUWZ-s.roa to pubd 2017-01-11 08:24:00 rpkid[1362]: Sending <Element {http://www.hactrn.net/uris/rpki/publication-spec/}publish at 0x7fe0ffef6098> hash = e0b6d9f7d4ae948eeffca1d997faccb7373d0159acbe834379357d33f7559e8b uri = rsync://rpki-root-01.lab.dtag.de/rpki/LAB-DTAG/sBabYTbJtSqE7ctuQmhESyZC8zQ.crl to pubd ———————— fen@rpki-dtag-01:~$ date --utc fen@rpki-dtag-01:~$ sudo rpkic show_published_objects fen@rpki-dtag-01:~$ vi roas_play.csv fen@rpki-dtag-01:~$ sudo rpkic load_roa_requests roas_play.csv fen@rpki-dtag-01: 2017-01-11 09:59:59 rpkid[1362]: 200 POST /left-right (172.20.0.52) 21.04ms If you mention that this is a problem of the GUI error, what can I do to reset my servers?? |
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.rpkid_tasks.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.rpkid_tasks.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 I
ve 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.The text was updated successfully, but these errors were encountered: