Re: dhcpcd v6.7.1 'realloc() error"
Roy Marples
Sat Sep 19 16:35:35 2015
On 19/09/2015 12:15, Roy Marples wrote:
> On 18/09/2015 22:58, David Hauck wrote:
>> I've recently turned on a couple DHCPv4 scope options in the Win2012
>> DHCP Server that our 'dhcpcd' clients talk to. Unfortunately this has
>> resulted in the following dhcpcd error (and termination):
>>
>> *** Error in `dhcpcd': realloc(): invalid next size: 0x0942d820 ***
>>
>> When I remove these options and reboot (restart dhcpcd) the error
>> goes away and 'dhcpcd' is back to normal. As a result I need to
>> either turn off DHCP completely on our 'dhcpcd' targets or remove the
>> problematic DHCPv4 server scope options.
>>
>> The two scope options are: 066 Boot Server Hostname (value is an IP
>> address) 067 Bootfile Name (value is "pxelinux.0")
>>
>> Any ideas?
>
> The problem is two fold. Firstly, option 66 should be a string and not
> an ip address - unless you are encoding the ip address as a string (such
> as "12.34.56.78" which should work).
> Secondly, if the above is correct there is an error with the option
> parser when it discovers an incorrect value which needs fixing!
...
> I'll try and setup a test case later tonight, but if in the meantime you
> can collect a full tcpdump of the DHCP message causing the problem, that
> might help speed things up, or at least clarify where the error is.
I setup tftp_server_name as both a string ip address and a numeric ip
address and both times dhcpcd worked fine, both dhcpcd-6.7.1 and my
current trunk. It correctly failed to decode the numeric ip address and
successfully decoded the string.
So I'll need more information such as your dhcpcd.conf and a tcpdump please.
Maybe a backtrace as well would be useful.
Thanks
Roy
Archive administrator: postmaster@marples.name