Router should reject /localhost prefix registration
Steps to reproduce:
- Connect to a testbed router over TCP.
- Send a prefix registration command for
Expected: the prefix registration command should be rejected because
/localhost Interest cannot be forwarded to a remote router.
Actual: the prefix registration command succeeds; after disconnecting, HTTP status page stops working and shows 504 error.
Updated by Junxiao Shi over 1 year ago
Updated by Eric Newberry about 1 year ago
One issue presenting itself as I work on this is determining the face scope from the RIB. Since the RIB manager runs in a separate thread from the rest of management, we shouldn't directly use the FaceTable from the RIB manager, as can be done in the FIB manager to get this kind of face information. Any suggestions on how to proceed? One idea I had was issuing a request for face scope information from the RIB manager to the Face manager and using this information to accept or deny the request.
Updated by Davide Pesavento about 1 year ago
Junxiao Shi wrote:
Management thread can lock data structure of main thread and read it directly. FaceTable is lockable and readable through this mechanism.
yeah, I wouldn't call that "directly accessing the table"... Also if you just want to add locking you can do that without #4529.