Red Hat Bugzilla – Bug 612007
[TAHI][MIPv6][MN]The source address of an echo reply packet is still an address before movement
Last modified: 2014-06-18 04:30:29 EDT
Created attachment 429947 [details]
Description of problem:
The source address of an echo reply packet is still an address(3ffe:501:ffff:102:223:aeff:fe8f:3c23) before movement when MN(NUT#) moves from LinkX to LinkY.
NUT is short for Node Under Test.
LinkX global 3ffe:501:ffff:102::/64 foreign link
LinkY global 3ffe:501:ffff:103::/64 foreign link
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The source address of an echo reply packet(No 42 Packet and the fourth echo reply in the tcpdump file) is still an address((3ffe:501:ffff:102:223:aeff:fe8f:3c23)) before movement when MN(NUT#) moves from LinkX to LinkY.
The test details can be seen as follows:
1 The test topology and procedure can be seen in http://focus.bne.redhat.com/~xhu/MIPv6/ct-mipv6-mn-rhel6-auto/mipv6-mn/MN-0-0-0-3-001.html
2 The test result can be seen http://focus.bne.redhat.com/~xhu/MIPv6/ct-mipv6-mn-rhel6-auto/mipv6-mn/189.html
3 The tcpdumpfile can be seen in "189_html_Link0.pcap" attachment
The source address of an echo reply packet is an address(3ffe:501:ffff:103:223:aeff:fe8f:3c23) after movement when MN(NUT#) moves from LinkX to LinkY.
Created attachment 429948 [details]
configure file of mipv6-daemon on MN NUT
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
mipv6-daemon-188.8.131.5210203bgit-1.el6 should fix this issue.
Please be so kind and add a few key words to the technical note of this
bugzilla entry using the following structure:
For details, see:
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
What actions or circumstances cause this bug to present.
What happens when the bug presents.
What was done to fix the bug.
What now happens when the actions or circumstances above occur.
Note: this is not the same as the bug doesn’t present anymore.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.