Actions
Bug #3524
closed
AutoPrefixPropagator: asymmetric log level
Start date:
03/09/2016
Due date:
% Done:
100%
Estimated time:
0.50 h
Description
Steps to reproduce:
- set log level
AutoPrefixPropagator=TRACE - properly configure automatic prefix propagation with
ndn:/my-identitycertificate trusted by the HUB nfdc register /localhop/nfd tcp4://hobondnpingserver /my-identity/hello- look at NFD logs
1457558803.878112 INFO: [AutoPrefixPropagator] this is a prefix registered by some hub: /localhop/nfd
1457558803.878515 INFO: [AutoPrefixPropagator] redo 0 propagations when new Hub connectivity is built.
1457558807.584872 INFO: [RibManager] Adding route /ndn/edu/arizona/cs/shijunxiao/hello/ping nexthop=265 origin=0 cost=0
1457558807.630564 TRACE: [AutoPrefixPropagator] start propagate /ndn/edu/arizona/cs/shijunxiao
1457558807.751975 TRACE: [AutoPrefixPropagator] success to propagate /ndn/edu/arizona/cs/shijunxiao
1457558822.254201 INFO: [RibManager] Removing route /ndn/edu/arizona/cs/shijunxiao/hello/ping nexthop=265 origin=0
1457558822.327040 INFO: [AutoPrefixPropagator] start revoke propagation of /ndn/edu/arizona/cs/shijunxiao
1457558822.683380 TRACE: [AutoPrefixPropagator] success to revoke propagation of /ndn/edu/arizona/cs/shijunxiao
Expected: start propagate and start revoke propagation of have the same log level
Actual: start propagate has TRACE level, but start revoke propagation of have INFO level
Updated by Junxiao Shi about 8 years ago
- Assignee set to Yanbiao Li
Also, I suggest using the term advertise and withdraw for the two cases.
Rationale: These operations are similar to advertise and withdraw in routing protocols, but usually on one hop.
Updated by Yanbiao Li over 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 60
Updated by Junxiao Shi over 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 60 to 100
Actions