Re: [Madwifi-devel] virtual dev to phy dev parameter mappings
Status: Beta
Brought to you by:
otaku
From: Henrique de M. H. <hm...@de...> - 2005-12-27 20:17:27
|
On Tue, 27 Dec 2005, Paolo wrote: > > For example: wifi0 is the physical device, ath0 and ath1 are two VAPs > > bound to wifi0. Trying to change the channel on either ath0 or ath1 > > results in an error, changing the channel on wifi0 works and > > automatically effects ath0 and ath1. > > hm, technically makes sense, but wouldn't that add even more confusion > to the question what-tools-to-use-on-what-iface-other-than-wireless-tool? Yes. I suggest that the default naming tie the VAP to the phy device, like this for example: PHY: wifi0 (might not need to even exist -- i.e. not in ifconfig list) VAP: wifi0-ath0 VAP: wifi0-ath1... (or whatever separator character other than : we can use, I don't recall the allowed characters in interface names right now) Also, remember that nothing better *depend* on this naming. Such decisions have no more place in the kernel these days, and udev CAN and DOES rename interfaces on new enough kernels. But the better the default naming scheme, the smaller the mess we will cause on people's minds... and userspace must cope with this by supporting ANY valid interface name. Make sure the driver printks a notice when it changes attributes on more than one device because of VAPs, and that should cover it with minimum userland impact. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh |