1. 14
  1.  

  2. 7

    If you’re going to rename your interfaces, be meaningful. if1 through if6 gives you no more information than eno1 through eno6.

    Consider:

    • name an outside interface after the ISP it connects to

    • name a point-to-point tunnel after the other side

    • name an internal network internal, or house, or to the name of the switch it talks to

    • name a wifi interface after the area it covers

    The goal is to never look at an interface and wonder what it’s for.

    1. 3

      If you’re going to rename your interfaces, be meaningful. if1 through if6 gives you no more information than eno1 through eno6.

      The alternative the author is moving away from is not eno1 but rather enp2s0 (bus/slot-based) or enx78e7d1ea46da (MAC-based).

      See https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

      That said, yes, you’re right: more meaningful interface names are possible. But they cannot be generated automatically because they require knowledge of your specific network configuration.

      1. 1

        Sure. But if anything, enx78e7d1ea46da style names are an even bigger incentive to rename for semantics – quick, is enx78e7d1ea46da or enx78e7d1ea48da the link to the wifi network?

        1. 1

          On my old router I renamed the interfaces wan0 and lan0. I thought about doing that on this router, but I settled on the port number so I could tell which port the cable was plugged into. (the auto-generated names were like ens33, 34, etc…) but yea, I understand what you’re getting at. I might rename them later. shrug