Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Apr 2004 09:13:40 +0200
From:      Milan Obuch <milan.obuch@bluegrass.sk>
To:        freebsd-net@freebsd.org
Subject:   Re: what is the story on if_index allocation ?
Message-ID:  <200404210913.40513.milan.obuch@bluegrass.sk>
In-Reply-To: <20040420235858.B47612@xorpc.icir.org>
References:  <20040419110912.A71274@xorpc.icir.org> <40861A71.1020502@he.iki.fi> <20040420235858.B47612@xorpc.icir.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 21 April 2004 08:58, Luigi Rizzo wrote:
> On Wed, Apr 21, 2004 at 09:53:37AM +0300, Petri Helenius wrote:
> ...
>
> > Relevant quote from the RFC:
>
> a very appropriate one indeed, which seems to substantiate my point.
>
> >    interfaces that might be added dynamically.  The exact meaning of a
> >    "different" interface is hard to define, and there will be gray
> >    areas.  Any firm definition in this document would likely turn out to
> >    be inadequate.  Instead, implementors must choose what it means in
> >    their particular situation, subject to the following rules:
>
> so if there are gray areas in defining 'different' the same applies
> to defining 'same' :)
>
> cheers
> luigi
>

I would say the easiest way is to take any new interface as 'different' in 
relation to any once existed but deleted in past interface and let the 
management station define what does it mean to be 'the same' interface.
We would have sparsely allocated ifindex values after some interface 
creation/deletion, which is not a big issue to me.
I would not think there is one-to-one mapping even for one network management 
solution, it depends on actual needs.
Regards,
Milan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404210913.40513.milan.obuch>