Page MenuHomePhabricator

Allow named interfaces
Open, WishlistPublicFEATURE REQUEST

Description

Is there any reason we don't allow named interfaces? (tun-NAME instead of tunNNN) Would make keeping track of a large number of interfaces a lot easier. It's valid in other distributions so I don't see a technical reason.

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close

Event Timeline

mb300sd created this task.Jul 30 2018, 6:38 PM
syncer triaged this task as Wishlist priority.Aug 1 2018, 7:48 AM
mb300sd updated the task description. (Show Details)Aug 2 2018, 6:15 PM

@mb300sd The reason we do not allo arbitrary names is that there's no easy way to find out exact interface type, so we forced them to begin with eth, br, tun etc. so that scripts can find out what it is and filter only compatible interfaces.
Relaxing the requirements to "starts with keyword" like eth-lan or tun-office would be an interesting idea, but I'm afraid only in the long run, since a number of scripts have regexes like eth\d+ hardcoded in them and it will take time to clean up.

pasik added a subscriber: pasik.Oct 1 2018, 9:51 AM