Description of problem: When having dhcpv6 tests in the server mode,we found that The recieved Relay- reply message do not include Advertise message in some scenarios. Version-Release number of selected component (if applicable): kernel-2.6.18-43.el5 Software Environment: Testee(NUT): RHEL5 Kernel:2.6.18-43.el5 Tester(TN): FreeBSD6.2 v6eval-3.0.12.tar.gz TAHI package: DHCPv6_Self_Test_P2_1_0_7.tar.gz How reproducible: every time Steps to Reproduce: 1. Configure TAHI test environment. 2. Run the TAHI test suite 3. After the test completes, check for the results Actual results: The recieved Relay-reply message do not include Advertise message Expected results: The recieved Relay-reply message should include Advertise message Additional info: please refer to http://focus.brisbane.redhat.com/~zwu/dhcp_server/20071101/DHCPv6_Self_Test_P2_ 1_0_7_server/rfc3315/index.html (1) 37 Part C : Relay-Reply message transmission through the layered Relay agents
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Fixed upstream and will be in dhcpv6-1.0.5.
Recenty, i run DHCPv6_Self_Test_P2_1_0_8.tar.gz separately with dhcpv6-1.0.10 and dhcpv6-1.0.4 on RHEL5.2 (RHEL5.2-Server-20080212.0) and found a problem that many test cases Pass with dhcpv6-1.0.4 while they all Fail with dhcpv6-1.0.10. for more details, pls refer to 1.test reports with dhcpv6-1.0.4 on rhel5.2 (1)http://focus.brisbane.redhat.com/~zwu/RHEL5.2-Server-20080212.0/20080220/DHCPv6_Self_Test_P2_1_0_8_server_1.0.4/rfc3315/index.html (2)http://focus.brisbane.redhat.com/~zwu/RHEL5.2-Server-20080212.0/20080220/DHCPv6_Self_Test_P2_1_0_8_server_1.0.4/rfc3646/index.html (3)http://focus.brisbane.redhat.com/~zwu/RHEL5.2-Server-20080212.0/20080220/DHCPv6_Self_Test_P2_1_0_8_server_1.0.4/rfc3736/index.html 2.test reports with dhcpv6-1.0.8 on rhel5.2 (1)http://focus.brisbane.redhat.com/~zwu/RHEL5.2-Server-20080212.0/20080220/DHCPv6_Self_Test_P2_1_0_8_server_1.0.10/rfc3315/index.html (2)http://focus.brisbane.redhat.com/~zwu/RHEL5.2-Server-20080212.0/20080220/DHCPv6_Self_Test_P2_1_0_8_server_1.0.10/rfc3646/index.html (3)http://focus.brisbane.redhat.com/~zwu/RHEL5.2-Server-20080212.0/20080220/DHCPv6_Self_Test_P2_1_0_8_server_1.0.10/rfc3736/index.html
I thank that the test reports with dhcpv6-1.0.4 on rhel5.2 should be same with those with dhcpv6-1.0.10 on rhel5.2 the bug still exists when using dhcpv6-1.0.10 to have a test. for the test result, pls see: (1)http://focus.brisbane.redhat.com/~zwu/RHEL5.2-Server-20080212.0/20080220/DHCPv6_Self_Test_P2_1_0_8_server_1.0.10/rfc3315/37.html
a more thing, they are all running tests on dhcpv6 server.
In order to debug this problem, we need the test case for RHEL 5.2 with an exact reproducer, including output with verbose debugging messages from the DHCPV6 software. One way to do this would be to extract the commands that TAHI runs. The man pages for dhcp6s, dhcp6r, and dhcp6c all show how to generate verbose debug messages.
*** Bug 363571 has been marked as a duplicate of this bug. ***
Fixed in dhcpv6-1.0.10-2.el5.
The current version of dhcpv6 does not work with multiple relays. This is a known problem and will be addressed upstream.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.