Date: Tue, 6 May 2003 08:41:40 -0700 From: Wes Peters <wes@softweyr.com> To: Harti Brandt <brandt@fokus.fraunhofer.de> Cc: Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: Howto rename an interface Message-ID: <200305060841.40502.wes@softweyr.com> In-Reply-To: <20030505114756.K53365@beagle.fokus.fraunhofer.de> References: <_MzYgD.A.O9P._h8s-@coal.sentex.ca> <200305042117.39042.wes@softweyr.com> <20030505114756.K53365@beagle.fokus.fraunhofer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 05 May 2003 02:49, Harti Brandt wrote:
> On Sun, 4 May 2003, Wes Peters wrote:
>
> >On Sunday 04 May 2003 11:18, Jeremy Chadwick wrote:
>
> > All of the system startups need to refer to these ports by function,
> > not by some silly number assigned as a side effect of the PCI bus
> > probing order.
> >
> > This almost begs for some simple alias that can be programmatically
> > (or via a command line utility) added to the interface so the
> > association with the device type isn't lost. That bears some
> > thought. An interface label, as it were...
>
> Perhaps an if_alias field in struct ifnet, setable via ifconfig? This
> would just nicely map to the alias name field in the SNMP interface
> MIB.
That's what I was thinking, but that's just the beginning of the project.
The next step is to make references to the alias, i.e. from ifconfig,
ipfw, ipfilter, etc. recognize the alias or label as well as the device
name. I'll ask the boss if I can do this on St. Bernard's ticket. ;^)
--
Where am I, and what am I doing in this handbasket?
Wes Peters wes@softweyr.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305060841.40502.wes>