Peter Memishian wrote: > > Maybe concrete examples would be better than any description. How > > about, "being able to give a meaningful vanity name to a network > > interface (e.g., netmanagement0 for an interface dedicated to network > > management, or upstream2 for an ISP-facing interface.)" > >A nit: I doubt anyone would want to type netmanagement0, and I'd prefer to >recommend compact names like netmgt0, netctl0, or netadm0. > >
Sure, but please remember to test long names, anyway. hmmm, mental rewind... I think the question of what names/character set to allow the interface name to be defined from came up earlier. It didn't occur to me then, but you might want to think about restricting an interface name to the character set restrictions that apply to hostnames. From using traceroute, I've seen hostnames for links show up where people have included the interface name for various Ciscos, etc. I imagine people will want to do the same here: be able to name an interface and then have nicname0-hostname.domain in DNS. I know I've included names such as foo-hme0, foo-nf0, in my DNS for Solaris boxes. This might also bring with it useful restrictions on what potentially nasty characters can and cannot be in an interface name, without needing to define your own set. Darren
