Hello,

sorry for the slow replies.
I mounted mounted my old non booting drive up and just copied everything from /etc/systemd/network/* in my current debian installation.

I think my Issue is fixed now, although I have no Idea what is going on in the files: There is bond0.netdev which defines the Mode to be 802.3ad (apparently called link aggregation).

bond0.network defines Bindcarrier=eno1np0 eno2np1
Then there is eno1np0.network and eno2np1.network which set Bond=bond0 and there is management.network which sets DHCP to false, UseDNS to true and sets my Address Gateway and DNS Server.

It seems that it defines a bonding between the 2 networks, although I would have thought, that both networks also would work together and not bonded.

I just wanted to give a quick update - thank you for all the help.

Best,
Lucienne
Zitat von The Wanderer <[email protected]>:

On 2026-10-24 at 01:30, [email protected] wrote:

On Fri, Oct 23, 2026 at 07:59:45PM +0200,
[email protected] wrote:

When I do dhcpcd on the networks, the addresses become the address
from link-local 1
65.254.0.0/16.

I'm still confused you have dhcp and not dhclient. The former comes
with Debian package isc-dhcp-server, which is priority "optional",
the latter with isc-dhcp-client, which is "important". And I didn't
know the dhcp server can request IP addresses (i.e. playing client).

I'm pretty sure it can't. While you've been writing 'dhcpd' (short for
"DHCP daemon", provided in the package 'isc-dhcp-server') in your
replies in this thread thus far, the OP has consistently (at least from
what I've noticed) been writing 'dhcpcd' (short for "DHCP client
daemon", provided in the package 'dhcpcd').

--
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw



Reply via email to