On Wednesday, May 6, 2020 3:21:46 PM MST Samuel Sieb wrote:
On 5/6/20 3:15 PM, John M. Harris Jr wrote:
> On Wednesday, May 6, 2020 3:01:28 PM MST Tom Horsley wrote:
>
>> On Wed, 06 May 2020 14:46:35 -0700
>> John M. Harris Jr wrote:
>>
>>> Anyone know if this is just broken now, and what the workaround is if
>>> so?
>>> I'm fine manually setting it on boot for now, but this is causing a
>>> lot
>>> of issues..
>>
>>
>>
>> Probably don't have network-scripts installed. Ever since about fedora
>> 29 I think they haven't shipped network-scripts by default, you have
>> to fetch them via:
>>
>>
>>
>> dnf install network-scripts
>>
>>
>>
>> (which can be tricky if you have no network :-).
>>
>>
>>
>> I finally gave up and after a monster struggle got my networking
>> functioning with just NetworkManager when I installed fedora 32.
>
>
> While this did solve it, I wonder why it was working in F31, but stopped
> in F32, if that was the issue. There should probably be a warning upon
> upgrade, or something like that, because using
> /etc/sysconfig/network-scripts is not at all uncommon..
You installed "network-scripts" and that made it work? That package is
deprecated and going away soon. You should make sure it works without that.
Well, that's just more confusing as it turns out.. I configured this one with
the GUI in Anaconda, but this is where it put the connection info. The only
thing I've got in /etc/NetworkManager/system-connections/ is a VPN
configuration. I installed this system as F31 via KDE Spin's installer, if
that makes a difference.
--
John M. Harris, Jr.
Splentity