Re: [systemd-devel] Dynamic link-local address not assigned after collision

2025-01-08 Thread Andrei Borzenkov
08.01.2025 01:38, Muggeridge, Matt wrote: It behaves this way when using IPv4LLStartAddress. If the address is in use, it chooses another from the 169.254/16 range. OK, I missed this option. ... What could be done is supporting something like Address=169.254.4.0/24 with the semantic "pic

Re: [systemd-devel] Dynamic link-local address not assigned after collision

2025-01-07 Thread Muggeridge, Matt
> -Original Message- > From: Andrei Borzenkov > Sent: Tuesday, 7 January 2025 4:53 PM > To: Muggeridge, Matt ; systemd- > de...@lists.freedesktop.org > Subject: Re: [systemd-devel] Dynamic link-local address not assigned after > collision > > 07.01.2025 06

Re: [systemd-devel] Dynamic link-local address not assigned after collision

2025-01-06 Thread Andrei Borzenkov
07.01.2025 06:01, Muggeridge, Matt wrote: I have two systems where I need them to assign link-local addresses in a 169.254.4/24 subnet, regardless of any other addresses configured. I'm using a /24 subnet because I have multiple interfaces on the system that require link-local addresses; I was

[systemd-devel] Dynamic link-local address not assigned after collision

2025-01-06 Thread Muggeridge, Matt
I have two systems where I need them to assign link-local addresses in a 169.254.4/24 subnet, regardless of any other addresses configured. I'm using a /24 subnet because I have multiple interfaces on the system that require link-local addresses; I was placing them in their own subnets. >From t