Assign static IP to dhcp device fails
-
I have an HD Homerun 4k flex device that I have no way to assign it a static IP. It will automatically request an IP from the DHCP server
No matter what I do it refuses to take the static IP I assign it. Based on its mac address I have it set to get the static ip of 192.168.3.13
I see something that says client identifier........but then nowhere is the client identifier visible for viewing (can we use a wild card?). This is becoming the worst tamagachi pet ever. A simple static bind is made as convoluted as possible.
I see reference online to look in var/dhcpd/var/db/dhcpd.lease but I am thinking this is old information as that file has 1 entry in my file and I have 54 current leases.
-
@xokia Can answer my own question wildcard works for client identifier. It took the static assignment. jeeesssshhhh.
-
@xokia said in Assign static IP to dhcp device fails:
No matter what I do it refuses to take the static IP I assign it
You mean you actually saw in the DHCP log that de device REFUSED the IP given to it by pfSense ?
Not proposing a choice between DHCP and Static mode seems already pretty broken to me. Not all networks have DHCP server ...
If you've set up a DHCP Static Mapping like this :
then the device can't refuse it. If it does, open a window, and make it fly towards the outside, as it is not compatible with your network. Don't waste your time with it.
@xokia said in Assign static IP to dhcp device fails:
var/dhcpd/var/db/dhcpd.lease
Wrong file.
It's/var/dhcpd/var/db/dhcpd.leasesThis file is the 'memory' of the DHCP server.
If some previous unknown device connects to the network, the DHCP server will propose a lease from the pool, and write the info in this file.
Even if the DHCP server restarted, or the system (pfSense) rebooted, the next time the device re connects, a 'record' will be found in this file, and the DHCP server will propose the same IP/lease (if not already recycled/used by another device).
If the file /var/dhcpd/var/db/dhcpd.leases is lost, then that's not really an issue neither.@xokia said in Assign static IP to dhcp device fails:
but then nowhere is the client identifier visible for viewing (can we use a wild card?)
Not sure if that info is ever used / usefull. I've seen devices using no ID what so ever, or they send info that's not even RFC compatible.
See the /var/dhcpd/var/db/dhcpd.leases if you want to know what devices send over when doing a DHCP request.... set vendor-class-identifier = "android-dhcp-10"; ....Or have a look on the wire yourself : Diagnostics > Packet Capture
Interface LAN, protocol UDP, View options : high and ports 67 and 68 and Start.
You see the live entire DHCP process communication.Example : go to a windows PC and type
ipconfig /renew -
/var/dhcpd/var/db/dhcpd.leases type-O in my post missed the s
this file was almost empty in mine
@Gertjan said in Assign static IP to dhcp device fails:
You mean you actually saw in the DHCP log that de device REFUSED the IP given to it by pfSense ?
Yes it showed the static mapping AND it showed up in the ARP table. However it refused to take the IP unless MAC address AND client identification is filled out
even though client identification says "optional" its not so optional. When I say refused it was popping up in the DHCP as a dynamic assigned IP (192.168.3.58) instead of the static I assigned (192.168.3.3). I used wilcard * for the client identification and it worked fine.I then changed the client identification to the same value as the mac address and it still seems to work.
