Dhcpleases: bad name
-
I keep getting these errors in my logs:
dhcpleases: bad name in /var/dhcpd/var/db/dhcpd.leases
I'm fairly sure this is being caused by a TP Link HS110 power outlet I'm using to control my holiday lights outside. The hostname for the outlet is "HS100(US)". I think the parenthesis are causing the problem, but there's no way on this device to change the host name.
Is there a way to get pfSense to ignore this error and keep it from filling my log? Is this error going to cause any other problems in the long run if I just ignore it?
-
Maybe giving it a DHCP Static Mapping using the mac address and give it a name of HS100 might work.
-
Yeah for sure ( ) in a hostname is not a good idea.. Should prob write a nasty gram to them about that. I looked those up - and I might have to pick one up for xmas season lights. I agree with NogBadtheBad static with setting hostname should get rid of the errors.
So there was newer rfc that changed host name restrictions where you could use a number as first character, etc. 1123 I do believe, Im pretty sure your still not suppose to use anything other than numbers, letters and - in the actual hostname.
-
Maybe giving it a DHCP Static Mapping using the mac address and give it a name of HS100 might work.
I gave this a shot last night, and it didn't seem to work. Same error popped up.
-
Yeah for sure ( ) in a hostname is not a good idea.. Should prob write a nasty gram to them about that. I looked those up - and I might have to pick one up for xmas season lights. I agree with NogBadtheBad static with setting hostname should get rid of the errors.
So there was newer rfc that changed host name restrictions where you could use a number as first character, etc. 1123 I do believe, Im pretty sure your still not suppose to use anything other than numbers, letters and - in the actual hostname.
Yeah, I got 2 of them for super cheap over the summer, about $12/each. I haven't seen the host name problem cause any actual routing problems yet. It gets an IP address, and right now the only problem I'm really seeing is the errors in the DHCP logs. I'm just not sure if this will cause any errors in the long run other than that.
-
$12 you got the 110 for 12?? That is freaking cheap!! The 110 does monitoring show you how much juice being used, while the 100 doesn't do monitoring from my understanding..
Was there some rebate or groupon or something. I would for sure pick up a few for that price.
How often do you get the error? What is your dhcp lease time? Other than log spam I don't see how it would cause too much of an issue.
So did you delete the old lease from the leases file.. Doing the static setting and setting specific hostname should remove that issue. I guess I could try and duplicate it with a host, etc..
-
$12 you got the 110 for 12?? That is freaking cheap!! The 110 does monitoring show you how much juice being used, while the 100 doesn't do monitoring from my understanding..
Was there some rebate or groupon or something. I would for sure pick up a few for that price.
How often do you get the error? What is your dhcp lease time? Other than log spam I don't see how it would cause too much of an issue.
So did you delete the old lease from the leases file.. Doing the static setting and setting specific hostname should remove that issue. I guess I could try and duplicate it with a host, etc..
Well, I got them from Amazon on Prime Day. I wasn't even looking for that kind of device, but for that price I couldn't pass up picking them up to experiment with. They make great timers for running holiday lights outside, but haven't really found another use around the house.
I didn't delete the old leases file when I set the static IP for the device. I can try that this evening and see if it'll correct the error. I'm fairly sure it was popping into the log about twice an hour.
-
well what is your lease time? If it was renewing its lease then yeah prob show back up in the lease file.
-
well what is your lease time? If it was renewing its lease then yeah prob show back up in the lease file.
The change to a static reservation with a different host name fixed the problem. I just had to delete the old leases file first to clear out the error. Once the new file was generated, the problem seems to have cleared up.
Thanks for the help everyone!
-
This is exactly what I was looking for, but can someone mention how exactly you went about deleting the dhcpd.leases file? I have opened it in the editor, so should I just clear out the whole file and save it?
I also have a TP Link plug with that same name and it floods the log file with the same error message all the time.
Thanks in advance!
-
you can just delete the whole file if you want. Or delete the leases from the gui..
