On Mon, May 4, 2020 at 2:20 AM Tom Horsley wrote:
> On Sun, 3 May 2020 14:45:49 -0700
> Samuel Sieb wrote:
>
>> I highly recommend using "nm-connection-editor". It's the official
>> connection editor for NetworkManager. It's quite nice and gives you
>> access to all the settings and connection
On 2020-05-04 08:19, Tom Horsley wrote:
> On Sun, 3 May 2020 14:45:49 -0700
> Samuel Sieb wrote:
>
>> I highly recommend using "nm-connection-editor". It's the official
>> connection editor for NetworkManager. It's quite nice and gives you
>> access to all the settings and connection types.
>
On Sun, 3 May 2020 14:45:49 -0700
Samuel Sieb wrote:
> I highly recommend using "nm-connection-editor". It's the official
> connection editor for NetworkManager. It's quite nice and gives you
> access to all the settings and connection types.
But it gives absolutely zero feedback on why the
On 5/3/20 10:27 AM, Tom Horsley wrote:
I was finally going to try to setup my network using nm
in fedora 32. I figured after 10 years or so all the
bits I use might finally work :-).
I'm pretty sure the bits have been working for many years because I've
been using them.
Here's the commands
On Sun, 3 May 2020 13:27:02 -0400
Tom Horsley wrote:
> But, I've defined a bridge with (seemingly) all the
> same properties as the fedora 31 bridge I created
> with network-scripts, yet my virtual machines using
> bridge networking never get an IP address, as if the
> router dhcp server never
I was finally going to try to setup my network using nm
in fedora 32. I figured after 10 years or so all the
bits I use might finally work :-).
But, I've defined a bridge with (seemingly) all the
same properties as the fedora 31 bridge I created
with network-scripts, yet my virtual machines using
