Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Re-synch MAC failed during UE attach process #17
My setup is the following : Amarisoft eNodeB + NextEpc.
Here is the message I got each time I want to connect my UE to the network :
And if that can help, here is the content of the Mongo DB I use and a part of my config :
Maybe I missed something in the config ?
Thank you so much for your prompt answer.
Please find attached (here: captures.zip ) a zip file containing 2 pcaps : dump.lo.pcap which contains all the traffic on the loopback interface (so everything internal to nextepc) and dump.enb.pcap, which contains all the traffic between the eNB and nextepc.
Concerning K, OPc and AMF they are included in the mongoDB quote in my previous message :)
IMHO, it is a different issue with (#11). Authentication failure type is not resync-failure, but MAC failure.
Is USIM using Milenage Algorithm? Current, NextEPC is not supporting XOR and TUAK. Milenage algorithm is only supported. And also, please re-check K, OPc, and AMF of USIM.
Nevertheless, NextEPC needs to add one more feature related to MAC failure of authentication failure. This feature is not supported at this point.
added a commit
Feb 7, 2018
I've updated the handler related to authentication failure.
Previously, I sent Authentication request regardless EMM_CAUSE of Authentication failure. In other worlds, re-authorization was always performed. Currently, Re-authorization only works when EMM Cause is synch-failure. If EMM cause is not synch-failure, MME will send an Authentication reject.
BTW, this updates is not solving your problem. I think that security parameter should be matched between USIM and MongoDB. What happened? Are you succeeding to pass the authorization process?
Feel free to raise any problem if you need to help.
Anyway thank you for your prompt answer and sorry for the trouble...