Fix handling of retractions with no next-hop again.
RFC 8966 Section 3.2.6 says that the route table is indexed by triples of the form (prefix, plen, neigh). Our indexing used to be incorrect, we'd sometimes include the next hop address, which made it impossible to interpret retractions with no next hop.
Showing
Please register or sign in to comment