interfaces bug
Cathy Almond
cathya at isc.org
Wed May 11 13:31:47 UTC 2011
Hi Sergey,
We verified that this is a bug - thanks for investigating and bringing
it to our attention.
Please could you make the report to dhcp-bugs at isc.org - thanks!
(See https://www.isc.org/software/dhcp/news for details of our mailing
lists and bug/feature reporting email addresses).
Kind regards,
Cathy
On 07/05/11 16:47, Sergey Naumov wrote:
> 2011/5/6 Sergey Naumov <sknaumov at gmail.com>:
>> Hello.
>>
>> I want to report a regression in dhcp4 (4.1-ESV-R2) in contrast to dhcp3.
>>
>> Lets assume that there is an interface definition in dhclient.conf
>> (interface "eth1" { ... }).
>>
>> If I run
>> #> killall dhclient
>> #> echo -n > /tmp/dhclient.leases (there is symbolic link to this
>> file)
>> #> ifconfig eth1 0.0.0.0 up
>> #> dhclient -cf /etc/dhcp/dhclient.conf
>> there is no action for eth1 (tcpdump doen't show any dhcp traffic).
>>
>> I figured out that it happens for interface with 0.0.0.0 address or
>> interface which had 0.0.0.0 address before it was put down.
>> The problem somewhere in discover_interfaces(DISCOVER_UNCONFIGURED), because
>> "interface" list is identical (empty) for working and not working case
>> before this function and in the bad case there is no eth1 interface in this
>> list after this function (in the good case there is eth1 with REQUESTED,
>> AUTOMATIC flags and after config parsing AUTOMATIC flag disappears).
>>
>> Environment: buildroot + uclibc-0.9.31 system based on busybox 1.17.1,
>> linux-2.6.35 kernel, dhclient-script slightly modified (0 address replaced
>> with 0.0.0.0 because busybox's ifconfig does not accept 0 as valid address).
>>
>> By the way, is there a way to disable bind compilation in dhcp 4.2 (I have
>> problems with cross-compilation with uclibc)?
>>
>> Thanks in advance,
>>
>> Sergey Naumov.
>>
>
> It seems that ioctl(SIOCGIFADDR) for interface with 0.0.0.0 address
> returns EADDRNOTAVAIL in next_iface4() function and such interfaces
> are not included in the list. Is it correct behavior?
> _______________________________________________
> dhcp-hackers mailing list
> dhcp-hackers at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-hackers
More information about the dhcp-hackers
mailing list