This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DHCP "no free leases"

Hi

So, i'm having this really frustrating issue that i hope someone inhere will magically make dissapear.. (or well, not magically, but hopefully someone will know what i have done wrong)

my setup is like this (i know, not a beauty, but it should give you an overview of the setup)

So, everything almost works, my pc's on VLAN 2 are getting IP's from DHCP (which works like a charm)

My Pc's on vlan 3 however refuses to get an IP, they have full connectivity when using a static IP on the Guest net though.

My guest interface has the following configuration on the interface and DHCP settings.

But when i look in the DHCP log, this is the result :-(

I simply cannot find the error, since this is a newly created DHCP scope, it is impossible that it should be full, not to mention that there aren't any entries from this network in the DHCP lease table, so i could really use some help here.

All help is much apreciated.

This thread was automatically locked due to age.

0 BarryG over 11 years ago

Hi,

UTM version #?

Anything else weird in the dhcp log?

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 martinta over 11 years ago

Hi Barry

Version is written on the topology :-) it's 9.109-1

I don't see anything else in the log, exept the client on VLAN 3 that won't get an address, here is a bigger output of the log.

only thing that would be of some interest would be the duplicate address, but that should not have anything to do with this issue.

2014:04:08-00:37:21 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:37:26 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:37:30 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:37:38 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:37:55 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:38:27 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:38:32 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:38:41 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:38:58 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:40:03 vpn dhcpd: DHCPREQUEST for 192.168.2.151 from 84:7a:88:25:98:57 via eth0.2
2014:04:08-00:40:03 vpn dhcpd: DHCPACK on 192.168.2.151 to 84:7a:88:25:98:57 via eth0.2
2014:04:08-00:44:37 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:44:41 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:44:45 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:44:52 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:45:08 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:45:41 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:45:46 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:45:53 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:46:09 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:51:46 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:51:51 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:51:56 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:52:03 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:52:20 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:52:53 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:52:57 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:53:06 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:53:22 vpn dhcpd: DHCPDISCOVER from ac:22:0b:17:7a:cb via eth0.3: network 192.168.3.0/24: no free leases
2014:04:08-00:57:42 vpn dhcpd: DHCPREQUEST for 192.168.2.208 from 24:a4:3c:02:55:38 (Stue) via eth0.2
2014:04:08-00:57:42 vpn dhcpd: DHCPACK on 192.168.2.208 to 24:a4:3c:02:55:38 (Stue) via eth0.2
2014:04:08-01:22:03 vpn dhcpd: uid lease 192.168.2.206 for client 00:15:99:eb:0b:77 is duplicate on 192.168.2.0/24
2014:04:08-01:22:03 vpn dhcpd: DHCPREQUEST for 192.168.2.155 from 00:15:99:eb:0b:77 via eth0.2
2014:04:08-01:22:03 vpn dhcpd: DHCPACK on 192.168.2.155 to 00:15:99:eb:0b:77 via eth0.2
Cancel
Vote Up 0 Vote Down

Cancel
0 teched_01 over 11 years ago

Why do you have the "Clients via DHCP relay agent" selected? Do your other DHCP configurations have it enabled?

If disabling that doesn't fix the problem then it is probably worth looking at /var/chroot-dhcps/etc/dhcpd.conf directly.
Cancel
Vote Up 0 Vote Down

Cancel
0 martinta over 11 years ago

Hi teched

I used the original DHCP settings that where created on startup as a template, and this setting where enabled on those settings.

I'll try disabling it when i get back to the firewall later today
Cancel
Vote Up 0 Vote Down

Cancel
0 martinta over 11 years ago

#4

Sir, i owe you a drink ;-) Thank you very much

I removed the relay setting and at the first sight it now works :-)

Now, and open question.

What exacly does the "Clients via DHCP relay agent" setting do?
Cancel
Vote Up 0 Vote Down

Cancel
0 scorpionking over 11 years ago
It's described in the online help... ;-)
Clients via DHCP relay agent: If selected, the DHCP server assigns IP addresses to clients which are not in the network of the attached interface. In this case, the address range defined above has to be inside the network where relayed DHCP requests are forwarded from, and not within the network of the attached interface.
----------
Sophos user, admin and reseller.
Private Setup:

XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)

UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Cancel
Vote Up 0 Vote Down

Cancel
0 martinta over 11 years ago

#7

Ahh, my mistake.. for once, i didn't search before i asked the question :-)

But thank you for the answer. i'm still not sure why i got the error though, wouln't it be irrelevant for the DHCP server aslong as the source IP was in the /24 range of the DHCP scope?

Or du i misunderstand the Online Help material?
Cancel
Vote Up 0 Vote Down

Cancel
0 teched_01 over 11 years ago
Sorry, this was on the back burner for a few days.

In your case you shouldn't need DHCP relay as your UTM has full layer-2 visibility (can see the layer-2 broadcasts) to the relevant networks.

If your smart switch were doing routing for vlans 2 & 3 and another vlan (4?) between it (smart switch) and the UTM then you'd need the switch (router) to relay the relevant DHCP traffic (broadcasts) to the DHCP server.

I haven't done a thorough verification of the following but it looks like it is a bug:

It appears that when enabling the DHCP Relay setting on a network that the UTM is on (layer-2) it creates a dhcpd.conf that results in the "no leases available".

Partial/approximate normal /var/chroot-dhcps/etc/dhcpd.conf from UTM:
group {
  subnet 192.168.0.0 netmask 255.255.255.0 {
    range 192.168.0.101 192.168.2.200;
     option domain-name-servers 192.168.2.100;
    option routers 192.168.0.100;
    option netbios-node-type 1;
    option subnet-mask 255.255.255.0;
    option broadcast-address 192.168.0.255;
    option wireless-security-magic-ip 192.168.0.100;
  }
}

Enabling DHCP Relay adds the following lines when the layer 2 network is on the UTM:
group {
  subnet 192.168.0.0 netmask 255.255.255.0 {}
}

(note no range or relevant options - no range = no leases available)

The configuration appears to generate correctly when the UTM doesn't otherwise know about the network.
Cancel
Vote Up 0 Vote Down

Cancel

DHCP "no free leases"

Submitted a Tech Support Case lately from the Support Portal?