Can you cheat and just set the lease expiration to be measured in seconds?
I suspect that you can have different lease times, so if you can
discriminate between first state and second state systems, you can provide
more reasonable lease durations once the systems are stage two...
_
Am 06.06.2018 um 10:36 schrieb Roy Marples:
> On 06/06/2018 09:14, Oliver Freyermuth wrote:
>> I finally managed to test this in my testing setup - it works perfectly fine!
>
> Awesome :D
>
>> Could you let me know once it's integrated upstream?
>
> I *am* the upstream for dhcpcd :)
> It will be
On 06/06/2018 09:14, Oliver Freyermuth wrote:
I finally managed to test this in my testing setup - it works perfectly fine!
Awesome :D
Could you let me know once it's integrated upstream?
I *am* the upstream for dhcpcd :)
It will be in the next dhcpcd release for sure.
I plan to open issu
Dear Roy,
Am 05.06.2018 um 13:34 schrieb Roy Marples:
> On 04/06/2018 11:49, Roy Marples wrote:
>> These problems are very nicely solved with RFC 6355 which adds DUID-UUID
>> where UUID is taken from the hosts firmware. The UUID can then be displayed
>> on the node alongside the MAC address for
>
> Alternatively:
> Does somebody know of a clean way to administratively expire a lease handed
> out by dnsmasq?
> Then deployment tooling could forcefully expire an old lease when
> reinstalling a node, and after the final reboot in the installed OS.
>
> Right now, I only know one coul
On 04/06/2018 11:49, Roy Marples wrote:
These problems are very nicely solved with RFC 6355 which adds DUID-UUID
where UUID is taken from the hosts firmware. The UUID can then be
displayed on the node alongside the MAC address for provisioning.
https://tools.ietf.org/html/rfc6355
The downside
Am 04.06.2018 um 23:27 schrieb Roy Marples:
> On 25/05/2018 13:07, Oliver Freyermuth wrote:
>> I fear the following is a design issue of DHCPv6, but I wonder if there's a
>> way to overcome it with dnsmasq...
>>
>> When automatically deploying machines via PXE / network installer, there's
>> usua
On 25/05/2018 13:07, Oliver Freyermuth wrote:
I fear the following is a design issue of DHCPv6, but I wonder if there's a way
to overcome it with dnsmasq...
When automatically deploying machines via PXE / network installer, there's
usually first a DHCPv6 client running in the installer,
and af
Am 04.06.2018 um 18:46 schrieb wkitt...@gmail.com:
> On 06/04/2018 07:36 AM, Oliver Freyermuth wrote:
>> Right now, I only know one could:
>> - Stop dnsmasq.
>> - Purge the lease from the leases-file.
>> - Restart dnsmasq.
>
>
> i think the process is:
>
> rewrite the leases file as needed
>
On 06/04/2018 07:36 AM, Oliver Freyermuth wrote:
Right now, I only know one could:
- Stop dnsmasq.
- Purge the lease from the leases-file.
- Restart dnsmasq.
i think the process is:
rewrite the leases file as needed
HUP dnsmasq
but i'm not positive... if not HUB, maybe one of the other s
Am 04.06.2018 um 12:49 schrieb Roy Marples:
> On 03/06/2018 22:20, Simon Kelley wrote:
>> I agree that this is an annoying problem. In DHCPv6 even determining the
>> MAC address of a client is a slightly dodgy operation - there are
>> circumstances where it's not possible. That notwithstanding, dns
On 03/06/2018 22:20, Simon Kelley wrote:
I agree that this is an annoying problem. In DHCPv6 even determining the
MAC address of a client is a slightly dodgy operation - there are
circumstances where it's not possible. That notwithstanding, dnsmasq
does it's best, and allows you to configure an a
Am 03.06.2018 um 23:20 schrieb Simon Kelley:
> I agree that this is an annoying problem. In DHCPv6 even determining the
> MAC address of a client is a slightly dodgy operation - there are
> circumstances where it's not possible. That notwithstanding, dnsmasq
> does it's best, and allows you to conf
There is an extension for DHCPv6 to send client's MAC address as DHCP
option 79. And in case there is no DHCPv6 relay and packets comes from
ethernet, you can read MAC address directly from ethernet frame which
contains that UDP (DHCPv6) packet. In other cases MAC address is really
not available, b
I agree that this is an annoying problem. In DHCPv6 even determining the
MAC address of a client is a slightly dodgy operation - there are
circumstances where it's not possible. That notwithstanding, dnsmasq
does it's best, and allows you to configure an address to allocated by
MAC address.
The pr
Am 25.05.2018 um 17:23 schrieb P W:
> On Fri, May 25, 2018 at 03:34:08PM +0200, Oliver Freyermuth wrote:
>> Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
On 25 May 2018, at 13:07, Oliver Freyermuth wrote:
Dear dnsmasqers,
I fear the following is a design issue of
On Fri, May 25, 2018 at 03:34:08PM +0200, Oliver Freyermuth wrote:
> Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
> >> On 25 May 2018, at 13:07, Oliver Freyermuth wrote:
> >>
> >> Dear dnsmasqers,
> >>
> >> I fear the following is a design issue of DHCPv6, but I wonder if there's
> >> a
Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
>
>
>> On 25 May 2018, at 13:07, Oliver Freyermuth
>> wrote:
>>
>> Dear dnsmasqers,
>>
>> I fear the following is a design issue of DHCPv6, but I wonder if there's a
>> way to overcome it with dnsmasq...
>
>
> Hi Oliver,
>
> I’ve a sim
> On 25 May 2018, at 13:07, Oliver Freyermuth
> wrote:
>
> Dear dnsmasqers,
>
> I fear the following is a design issue of DHCPv6, but I wonder if there's a
> way to overcome it with dnsmasq...
Hi Oliver,
I’ve a similar/same problem when rebooting some QNAP NAS boxen, first
boot/introduct
On Friday 25 May 2018 14:07:34 Oliver Freyermuth wrote:
> Dear dnsmasqers,
>
> I fear the following is a design issue of DHCPv6, but I wonder if there's a
> way to overcome it with dnsmasq...
>
> When automatically deploying machines via PXE / network installer, there's
> usually first a DHCPv
Dear dnsmasqers,
I fear the following is a design issue of DHCPv6, but I wonder if there's a way
to overcome it with dnsmasq...
When automatically deploying machines via PXE / network installer, there's
usually first a DHCPv6 client running in the installer,
and afterwards (when the machine is
21 matches
Mail list logo
