Requirement to customize Linux Network Interface naming Convention

[Greg KH]

On Wed, Aug 05, 2015 at 08:09:59PM +0530, Akash Bhatnagar wrote:
> Hi Greg,
> 
> Thanks for a quick reply, "We" means me and my manager :)
> 
> In our company we provide HTTP based View to  User with naming conventions of
> interfaces in these formats.
> This is done and stored via higher layer applications in Databases and a lower
> application (X) will make interfaces at Linux Level accordingly.

I don't understand what this means, and how it relates to network names.

> Thus, we need to maintain a mapping of names, of what user have given with
> what is created. This mapping is available to only X and not to other Linux
> daemons (like dhcpd etc). Right now, all daemons need some tweaking in order to
> fetch the mappings from X.
> 
> Hence, there comes requirement to store all the mapping somehow inside kernel
> so that every daemon can easily accessible Interface related information via
> ioctls.

Don't use the kernel as a database for something it was not meant to be.
Again, network names should not "mean" anything, I suggest you revisit
your "requirements".

good luck,

greg k-h