 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Hi all,
I have a doubt regarding MN-AAA extension. Please help me to solve this.
When the mobile node has sent a request with MN-AAA extension, what are the parameters to be filled in each field of the Radius request?
The draft draft-ietf-mobileip-radius-challenge-00 says:
The CHAP-ID octet of the RADIUS CHAP-password attribute will contain the last byte of the Challenge value from MIP FA Challenge extension[6]. The authenticator from the MN-AAA Authentication extension MUST be used as the CHAP-Password attribute. The User-Name attribute MUST be populated with the user-name attribute from the AMR message. The following data stream, as described earlier, MUST be included in the CHAP- Challenge attribute:
Preceding Mobile IP data || Type, Length, SPI.
We made CHAP-ID as the last byte of the challenge value from MIP FA Challenge extension, Password as the authenticator from MN-AAA extension, and username attribute is also correct. In CHAP-Challenge field, currently we are filling the MD5 checksum of the preceding mobile ip data || Type, Length, SPI. Is this correct? How can we fill the preceding mobile IP data as it is since size of the data can vary each time?
Now the radius server is rejecting the request every time. What are the correct parameters to be filled?
Please do reply. Thanks & Regards Manju
This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
|
--
Mip4 mailing list: Mip4 at ietf.org
Web interface: https://www1.ietf.org/mailman/listinfo/mip4
Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/