You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the key chain is created in the default PIB/TPM ($HOME/.ndn/{ndnsec-key-file/,pib.db} and the router key/identity/certificate are created in the scenario context (not in the router context). As a consequence, we cannot run parallel simulations (due to file lock on $HOME/.ndn/pib.db) and also the n-th router knows about the identities of the (n-1)-th and not the opposite, which leads to inconsistency in Pib:
Currently, the key chain is created in the default PIB/TPM ($HOME/.ndn/{ndnsec-key-file/,pib.db} and the router key/identity/certificate are created in the scenario context (not in the router context). As a consequence, we cannot run parallel simulations (due to file lock on $HOME/.ndn/pib.db) and also the n-th router knows about the identities of the (n-1)-th and not the opposite, which leads to inconsistency in Pib:
NDVR should be able to run an in-memory router's KeyChain:
The text was updated successfully, but these errors were encountered: