Bug 498535
Summary: | DHCPv6 client doesn't form the DHCP REQUEST packets properly | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Bryan Mason <bmason> | ||||||||||||
Component: | dhcpv6 | Assignee: | Jiri Popelka <jpopelka> | ||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||||
Severity: | high | Docs Contact: | |||||||||||||
Priority: | high | ||||||||||||||
Version: | 4.8 | CC: | jfeeney, jwest, narendra_k, tao, wwlinuxengineering | ||||||||||||
Target Milestone: | rc | Keywords: | Patch | ||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | All | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | 476974 | Environment: | |||||||||||||
Last Closed: | 2012-06-14 20:21:11 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
Bryan Mason
2009-04-30 21:59:40 UTC
Created attachment 342020 [details] Proposed patch It looks like this was fixed with the following upstream commits: https://fedorahosted.org/dhcpv6/changeset/95e3fd53cf8487b6426d8f81bfdf9890275cb2e8 https://fedorahosted.org/dhcpv6/changeset/1155a69e9456e5883885175598731ba12de49c05 Is this correct? If so, then the attached patch is my attempt to backport these to RHEL 4 (other than line numbers, the only change I made was to change dhcp6_copy_list(&ia->addr_list, &request_list); to dhcp6_copy_list(&optinfo->addr_list, &request_list); in the patch). Created attachment 342024 [details]
Corrected patch
(In reply to comment #1) > Created an attachment (id=342020) [details] > Proposed patch > > It looks like this was fixed with the following upstream commits: > > https://fedorahosted.org/dhcpv6/changeset/95e3fd53cf8487b6426d8f81bfdf9890275cb2e8 > https://fedorahosted.org/dhcpv6/changeset/1155a69e9456e5883885175598731ba12de49c05 > > Is this correct? If so, then the attached patch is my attempt to backport > these to RHEL 4 (other than line numbers, the only change I made was to change > > dhcp6_copy_list(&ia->addr_list, &request_list); > > to > > dhcp6_copy_list(&optinfo->addr_list, &request_list); > > in the patch). This indeed looks like the patch which fixes this issue. I have two observations after applying this patch - 1. I tested the fix with a windows dhcpv6 server. Now the client gets an IPv6 address. 2. With a Linux DHCPv6 ( RHEL 5.2 dhcpv6 server) server, the client initially sends the proper request ( With a IA field) and gets a proper response, but immedielty after that repeats the whole process and this time the request is without a IA filed as advertised by the server. And the behaviour and result are as described in the problem description. I have attached the protocol traces to this issue. Created attachment 342312 [details]
dhcp6c with a RHEL 5.2 dhcp6s server
Created attachment 342314 [details]
dhcp6c with a windows dhcp6s server
(In reply to comment #3) > 2. With a Linux DHCPv6 ( RHEL 5.2 dhcpv6 server) server, the client initially > sends the proper request ( With a IA field) and gets a proper response, but > immedielty after that repeats the whole process and this time the request is > without a IA filed as advertised by the server. And the behaviour and result > are as described in the problem description. Does this mean that the Linux client was able to configure itself properly with an address from the Linux DHCPv6 server, but it just took an additional iteration? Created attachment 348461 [details]
dhcp6c debug output and packet trace with a linux server only.
(In reply to comment #6) > (In reply to comment #3) > > > 2. With a Linux DHCPv6 ( RHEL 5.2 dhcpv6 server) server, the client initially > > sends the proper request ( With a IA field) and gets a proper response, but > > immedielty after that repeats the whole process and this time the request is > > without a IA filed as advertised by the server. And the behaviour and result > > are as described in the problem description. > > Does this mean that the Linux client was able to configure itself properly with > an address from the Linux DHCPv6 server, but it just took an additional > iteration? No. Not properly. The first iteration the behaviour is proper. The second iteration it doesn't include the advertised address in it's request to the server, so the server replies with a different address than it advertised. I am attching a packet capture file and debug output of dhcp6c to this issue. The patch is fine by me for backporting to RHEL-4. Keep in mind that the version of dhcpv6 in RHEL-4 and RHEL-5 differ by years. The version in RHEL-5 is far more RFC compliant. I mention that because if a customer continues down the road of using dhcpv6 in RHEL-4, they are likely to hit a lot of problems. They would be much better off using RHEL-5 as that version of dhcpv6 has had significant improvements in order to improve RFC compliance and pass various IPv6 certifications. Just something to think about if more issues are found with the version in RHEL-4. I am not interested in backporting huge amounts of code to RHEL-4. However, if the goal is to make the version in RHEL-4 simply work for customers, then this patch is probably adequate. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. |