Thread: Re: [Madwifi-devel] Re: [Madwifi-users] wlanconfig => athconfig
Status: Beta
Brought to you by:
otaku
From: Bell K. <bel...@pe...> - 2005-12-26 16:50:48
|
Hi, I am using madwifi in our embedded systems, usually in AP mode, for AP mode, there is no standard interface defined in wireless tools, any interface is fine to us, as long as it is small... wlanconfig is a utility for net80211, and I think the interface of net80211 is like a standard, many features in madwifi is unsupported by wireless tools, but they are really handy, we can just follow it as is, so the we can use patches from bsd easier. add a lot of iwpriv to wireless tools is not easy to maintain, also there are many old 2.4.1x kernels in embedded system, which can not use large iwpriv tables. on the other hand, desktop system usually run in station mode, and there are many GUI tools and rc scripts rely on wireless tools, I think this can be done with "a default virtual device per real device", so the driver looks the same from wireless tools, no wlanconfig is needed for station mode to work. this is based on my needs, I have to support many embedded systems, maybe desktop users have other priorities? Pavel Roskin wrote: >>Hello, Kel! >> >>On Mon, 2005-12-19 at 21:54 +1000, Kel Modderman wrote: >> >> >> >>>Hi all, >>> >>>dy...@gm... was kind enough to donate some time into rewriting >>>wlanconfig into a new tool named athconfig. athconfig promises to be >>>much easier to use. >>> >>>This will change the way everyone uses madwifi-ng as they know it, so it >>>would be good if a few poeple took a look at >>>http://madwifi.org/ticket/44 and the proposed changes, and either >>>prepare to update quite a bit of the wiki or prepare an argument against >>>these changes ;-) >>> >>> >>I would prefer to have configuration entirely based on wireless tools, >>e.g. >> >>iwpriv wifi0 add_if ath0 >>ifconfig ath0 hw ether 00:11:22:33:44:55 >>iwconfig ath0 mode master >>iwpriv ath0 beacon 1 >> >>and so on. The main interface doesn't need to support any wireless >>extensions other than add_if and del_if private calls. >> >>Only thing that may be missing from wireless tools is the ability to >>return custom lists, so "wlanconfig ath0 list wme" could be harder to >>replace. Still, I think it can be done in a more standard way than it's >>done now. >> >>I have no objections against the change per se, but I think we would >>spend too many efforts on a temporary fix. And let's not forget that >>all users would have to change their setup scripts to accommodate for >>the change. >> >> >> > >Well it would appear that the current wlanconfig is not to everyone's >liking, and changing it to athconfig apparently doesn't solve the real >issue. So, now the problem becomes.... > >Who can make the necessary changes to madwifi for supporting wireless >tools as a replacement for wlanconfig? > >Alex > > > -- Bell Kin System Analyst PEK Inc. Consult & Design TEL:+886-3-5290115 FAX:+886-3-5297445 No.4 Lane 356, Xinxiang St. Hsinchu City 300 Taiwan, ROC |
From: Michael R. <ma...@no...> - 2005-12-27 14:17:45
|
Hi. On Tue, 2005-12-27 at 01:09 +0800, Bell Kin wrote: > for AP mode, there is no standard interface defined in wireless tools, > any interface is fine to us, as long as it is small... Where necessary we could make use of iwpriv ioctls. Even then we could stick with athconfig to provide a "cleaner" (more consistent) way of configuring the interfaces - making it a wrapper around all the wireless tools ioctls. Bye, Mike |