DHCP Server Not handing out Leases

Hi,XG version?
ian

Hi rfcat_vk

SFVH (SFOS 19.0.1 MR-1-Build365)

Thank you, hardware device? Sounds like cable connector issue or something similar.

ian

This is a intel i7 with a intel board  self build that I have used running pfSense for somewhat over 3 years.

Never had any issues. might it be a network card compatibility issue?

The onboard NIC is used for WAN and then I had a RealTek PCIe GbE card for the LAN..

I have no idea if it might be a compatibility issue with the RealTek nic.

That's what I start to suspect.

All network cables are newly replaced 3 months ago and never had this issue with pfSense.

Realtek are not favoured especially in high load  connections. Check the mtu. Also have you disabled power saving on the board?
ian

Yes, I have disabled power-saving.

Also aware that Realtek isn't favorable for my use case.

Maybe I should just replace the card and get it over with.

Current MTU and MSS on the Realtek.

Yes, I have disabled power-saving.

Also aware that Realtek isn't favorable for my use case.

Maybe I should just replace the card and get it over with.

Current MTU and MSS on the Realtek.

that looks good. So maybe the card is going into power saving mode?

Ian

rfcat_vk, how would I determine that?

I can't test it now but your dynamic IP lease range is outside your static leases - try to set the End IP to 192.168.1.25 and test it again.

Hi Thomas.

Should I perhaps extend the DHCP range as follow 192.168.1.10 - 192.168.1.253?

You can expand it to 192.168.1.240 for example to reserve the last IPs for static IP mapping directly on a device (without DHCP reservation)

I would rather extend the DHCP range and deal with IP conflicts at this very moment before some of the crucial services goes down.

Let me test this and see if it would make a difference.

That's the reason why I said to extend it to this value (as an example)  before the whole subnet is used in the DHCP lease range - only you know your network best ;)

Hi,

on the XG the static range has to be outside the DHCP dynamic range otherwise you end up with errors.

Ian