aboutsummaryrefslogtreecommitdiff
path: root/8f5c91bdb64f4675e2e50f1e2d4b5af39ffbdb2c
diff options
context:
space:
mode:
authorTom Harrison <tomh@apnic.net>2018-08-25 14:11:12 +1000
committerRob Austein <sra@hactrn.net>2018-08-26 14:54:34 -0400
commit349194f64968fdade05c70db900e8518d56114ad (patch)
tree366fd036bc65e29a8fee63c29ea5f836e0f8fbc9 /8f5c91bdb64f4675e2e50f1e2d4b5af39ffbdb2c
parent1acf23f78c839e16998ae391811b1152709b8377 (diff)
[max-length] Fix ROA parsing issue
The ROA update and generate methods were parsing the ipv4 and ipv6 instance variables as if they were resource sets, rather than ROA prefix sets. This works as expected when max-length is not being used, but when max-length is used, parsing does not succeed and ROAs cannot be generated or updated. Parsing each variable as if it's a ROA prefix set, and then converting the result to a resource set, appears to fix the problem. Signed-off-by: Rob Austein <sra@hactrn.net>
Diffstat (limited to '8f5c91bdb64f4675e2e50f1e2d4b5af39ffbdb2c')
0 files changed, 0 insertions, 0 deletions