Continuing the discussion from My Home Fedora32 project:
This is the network interface details in my Fedora32:
networkctl list files under /etc/systemd/network tail -n +1 /etc/systemd/network/*
I hit by this bug regarding the “configuring” of enp1s0 in networkctl output.
Solution to avoid the extended wait time, as per the linked bug is:-
need to modify systemd-networkd-wait-online.service as
In my setup, can I have DHCPServer running for the interface enp1s0 ? Will it serve DHCP offers to clients connected to my OpenWRT a vlan switch?
I just noticed: Fedora 32 has not been released. It has not even gone beta. It is currently under development and is unsupported. You should not be using it unless you are helping test it out to prepare it for release.
Ah, good. So, forums and support channels are meant for supported releases only because the software you are using has been tested (undergone QA). So the community is aware of bugs, features, changes, and so on for them.
If you’re insist on using unreleased/untested versions, these forums are not the right channel for discussion. Your best bet is the QA team. Even there, though, you will probably be asked to use a released version for these experiments instead of rawhide.
Rawhide :: Fedora Docs says:
Rawhide is targeted at advanced users, testers and package maintainers.
As a Rawhide consumer, you should:
Be willing to update on an almost daily basis. Rawhide gets hundreds of updates a day, and applying those updates on a regular basis allows you to more easily isolate when a bug appeared and what package(s) are responsible.
Be willing and able to troubleshoot problems. From time to time there are problems with Rawhide packages, and you will need strong troubleshooting skills and the ability to gather information for bug reports. You need a good understanding of dnf and how to downgrade packages, as well as boot time troubleshooting.
Have time and desire to always be able to learn new interfaces and changes. Rawhide packages stick closely to upstream projects, so interfaces and command-line options are subject to frequent changes.
Be willing to reboot frequently to test new kernel versions and confirm functionality of the boot process. If you can’t reboot often, consider using a stable release instead.
Be willing and able to report bugs to bugzilla as you find them and help maintainers gather information to fix them.
If the above doesn’t match you, you may wish to instead follow the Branched release (depending on the point in the release cycle) or use regular stable Fedora releases.