Topic: dhcpd.conf error in range [Bug 8298 - Resolved]

[Allan Pritchard]

HI All

This maybe a bug but before I go down that track I thought I would get some advice having never submitted a bug before
We were using a Cisco router in our office that was set to be the DHCP server. We have changed this to the SME server

SME 8.0 - fully up to date
The only additional contrib is the user vacations

We configured the DHCP range in the admin panel to 192.168.2.100 to 192.168.2.199. We have check this in the panel
The GUI server manager panel shows the same range in the "review configuration"

However no one could get a lease from the DHCP server requiring us to manually set DHCP address.

Looking at the DHCP config shows that the address range is in fact 192.168.2.100 to 192.168.2.99
which is a negative range of numbers. Looking through the dhcpd log there are hundreds of entries
that say no free lease except for two leases 192.168.2.100 and 192.168.2.99. I have pasted a small
section of the log below the dhcp.conf

Before I go and change the range in the server admin panel to see if it re-writes the dhcp.conf file
I thought I better see if anyone wants any further information or if it should be entered as a bug.


[root@sammy dhcp]# cat /etc/dhcpd.conf
#------------------------------------------------------------
#              !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at http://www.contribs.org/development/
#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------


# Addresses from 192.168.2.100 to 192.168.2.199 taken for PPTP sessions


authoritative;
ddns-update-style none;
option wpad-url code 252 = text;

subnet 192.168.2.0 netmask 255.255.255.0
{
    option broadcast-address    192.168.2.255;
deny bootp;
    option domain-name  "apdesign-ami.co.nz";
    option domain-name-servers  192.168.2.253;
    default-lease-time          86400;
    max-lease-time              604800;
    option netbios-dd-server    192.168.2.253;
    option netbios-name-servers 192.168.2.253;
    option netbios-node-type    8;
    option subnet-mask          255.255.255.0;
    range    192.168.2.100 192.168.2.99;
    option routers 192.168.2.1;
    option wpad-url            "http://wpad.apdesign-ami.co.nz/wpad.dat";

}



2014-04-01 13:58:47.692785500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:58:56.130201500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:04.226030500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:12.868633500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:21.473443500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:24.355026500 Wrote 2 leases to leases file.
2014-04-01 13:59:24.378376500 DHCPREQUEST for 192.168.2.99 from 38:0f:4a:bc:6b:f1 (ADAMs-iPad) via bond0
2014-04-01 13:59:24.378378500 DHCPACK on 192.168.2.99 to 38:0f:4a:bc:6b:f1 (ADAMs-iPad) via bond0
2014-04-01 13:59:29.693417500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:37.889949500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:41.660042500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:44.126198500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases
2014-04-01 13:59:48.528942500 DHCPDISCOVER from 70:de:e2:4c:5a:72 via bond0: network 192.168.2/24: no free leases


Regards
Allan Pritchard

[mmccarn]

My dhcpd.conf settings seem to match my configuration db settings:

Code: [Select]

dhcpd=service
    Bootp=deny
    end=192.168.200.199
    start=192.168.200.110
    status=enabled

Code: [Select]

#------------------------------------------------------------
#        !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at http://www.contribs.org/development/
#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------





authoritative;
ddns-update-style none;
option wpad-url code 252 = text;

subnet 192.168.200.0 netmask 255.255.255.0
{
    option broadcast-address    192.168.200.255;
deny bootp;
    option domain-name "mydomain.us";
    option domain-name-servers 192.168.200.2;
    default-lease-time          86400;
    max-lease-time              604800;



    option subnet-mask          255.255.255.0;
    range    192.168.200.110 192.168.200.199;
option routers 192.168.200.2;
    option wpad-url            "http://wpad.mydomain.us/wpad.dat";

}


[Allan Pritchard]

Hi mmccarn

Yes, that's what I thought it should look like with the range being (for us)

    range    192.168.2.100 192.168.2.199;

It seems if there has been an error and the 1 has been dropped from the range
yet the server panel and the admin page both appear correct.

Is there a way to force the dhcpd.conf file to regenerate without rebooting the server

Regards
Allan

[mmccarn]

(Untested - entered from my mobile)

Code: [Select]

config setprop dhcpd start 192.168.2.100 end 192.168.2.199
expand-template /etc/dhcpd.conf
sv t dhcpd

- set your start and end values in case the '1' you're seeing in the end of the range isn't really a 1.
- recreate /etc/dhcpd.conf
- restart the dhcpd service (if it's supervised by tcpsvd)

[Stefano]

Allan

if mmccarn's suggestion doesn't work, please fill a bug asap

thank you

[Jáder]

Hi

I just saw this:

Code: [Select]

# Addresses from 192.168.2.100 to 192.168.2.199 taken for PPTP sessions
I think you choose too many PPTP clients and now your DHCP have no more free IPs to lease.

Verify that on server-manager, remoteacccess , first parameter.
It should be just a few (5 or 10?) to allow your remote clients to use PPTP.
It SHOULD NOT be 100 !

I hope I have found the error and not BEING A MORON

[Stefano]

nice shot jader

Allan, please report here the output of

Code: [Select]

config show pptpd

thank you

[Allan Pritchard]

Very strange, I have used the setprop dhcpd to set the range to 192.168.2.100 to 192.168.2.180 and now the range has 192.168.2.100 192.168.2.80

Once again the 1 is missing however the PPTP sessions show as correct as before.


[root@sammy ~]# config setprop dhcpd start 192.168.2.100 end 192.168.2.180
[root@sammy ~]# expand-template /etc/dhcpd.conf
[root@sammy ~]# cat /etc/dhcpd.conf
#------------------------------------------------------------
#              !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at http://www.contribs.org/development/
#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------


# Addresses from 192.168.2.81 to 192.168.2.180 taken for PPTP sessions


authoritative;
ddns-update-style none;
option wpad-url code 252 = text;

subnet 192.168.2.0 netmask 255.255.255.0
{
    option broadcast-address    192.168.2.255;
deny bootp;
    option domain-name  "apdesign-ami.co.nz";
    option domain-name-servers  192.168.2.253;
    default-lease-time          86400;
    max-lease-time              604800;
    option netbios-dd-server    192.168.2.253;
    option netbios-name-servers 192.168.2.253;
    option netbios-node-type    8;
    option subnet-mask          255.255.255.0;
    range    192.168.2.100 192.168.2.80;
    option routers 192.168.2.1;
    option wpad-url            "http://wpad.apdesign-ami.co.nz/wpad.dat";

}
Output of config show pptpd

pptpd=service
    Interfaces=ppp0,ppp1
    TCPPort=1723
    access=public
    sessions=100
    status=enabled

[Daniel B.]

Hi.

Yep, you found a bug. The problem here is that you've allowed more PPTP sessions than you have available IP in the dynamic range (DHCP). The dynamic DHCP range is reduced by the number of PPTP session allowed (see /etc/e-smith/templates/etc/dhcpd.conf/04TakePPTPDAddresses). The server-manager should check that, and refuse to save the remote setting in such a case

[Allan Pritchard]

Thanks Jadar, that seem to have fixed the issue. I didn't look at the remote access section, it was suppose to be 10 but I guess a slip of an extra 0. It must have been like that for the last 12 months as we have only just started using the SME to issue DHCP leases when out router decided to die.

cat /etc/dhcpd.conf
#------------------------------------------------------------
#              !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at http://www.contribs.org/development/
#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------


# Addresses from 192.168.2.161 to 192.168.2.180 taken for PPTP sessions


authoritative;
ddns-update-style none;
option wpad-url code 252 = text;

subnet 192.168.2.0 netmask 255.255.255.0
{
    option broadcast-address    192.168.2.255;
deny bootp;
    option domain-name  "apdesign-ami.co.nz";
    option domain-name-servers  192.168.2.253;
    default-lease-time          86400;
    max-lease-time              604800;
    option netbios-dd-server    192.168.2.253;
    option netbios-name-servers 192.168.2.253;
    option netbios-node-type    8;
    option subnet-mask          255.255.255.0;
    range    192.168.2.100 192.168.2.160;
    option routers 192.168.2.1;
    option wpad-url            "http://wpad.apdesign-ami.co.nz/wpad.dat";


Cheers and thanks for all of your help.

Allan

[Stefano]

Allan, do you really need 100 pptpd sessions? we are talking about 100 concurrent sessions..

[Allan Pritchard]

Hi Daniel B

Should I submit this as a Bug ? that's not something I have done before


Cheers

[Stefano]

Hi Daniel B

Should I submit this as a Bug ? that's not something I have done before


Cheers

you MUST do it

seriously, I think Daniel has already all the infos and can do himself

@Daniel: would you be so kind to file a bug? thank you

[Allan Pritchard]

Hi Stefano

I have been reminded here that we set the PPTP to 100 when our server was used to co-ordinate the emergency response to the earthquake that hit Christchurch nz in 2011 and we had 70 workstations dialing in remotely accessing a communication and incident management database for the volunteer response. The SME server worked perfectly.

I should have set it back to 10. oops

Cheers 

[Stefano]

well..

as a workaround, set it to 10..

you've found a bug, it will be corrected

thank you

[Daniel B.]

Bug opened: http://bugs.contribs.org/show_bug.cgi?id=8298