| Linux hackers tackle WiFi hassles |
Feb. 07, 2007
 Analysis -- When it comes to troublesome Linux peripherals, WiFi takes the cake. Sparked by the Portland Project's efforts to bring standardization to the Linux desktop, the Linux wireless developer community tackled this problem at its second Linux Wireless Summit last month in London.
The Summit was scheduled as a followup to the January IEEE 802 standards committee meeting, which, among other issues, moved a step closer to making 802.11n a real IEEE standard. As a result of this timing, participants at the Linux WiFi meeting included kernel developers and vendor representatives from Intel, Broadcom, Devicescape, MontaVista, and Nokia.
Once there, according to Stephen Hemminger, Linux Wireless Summit co-coordinator and a Linux software developer at the Linux Foundation, the attendees had a very productive meeting.
Still, it's been slow going in some critical areas of Linux and WiFi, according to John Linville, the Linux wireless software maintainer. In particular, Linville reported that development work is proceeding too slowly on a new 802.11 stack (d80211); and with a new WiFi API (cfg80211), "development is even slower." Hemminger described the cfg80211 as "a good start but there are no user interface tools (the iproute2 equivalent of iwconfig)."
As for d80211, a breakout session addressed its technical issues. Hemminger wrote in his report on the summit that most of its problems "are not specific to the d80211 stack but have existed all along in Linux wireless. The problem is that up to now each device was doing its own different implementation. The d80211 stack currently exposes a 'master' interface which is only used for reconfiguring the internal queuing disciplines. Since the master interface shows up as a device, it can be a potential point of bugs or user confusion so there was discussion on ways to get rid of it prior to acceptance in the main kernel."
There was also a discussion of the d80211 stack's more advanced features that are seeing little use as of yet. In particular, Nokia was interested in QoS (Quality of Service) and WMM (WiFi Multimedia) support, because their existing device uses a proprietary userspace library.
As it is, "D80211 supports WMM based on the IP type of service (TOS) value in the socket API," Hemminger added. This led to a discussion of whether or not existing glibc header files include the right values for WMM/TOS. It was noted that many existing multimedia applications, like Ekiga, Skype, and Google Talk, are not properly setting TOS.
Another breakout session dealt with regulatory concerns. This discussion led the group into facing the dilemma of proprietary hardware and firmware. According to Hemminger, "Hardware vendors license their equipment under FCC section 15 regulations, even though technically pure software devices could be under SDR (Software Defined Radio) regulations. FCC wants all devices to have a 'no trespassing' sign on radio settings but there is no consensus on what that means."
As a result, "the only solution that can get certified in the current regulatory environment is to have a closed source component either in firmware (good), kernel (bad) or userspace (less evil)," Hemminger continued. The reverse-engineered drivers don't have this problem, but the developers were concerned about the legal implications of redistributing them. "There is some concern since FCC has already stopped hackers who modify power levels on access points. Vendors are reluctant to address the SDR issues too directly because of the regulatory impact to existing non-Linux products if there was any problem."
The reason why the FCC takes this position is that the governmental agency doesn't want it to be easy for users to tamper with radio settings or power levels. Thus, the only WiFi solution that can be certified must have a closed source component. Thus, as distasteful as it is to some free software distributors, legal support for WiFi on Linux will often have to incorporate proprietary elements in one way or another.
Coming out of the meeting, the developers committed to make experimental wireless tarball (and driver) packages available; move faster on the new cfg80211 API; and gain a more complete understanding of the regulatory WiFi situation.
The next Linux Wireless Summit will be this fall, most likely in October, on either the U.S. East Coast or in Israel.
-- Steven J. Vaughan-Nichols
Do you have comments on this story?
Talkback here
NOTE: Please post your comments regarding our articles using the above link. Be sure to use this article's title as the "Subject" in your posts. Before you create a new thread, please check to see if a discussion thread is already running on the article you plan to comment on. Thanks!
Related Stories:
(Click here for further information)
|
|
|
Approaching the Linux Desktop
The purpose of this paper is to help organizations evaluate the Linux desktop against their own enterprise needs and discover what benefits the Linux desktop might bring to their organizations.
Migrating To Linux: Application Challenges and Solutions
Several solutions exist to help organizations migrate in an orderly fashion from Windows to Linux desktops. This paper establishes the characteristics of an ideal cross-platform solution and reviews these alternatives in light of this ideal standard. The paper takes a closer look at the pros and cons of various solutions and outlines the business benefits that can be achieved.
Linux Advantages: Publicly Available Information on Linux Software
This paper offers a brief summary of readily-available Linux information to help businesses sort out this widely misunderstood operating system.
Top 5 Strategies for Managing Linux
Despite continuous evolution in the manageability of Linux, a 2006 survey cited manageability concerns as a top reason why organizations are hesitating to adopt Linux. Levanta believes Linux can be as manageable, if not more so, than other operating systems by following key strategies. These strategic recommendations were developed from experiences in numerous customer environments, both large and small.
Why Choose Novell for Linux?
This paper outlines the benefits of switching to the Linux platform and choosing Novell as a high-performance, enterprise solution.
Enterprise Linux Selection Guide
Considering moving your enterprise to the Linux operating system? Since there are so many similar versions, choosing the right one can be tough. This paper offers a clear process to help you make an informed decision and get the features, support, and cost that are right for your business and technical needs.
Overcoming Challenges in Managing Linux
Levanta has created a new administration model with innovative technology that breaks down the barriers to making the most of Linux systems. This paper will provide an in-depth look at the workings of Levanta’s product, the first Linux appliance of its kind.
SUSE Linux Enterprise 10 for Retail Businesses
Discover why major retailers have switched to SUSE Linux Enterprise Desktop in the back office. SUSE Linux Enterprise Desktop 10 is a low-cost desktop that offers a complete set of productivity applications and interoperates seamlessly with the other Windows, Macintosh and UNIX desktops in your store.
Moving to a Linux Desktop
Migrating from Windows to Linux on the desktop can be a substantial undertaking because it has the potential for touching -- and perhaps disrupting -- every user in your organization. Unlike a data center (server and infrastructure) migration that is largely transparent to users, the cultural and administrative transitions and environment readiness required to support a Linux desktop migration are extensive.
Seven Good Reasons to Exchange Exchange
This paper describes seven compelling reasons why you should switch from Exchange to Scalix.
|
|
|
|
|
news feed
