<p dir="ltr">Hi Greg,</p>
<p dir="ltr">Thanks for a quick reply, "We" means me and my manager :)</p>
<p dir="ltr">In our company we provide HTTP based View to User with naming conventions of interfaces in these formats.<br>
This is done and stored via higher layer applications in Databases and a lower application (X) will <br>
make interfaces at Linux Level accordingly.</p>
<p dir="ltr">Thus, we need to maintain a mapping of names, of what user have given with <br>
what is created. This mapping is available to only X and not to other Linux<br>
daemons (like dhcpd etc). Right now, all daemons need some tweaking in order to fetch the<br>
mappings from X.</p>
<p dir="ltr">Hence, there comes requirement to store all the mapping somehow inside kernel <br>
so that every daemon can easily accessible Interface related information via ioctls.</p>
<p dir="ltr">Thanks <br>
Akash Bhatnagar<br>
▶ Show quoted text<br>
On 5 Aug 2015 09:34, "Greg KH" <<a href="mailto:greg@kroah.com">greg@kroah.com</a>> wrote:<br>
><br>
> On Wed, Aug 05, 2015 at 09:24:41AM +0530, Akash Bhatnagar wrote:<br>
> > Hi,<br>
> ><br>
> > We have a requirement to tweak the Linux Network Interface Naming<br>
> > conventions so that, it can support names of interfaces with "/" character.<br>
><br>
> Who is "we"?<br>
><br>
> And why do you want such a thing?<br>
><br>
> > For example, ip tuntap add dev fe/1/1 mode tap<br>
> ><br>
> > With iproute2 it simply shows error as INVALID Argument. What are the<br>
> > changes we supposed to do inside Kernel and iproute2 package?<br>
><br>
> Lots, good luck :)<br>
><br>
> But first, push back, you should never care what the network interface<br>
> name is, that never matters.<br>
><br>
> greg k-h<br>
</p>