On Wednesday, May 6, 2020 4:41:27 PM MST John M. Harris Jr wrote:
On Wednesday, May 6, 2020 4:10:56 PM MST John M. Harris Jr wrote:
> On Wednesday, May 6, 2020 3:59:32 PM MST Samuel Sieb wrote:
>
>
> > On 5/6/20 3:48 PM, Ed Greshko wrote:
> >
> >
> >
> > > On 2020-05-07 06:19, Samuel Sieb wrote:
> > >
> > >
> > >
> > >> On 5/6/20 3:10 PM, John M. Harris Jr wrote:
> > >>
> > >>
> > >>
> > >>> On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote:
> > >>>
> > >>>
> > >>>
> > >>>> On 5/6/20 2:46 PM, 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..
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> Are you using NetworkManager or something else?
> > >>>> What do you mean they aren't being read? What is
happening or not
> > >>>> happening?
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> I'm using NetworkManager. The interface is present, with the
> > >>> correct
> > >>> name, but didn't get an IP address assigned.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> My ethernet port is called enp0s25, change the following command as
> > >> necessary. Run "nmcli c show enp0s25" to see what
NetworkManager
> > >> knows
> > >> about the connection. See if there's anything missing.
> >
> >
> >
> >
> >
> > >
> > > I would first run just "nmcli c" to see what the name of the
> > > connection
> > > is. The name is often not equal to the device.
> >
> >
> >
> >
> > Thank you, that's a good point, considering I did exactly that to find
> > out mine...
>
>
>
> Useful info, that returned that it is actually managed by NetworkManager,
> as
> "Wired connection 1"..
Looking into this some more, looks like NetworkManager doesn't recognize
that it's associated with an actual device, which I imagine is why it's
not coming up on boot.. I may be horribly wrong, I'm not incredibly
familiar with NetworkManager.
Well, rebooted and now NetworkManager recognizes that it's enp1s0, and it
works without network-scripts installed. Don't know what changed, but I'll
take it.
--
John M. Harris, Jr.
Splentity