There have been some discussion lately on the VLAN list about what naming convention should be followed for the VLAN interfaces. The only obvious thing is that no single method suits everyone. Some valid ideas for vlan 5 on eth0 are: eth0.5, vlan5, vlan0005, eth0:5 and so on. One solution to this is to allow the user to explicitly set the device name upon creation. The code won't be hard to do, but I'm a little concerned about the consequences...imagine someone sending you a debugging output that has eth0:5 really being VLAN 4 on eth1 (not that you'd be able to tell that...) For the power user, though, naming one vlan mkting, another sales, etc, might be considered useful... So, the question is, has this been discussed before for other virtual interfaces? Does it seem like a useful feature to allow users to explicitly set the device name? If I allow them to set their VLAN name as they like, how about ethernet and other devices too? Thanks, Ben -- Ben Greear ([EMAIL PROTECTED]) http://www.candelatech.com Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL) http://scry.wanfear.com http://scry.wanfear.com/~greear - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
