Bug 166508 - radvd and dhcpv6 dows not agree on the prefixes
Summary: radvd and dhcpv6 dows not agree on the prefixes
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: dhcpv6
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Jason Vas Dias
QA Contact:
URL: http://sourceforge.net/mailarchive/fo...
Depends On: 144585
Blocks: 168429
TreeView+ depends on / blocked
Reported: 2005-08-22 17:14 UTC by Jason Vas Dias
Modified: 2007-11-30 22:07 UTC (History)
0 users

Clone Of:
Last Closed: 2006-03-07 18:36:49 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0115 qe-ready SHIPPED_LIVE dhcpv6 bug fix update 2006-03-06 05:00:00 UTC

Description Jason Vas Dias 2005-08-22 17:14:20 UTC
+++ This bug was initially created as a clone of Bug #144585 +++

Description of problem:
(Just copying from the link)

"I manage to get the prefix for the client router which i saw from the 
 debug message, but I didn"t see any modification done to /etc/radvd.conf 
 by the dhcp6c program. I suppose it should modify the range of the 
 available IP addresses according to the assigned prefix." 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Set up dhcpv6 with correct prefix
2. restart dhcpv6 (server) and radvd
3. start dhcp6c on a client to get address
Actual results:
radvd will give you different prefixes than dhcp6

Expected results:
radvd and dhcp6 should agree on what to give the clients

Additional info:
There is also a patch provided on the url mentioned:
 in line 116 of radvd_token.l, 
     (before) : if (!strcmp(yytext, dhcp6_if->ifname))
     (after)  : if (strcmp(yytext, dhcp6_if->ifname))

Comment 1 Jason Vas Dias 2005-08-22 17:15:27 UTC
fixed with dhcpv6-0.10-14_EL4

Comment 8 Red Hat Bugzilla 2006-03-07 18:36:49 UTC
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 the 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.


Note You need to log in before you can comment on or make changes to this bug.