Topic: e-smith 4.1 dhcp startup error

[Sergei Slobodov]

Here is the dhcp start error
value 65989 exceeds max (255) for precision.
/etc/dhcpd.conf line 28: too few numbers.
    fixed-address 10.65989;
                           ^
/etc/dhcpd.conf line 29: semicolon expected.
}
^
/etc/dhcpd.conf line 36: host declarations not allowed here.
host
^
/etc/dhcpd.conf line 41: host declarations not allowed here.
host
^
/etc/dhcpd.conf line 50: unexpected end of file

^
Configuration file errors encountered -- exiting
exiting.

I've tried, unsuccessfully:
- reboot
- re-expand dhcp template
- reconfigure dhcp range from console
- remove the only customized template I had (some masq stuff)

Looks like bug. Nothing in the FAQ or forums.

Ideas?

Thanks,
Sergei

[Alejandro]

You should check your dhcpd.conf file, a standard install would have a file no longer than 30 - 35 lines, so I would say your file is corrupted or some template process was done in a wrong way (?)
I extracted this, hope you find it usefull
 
subnet 192.168.1.0 netmask 255.255.255.0
{
    option broadcast-address    192.168.1.255;
    deny bootp;
    option domain-name  "domain.ext";
    option domain-name-servers  192.168.1.1;
    default-lease-time          86400;
    max-lease-time              604800;
    option netbios-dd-server    192.168.1.1;
    option netbios-name-servers 192.168.1.1;
    option netbios-node-type    8;
    option subnet-mask          255.255.255.0;
    range    192.168.1.65 192.168.1.250;
    option routers 192.168.1.1;
}

This is a standard file,with the default setting of a fresh install (domain.ext should be your domain and extension)
Alejandro

[Sergei Slobodov]

I discovered that the errors are from the PPTP parts of the dhcpd template... Reducing the PPTP connections to 0 from the config screen did not change the /etc/dhcpd.conf, so I had to manually cut the offending piece out and restart dhcpd to get it to work.

Hope someone from e-smith reads this and figures out how a line like

fixed-address 10.65989

could appear in the template expander output...

Sergei

[steve bush]

I have the same problem on two servers.
It is in the PPTP section like you mentioned.
I am suspecting it is a bug relating to the subnet
I chose for my network.

I have the 10.x.x.x A class network subnetted with 255.255.0.0

Here is the problem section, I have PPTP set for 5 sessions.

host pptpd51450
{
    fixed-address 10.200.51450;
}
 
host pptpd51451
{
    fixed-address 10.200.51451;
}
 
host pptpd51452
{
    fixed-address 10.200.51452;
}
 
host pptpd51453
{
    fixed-address 10.200.51453;
}
 
host pptpd51454
{
    fixed-address 10.200.51454;
}