[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: No networking after resume from suspend



On Fri 23 Apr 2021 at 13:23:31 (-0400), Cindy Sue Causey wrote:
> 
> All of the adapters that come as a single item have worked great. You
> just have to track down the new identifier, e.g. one of mine is
> "enx00909e9dd1ee". That long value goes wherever one normally types in
> eth0, enp1s0, eno1, etc.
> 
> Dmesg often reports that value. I grep /var/log/kern* for the word
> "renamed" because that's what I always remember first. Except that
> then there's having to open kern.log in a text editor occasionally so
> yeah, dmesg rocks if one can remember to go that route.
> 
> Grep works with dmesg, too. I just tested it. Only one line to read as
> output. Very cognitively friendly! :)

That seems like a lot of typing. You should be able to read your
interface name with 5 keystrokes:

$ ip a

and l(ink) will work in place of a(ddress).

OTOH my startup files set Mywiredifname for scripts to use, where:

Mywiredifname=$(ip -o link show | sed -e '/^[0-9]\+: [^e]/d;s/[0-9]\+: \([^:]\+\): .*/\1/;q')

$ echo $Mywiredifname 
enp3s0
$ 

(My days of running multiple ethernet cards are long gone,
so sed will quit after one match.)

Cheers,
David.


Reply to: