On 12/19/22 13:49, Barry wrote:
> On 19 Dec 2022, at 19:50, ToddAndMargo via users
<users(a)lists.fedoraproject.org> wrote:
>
> On 12/19/22 09:57, Barry wrote:
>>>> On 18 Dec 2022, at 21:28, Tom Horsley <horsley1953(a)gmail.com>
wrote:
>>>
>>> On Sun, 18 Dec 2022 21:19:02 +0000
>>> Barry wrote:
>>>
>>>> That like my router config. Except I use systemd-networkd not
networkmanager.
>>>> Its been stable over lots of fedora releases.
>>>
>>> Right up till the release when they decide to eradicate it
>>> because everyone must use NetworkManager :-).
>> I remove network manager years ago and it has not come back in f37.
>> I do see NetworkManager-libnm that is a dep of lots of stuff so that cannot be
removed.
>> But all my interfaces are .network units in /etc/systemd/network
>>>
>>> That's why I gave up and figured out how to beat NetworkManager
>>> into submission sicne I figured I'd be forced to use it in the
>>> not too distant future.
>> No you are not forced to use it.
>> Barry
>
> I have all my network configured in
> /etc/sysconfig/network-scripts/
> which is probably were most of the issue lies
That has been legacy for a while now. And you suspect you are right it is the source of
your trouble.
You need to either use systemd-networkd or native NetworkManager config to replace the
legacy setup. Both support your multi interface setup.
Maybe f37 shipped something that dropped/broke some of the legacy support?
My systems are using a combination of legacy and new configs with no
problems.