Bug 165882
Summary: | dhcp6c failed: interface eth0 iaid failed to be created | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Bieringer <pb> |
Component: | dhcpv6 | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | dhcpv6-0.10-14_FC4 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-01 18:04:21 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: | |||
Bug Depends On: | |||
Bug Blocks: | 166505 |
Description
Peter Bieringer
2005-08-13 15:09:09 UTC
This bug is now fixed with dhcpv6-0.10-14_FC4 , available from: http://people.redhat.com/~jvdias/dhcpv6/FC4 and which will shortly be released in fc4-updates-testing . The code was using the obsolete ioctl(sockfd, SIOGIFCONF,...) to get the hardware addresses for the interfaces in order to construct the iaid in client6_addr.c's create_iaid() function. The SIOGIFCONF ioctl only lists devices which have an IPv4 address . create_iaid() now uses glibc's getifaddrs(...) to list the interfaces, which does not require them to have an IPv4 address. Any interface to be configured with dhcp6c MUST however have a LINK LOCAL IPv6 address, which is automatically assigned by the IPv6 module when the device is first brought up . Please try out the dhcpv6-0.10-14 version and let me know of any issues. BTW, the configuration with which I tested was: SERVER /etc/dhcp6s.conf: interface eth1 { renew-time 60; rebind-time 90; prefer-life-time 130; option dns_servers fec0:0:0:1::1 jvd6.; allow rapid-commit; link eth1 { pool { range fec0:0:0:1::10 to fec0:0:0:1::19/64; }; }; }; SERVER command: # dhcp6s -dDf eth1 CLIENT /etc/dhcp6s.conf: ( NONE ) CLIENT command: # dhcp6c -dDf eth0 Please append the server and client conf files, the commands used to run them, and the output of these commands on your client and server systems when reporting any dhcpv6 bugs: # ip link show # ip addr show Thank You! It's working now, thank you for fixing it - sorry for delay, I was busy. BTW: do you know the reason for the message: netlink_recv_rtgenmsg error Sep/06/2005 20:40:17 hash add client iaidaddr type 0 for duid 00:01:00:01:0a:90:bb:f0:00:00:39:ea:77:81 for iaid 3929604096 Sep/06/2005 20:40:17 add an address fec0:0:0:f101::1001 on eth0 Sep/06/2005 20:40:17 open_netlink_socket called Sep/06/2005 20:40:17 netlink_send_rtmsg called Sep/06/2005 20:40:17 netlink_recv_rtgenmsg called Sep/06/2005 20:40:17 netlink_recv_rtgenmsg error Sep/06/2005 20:40:17 netlink_send_rtgenmsg called Sep/06/2005 20:40:17 netlink_recv_rtgenmsg called Sep/06/2005 20:40:17 get_if_flags called Sep/06/2005 20:40:17 get_if_flags called Sep/06/2005 20:40:17 netlink_recv_rtgenmsg error strace shows me that this are triggered after recvmsg(15, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\221\345\35C\273\v\0\0\0\0\0\0dhcp6c: netlink_recv_rtgenmsg called\0:10Yg\1\0n eth0\0000:01:Ig\1\0001:0a:90:bb:f0:00:00:39:01:23:45 for iaid 3929604096\0\21g\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0... In reply to comment #4: Yes, I noticed that message, but as yet have not had time to investigate further, since the routes created seem to be OK . Are the routes created OK for you ? ie. doing an 'ip route show' after dhcp6c configures an interface should show correct routes for the (IPv6 address)/prefix you configured on the server - it does for me. If the routes are incorrect, or you don't like those messages, please raise another bug report about them. |