Jump to content

chamabreu

Validating
  • Posts

    1
  • Joined

  • Last visited

  1. Hi, i have a Problem, where the Network is not coming up. What i have done: Installed Arbmian Bullseye CLI on SD Card Booted it on Odroid M1, update and updgrade system - Reboot Until then, the NetworkManager is active and works Installed OMV through armbian-config OMV kills all NetworkManager stuff, and enables systemd-networkd and it does that as i can see correct, with netplan etc... After reboot, the boot hangs 2 Minutes in "A start job is running for Wait for Network to be Configured" and finally boots - without IP Boot finished - login and try to find the error: networkctl shows eth0 is off and unmanaged systemctl status systemd-networkd has no errors and logs: Starting Network Service Enumeration Complete Started Network Service systemctl status systemd-udevd is active and running, but got errors: Starting Rule-Based Manager for Device Events and Files Started Rule-Bas... Using default interface naming scheme 'v247' eht0: Failed to query device driver: Device or resource busy Also, my netplan configuration searches the eth0 by MACaddress: cat /etc/netplan/20-openmediavault-eth0.yaml network: ethernets: eth0: match: macaddress: "some macadress" accept-ra: true dhcp4: true dhcp6: true If i remove the match by macaddress or change it to name: eth0, the reboot works and it gets an IP and network is running. So i observed the macaddress, and networkctl status eth0 shows another macaddress each reboot. Why? I can't help myself, after 2 Days of searching the whole internet, nothing seems to be close to my problem. Someone ideas? Greetings
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines