[Dnsmasq-discuss] problem with dhcp options
carlos at fisica.ufpr.br
Fri Jan 5 15:02:18 GMT 2007
Sorry, I only saw this msg. after replying to the other one.
Simon Kelley (simon at thekelleys.org.uk) wrote on 5 January 2007 07:42:
>Carlos Carvalho wrote:
>> I'm using the config below for dhcp in dnsmasq.
>> In /etc/dnsmasq.conf:
>> conf-file = /etc/dnsmasq/dhcp
>> In /etc/dnsmasq/dhcp:
>> # smtp server
>> dhcp-range = 192.168.5.1,static,5m
>> conf-file = /etc/dnsmasq/dhcp-hosts
>> And this is the config for one of the machines in /etc/dnsmasq/dhcp-hosts:
>> dhcp-host = abiod,00:e0:7d:d0:b8:e5,id:*,net:abiod
>> dhcp-boot = net:abiod,/var/remoteboot/pentium-rtl8139,hoggar
>> dhcp-option = abiod,19,/var/nfsroot/profs-root/abiod
> > In another machine with more recent software I get
> > *** glibc detected *** malloc(): memory corruption: 0x0804f278 ***
> > zsh: abort env - ./udhcpc -q -s ./script.udhcpc
>It looks like udhcp didn't behave well: you should probably use
>ethereal/wireshark or tcpdump to grab a copy of the DHCP packet and send
>it to the maintainers: If a broken packet make udhcp core dump, chances
>are that a suitably crafted broken packet can break root. udhcp should
>not be trusting its input from the net to be well-formed.
Agreed. Also I can probably hack around and not use udhcpc, will try
it now. However, there are more problems. First, machines don't get a
default route, which should be provided by the dhcp-option=3,zagros
line. I tested with two linux distributions (gentoo included), windows
98 and xp.
Second, I'm getting this in the logs for some machines:
dnsmasq: cannot send DHCP option 17: no space left in packet
dnsmasq: cannot send DHCP option 19: no space left in packet
I've put the right number for root path.
More information about the Dnsmasq-discuss