Red Hat Bugzilla – Bug 353481
TAHI--About IPv6 routing header issue
Last modified: 2014-06-03 08:49:44 EDT
Description of problem:
When we have tests about "RFC 2460 - IPv6 Specification" by IPv6 test suite
from TAHI and NUT is set to be the router mode, we found some failing tests
about IPv6 routing header.For more
detaily information ,please refer to "Additional info".
Reply packet is not right.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure TAHI test environment.
2. Run the TAHI test suite
3. After the test completes, check for the results
TN can not receive Echo Reply or forwarded Echo Request from NUT.
TN can receive Echo Reply or forwarded Echo Request from NUT.
Note: IPv6 Ready Logon Phase-2 and NUT is set to be the router mode.
For more information,please refer to
(1) 52 Responding to Routing Header - End Node
(2) 53 Unrecognized Routing Type - End Node
(3) 55 Routing Header Reserved Field - End Node
(4) 56 Routing Header Reserved Field - Intermediate Node (Routers Only)
(5) 57 Part A: Header Extension Length Odd
(6) 58 Part B: Address[i] is Multicast
(7) 59 Part A: Header Extension Length Odd
(8) 60 Part B: Segments Left Greater Than Number of Addresses
(9) 63 Part E: Hop Limit = 0.
(10)64 Part F: Hop Limit = 1.
(11)65 Part G: Valid Processing
Also about IPv6 routing header:
when IPv6 Ready Logon Phase-2 and NUT is set to the host mode,
pls refer to the url below:
(1) 38 Responding to Routing Header - End Node
(2) 39 Unrecognized Routing Type - End Node
(3) 40 Routing Header Reserved Field - End Node
(4) 41 Part A: Header Extension Length Odd
(5) 42 Part B: Address[i] is Multicast
RFC 5095 has been approved and RH0 is now considered depracated from supported
TAHI test suite 1.5.0-b2 (beta) contains an option in config.txt that allows the
test to succeed based on the draft version on RFC 5095. It is expected that the
final release of TAHI Self Test 1.5.0 will follow RFC 5095 guidelines.
Adding firstname.lastname@example.org to the cc list as the manager of the disabled user email@example.com who reported this bug
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).