[LISPMAP-117] Map Notify Authentication Data is not computed correctly Created: 15/Jun/16  Updated: 19/Oct/17  Resolved: 27/Mar/17

Status: Resolved
Project: lispflowmapping
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug
Reporter: Vina Ermagan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 6071

 Description   

Map Notify Auth data is not built correctly in the MapServer. Currently it is just copied form the MapRegister, while it has to be computed properly using the Auth Key over the Map Notify data.



 Comments   
Comment by Lori Jakab [ 07/Jul/16 ]

Patch 1 submitted: https://git.opendaylight.org/gerrit/#/c/41514/

Comment by Lori Jakab [ 12/Jul/16 ]

Patch 2 submitted: https://git.opendaylight.org/gerrit/#/c/41599/

Comment by Lori Jakab [ 16/Feb/17 ]

This cropped up again. CSR1Kv debug logs show messages like:

*Feb 16 23:04:56.247: LISP-0: AF IID 0 IPv4, Map notify for 10.10.200.0/24 failed authentication.

Need to investigate if it is only fast path, or both slow and fast paths. Slow path was fixed a while ago, but we may have regressed.

Comment by Lori Jakab [ 17/Feb/17 ]

(In reply to Lori Jakab from comment #3)
> Need to investigate if it is only fast path, or both slow and fast paths.
> Slow path was fixed a while ago, but we may have regressed.

Disabling the Map-Register cache confirms that only the fast path is affected, slow path works fine.

Comment by Lori Jakab [ 17/Feb/17 ]

Fix proposed: https://git.opendaylight.org/gerrit/#/c/52016/

Generated at Wed Feb 07 20:06:32 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.