On 4/22/2020 9:08 AM, William Edwards wrote:
>
>> Op 22 apr. 2020 om 08:41 heeft Olaf Hering het volgende
>> geschreven:
>>
>> Am Tue, 21 Apr 2020 15:58:25 +0200
>> schrieb "William Edwards" :
>>
>>> Ideas are welcome.
>>
>> You did not say how hosts are identified, nor did you say why exactly
>
Hey - that worked! Setting my leases to 12 hrs fixed everything. Heh, I
guess there are some subtleties in interpreting "infinite".
For completeness:
# Old. not working.
# dhcp-host=,192.168.0.150,livingr
oom.internal,infinite
# New, working.
# Diff:
# - 12 hour lease, not infinite
# - Don't eve
Thanks! That makes sense. I actually do dual-boot my living room PC but not
very often and there are only a few configurations. So I can just
statically add their DUID/IAIDs to dhcp-host.
I guess the problem you're referring to is that dhcp-host only supports a
single "id:" option instead of a set
> Op 22 apr. 2020 om 08:41 heeft Olaf Hering het volgende
> geschreven:
>
> Am Tue, 21 Apr 2020 15:58:25 +0200
> schrieb "William Edwards" :
>
>> Ideas are welcome.
>
> You did not say how hosts are identified, nor did you say why exactly
> addresses matter in your setup.
> If it is done bas
Am Tue, 21 Apr 2020 15:58:25 +0200
schrieb "William Edwards" :
> Ideas are welcome.
You did not say how hosts are identified, nor did you say why exactly addresses
matter in your setup.
If it is done based on their MAC addresses, just give each host a name.
host-record=hostname,hostname.${dns_d
