-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
Using a configuration file to enable prefixes to be hICN does not always work properly. In particular, we discover that the fib entry referring to the next hop for the prefix to enable is not created properly and it points to a drop adjacency. This never occurs if prefixes are enabled with the api or the cli.
When enable is called from a configuration file:
2001::2/128
unicast-ip6-chain
[@0]: dpo-load-balance: [proto:ip6 index:34 buckets:1 uRPF:33 to:[0:0]]
[0] [@0]: dpo-drop ip6
b001::/64
unicast-ip6-chain
[@0]: dpo-load-balance: [proto:ip6 index:33 buckets:1 uRPF:36 to:[0:0]]
[0] [@19]: hicn-mw
Face 1: nat address 2001::1 locks 1, path_label 0
[@4]: arp-ipv6: via 2001::2 memif1/0 weight 0 FIB
When enable is called from the cli/api:
2001::2/128
unicast-ip6-chain
[@0]: dpo-load-balance: [proto:ip6 index:34 buckets:1 uRPF:37 to:[0:0]]
[0] [@3]: arp-ipv6: via 2001::2 memif1/0
b001::/64
unicast-ip6-chain
[@0]: dpo-load-balance: [proto:ip6 index:33 buckets:1 uRPF:36 to:[0:0]]
[0] [@19]: hicn-mw
Face 0: nat address 2001::1 locks 1, path_label 0
[@3]: arp-ipv6: via 2001::2 memif1/0 weight 0 FIB