So I’m working on a server from home.

I do a cat /sys/class/net/eth0/operstate and it says unknown despite the interface being obviously up, since I’m SSH’ing into the box.

I try to explicitely set the interface up to force the status to say up with ip link set eth0 up. No joy, still unknown.

Hmm… maybe I should bring it down and back up.

So I do ip link set eth0 down and… I drive 15 miles to work to do the corresponding ip link set eth0 up

50 years using Unix and I’m still doing this… 😥

  • ExtremeDullardOP
    link
    fedilink
    arrow-up
    20
    ·
    3 days ago

    In my defense, I just installed the machine. I was configuring it from home after hours.

    • DasFaultier@sh.itjust.works
      link
      fedilink
      arrow-up
      22
      ·
      3 days ago

      after hours

      I’ve configured PAM to not let me login remotely after hours, because I just know that someday I’ll want to fix “just this tiny thing” and I’ll break production because I’m too tired. I clearly need protection from myself, and this is one slice in Dr.Reasons’s Swiss cheese model.

      Don’t let the people drag you down, this happens to all of us.