Slashdot Mirror

ntropic asks: "I/ve recently bought a Belkin 802.11G USB adapter and was dismayed to find, after a few hours of struggling with it, that there seems to be no one who has managed to get it working under Linux. During the search for clues, it seemed that sum total of Linux support for wireless networking are the linux-wlan project, and the linuxant wrappers for Windows drivers. The former seems to support only Prism chipsets while the latter is a commercial solution, albeit quite an inexpensive one. Is that all, or are there better sources for wireless networking support?"

lasindi writes "Whenever I install Linux, I have trouble with the modem (unfortunately I'm stuck on dial-up). On the first installation, I found out it was a Winmodem and when I tried the solutions and drivers offered by linmodems.org, it still wouldn't work. I finally got an Intel PCI modem, but Intel only provides drivers that work on the 2.4 kernel. I have also have a Conexant modem lying around, but I found out that the only drivers that work for it are provided by Linuxant. These drivers, however, cost money (unless you want to crawl along at 14.4 Kbps for free) and are closed-source. I've found that, although I have five modems, I can't run any of them at full speed under the 2.6 kernel. I would like to know how common such problems are and how Slashdotters have gotten around them."

Alex Moskalyuk writes "Remember the Best Buy commercial where a puppet asks a woman for a laptop computer, and upon hearing that it's a 'wireless' laptop, starts imagining his life free of strings and limitations? That guy doesn't know it yet, but soon the harsh reality will kick in, ironically kicking him off the wireless network periodically if he uses Microsoft Windows Wireless Zero Configuration or if he wants to run Linux on a laptop with WiFi card that doesn't support Linux. This book, however, is not just about getting your Linux laptop onto the wireless network. Granted, WiFi plays a big role in today's business and personal networks, and three chapters are dedicated to exactly that purpose, but behind that wireless adjective we have a variety of technologies." Read on for the rest of Alex's review of Linux Unwired, from O'Reilly. Linux Unwired: A Complete Guide to Wireless Configuration author Roger Weeks, Edd Dumbill, Brian Jepson pages 300 publisher OReilly rating 8 reviewer Alex Moskalyuk ISBN 0596005830 summary Complete guide to wireless configuration on Linux

Infrared, Bluetooth, 802.11 (in current a, b and g offerings, 802.11i is also being discussed), wireless access points friendly to Linux, United States commercial cellular networks and GPS systems are all covered in a single title that surprisingly fits all of this information into 284 pages. All the chapters can be subdivided into two large parts - familiarizing yourself with the technology (the primer on GPS is pretty good) and running Linux on it (with code and shell command samples and lots of URLs).

Introduction

The authors start up with introduction to wireless, intended for Linux geeks who are not quite up to speed on radio technologies. The concepts of waves, spectrum and radio wave behavior are explained, so later the reader can explain what a retracted radio wave is. Then the first chapter moves on to explain antenna behavior, wireless infrastructure modes and some common problem, like a hidden node in ad-hoc infrastructure. The chapter is well-written, and you're not expected to have an advanced radio degree or ARRL membership to understand the terms.

WiFi cards

Chapters 2, 3 and 4 deal with connecting a Linux desktop or notebook to a wireless 802.11 network. The first issue is that of chipsets used in the wireless card, and even though enough research has been done already, authors discuss different quirks relevant to Intersil Prism, Lucent WavelLan/Orinoco, Aironet/Cisco, Symbol, Atmel, Atheros and Broadcom chipsets. We need to discuss chipsets instead of discussing the actual wireless cards, since some hardware may be shipped under the same brand name with different internals. "A good case in point: the D-Link DWL-650. This radio card initially shipped with a Prism II chipset and was very popular, because it worked on a Linux box. However, D-Link changed chipsets when it released the DWL-650 Version 2, choosing the ADMtek chipset. It is very difficult to tell from the packaging which version of the DWL-650 you are purchasing".

The chapters are done in traditional walk-through mode. They are not HOWTOs or compendia of reference information, available from the manufacturer's Web sites. The authors made an effort to ensure the reader is capable of starting up a wireless connection on Linux box, knowing nothing about it while learning important technology in the process. Certain wireless drivers need to be compiled into Linux kernel, so the task is not for the meek, but with detailed explanation, plenty of URLs and nice fonts and paragraph formatting O'Reilly Publishing uses to differentiate between the text, commands entered at the shell, and URLs, the book is easy to read.

Chapter 3 (available in PDF) teaches the reader how to connect to existing wireless network once the wireless card has been recognized by the system and proven functional. By the time the book hit the stores it was already a bit out of date, since the very first hotspot operator, Cometa Networks, shut down in May 2004. Chapter 4 discusses wireless security, touching WEP settings, a $20 Linuxant utility allowing the user to implement WiFi Protected Access, as well as authentication utilities wpa_supplicant and XSupplicant.

WiFi access points

The issue of WiFi access points is not trivial either, as many vendors out there will ship the product with a Windows app being the only way to set it up. However, for the access point setups that are Web-based, a browser in Linux will do the job. The most Linux-friendly access point include Linksys, Netgear, D-Link, Cisco, SMC, EnGenius, Belkin, US Robotics, Microsoft and ActionTec. Again, harsh reality kicked in between the time the book was written and went to press, and it's sad to see yet another Linux-friendly access point vendor quitting the market.

Not satisfied with commercial offerings out there? Chapter 6 takes the reader into the task of building your own access point. Don't forget that an access point doesn't need to be a compact portable - your old 486 with Linux on it and a wireless card connected to it might serve the purpose. Unfortunately, after all the hardware is bought and assembled, the final product might still cost you the quadruple (in case you go with smaller form-factor motherboards and CompactFlash cards for software storage), so consider this more as a geek project, not a viable solution. The authors use LinuxAP distribution for this task.

16 pages are dedicated to hacking Linksys WRT54G access point with Sveasoft, described as disruptive technology by Robert X. Cringely. The authors also take a brief look at Wifi-box and OpenWRT.

Other wireless technologies

Bluetooth, Infrared, cellular and GPS chapters follow the same chapter plan - first the basics of the technology and simple use case scenarios of what you might use it for, then the hardware needed to implement the wireless technology, available Linux software to do the jobs, accompanied with the list of shell commands to successfully talk to a wireless product, and after that typical applications of the working link.

The authors tested various wireless data plans in the United States, although this data, once again, is constantly changing as the operators buy one another and introduce new data plans. The winner of the quality and the fastest download tests, by the way, was a Motorola v120e phone on Verizon Wireless network. In upload speed tests a Merlin C201 PCMCIA card on Sprint PCS network won. T-Mobile also offers a PCMCIA card for its GPRS network, so the authors install and run it under Linux in Chapter 9.

The last chapter discusses using Linux computers with GPS devices and open-source GPSdrive project for reading GPS data.

The book

For those just venturing into the wireless world, the book would be useful. All the information provided on WiFi connectivity can perhaps be googled and found in various HOWTOs. With wireless operators, GPS systems and Infrared connection one would have to rely on enthusiast sites and newsgroups. Having such informative title that covers all of the technologies would be very useful to a Linux enthusiast.

With that, the book can be quite overwhelming, although it's probably not intended to be read from page 1 to the end. There's usually more than one correct way to do things in Linux, and for each successful project another competitor appears on SourceForge the next day. I like the authors' approach of dedicating most of the chapter space to one, leading, Linux package that seems to be dominant in the field, and then briefly mentioning the others. A notable omission is Intel's Centrino drivers for Linux, as the company is bound to become a leader in the chipset marketplace with 42% of notebooks shipped in 2003 running Centrino chipsets.

But overall the book proved to have a high informational and educational value, not only you follow the steps on setting up wireless technologies on Linux, but you also learn the internals of the technology and why certain things are done that way, but not another.

You can purchase Linux Unwired from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, carefully read the book review guidelines, then visit the submission page.

jon787 writes "An email to LKML about the Linuxant's HSF Modem drivers lying to the kernel about their license has prompted some interesting replies. Lots of talk about how to effectively blacklist these kind of things; a patch is here. One of the more interesting is this one. Linus as always has his $0.02."

Edy52285 writes "An article on News.com talks about how Intel has been, and still is, dragging on releasing their Linux drivers for Centrino. Intel is reluctant to release its drivers as open source since doing so would reveal secrets about their wireless hardware. Linux in currently unable to take advantage of Centrino's wireless networking devices, without, that is, prying $20 from your thin wallet to buy Linuxant's DriverLoader (discussed in an earlier story). Will Swope (Intel's General Manager of Software and Solutions Group) said in an interview said "What I believe will happen is we will end up having a Linux compatibility driver that is not open source at first, then designing future drivers in such a way that they are open source but will not expose intellectual property," Intel seem to be taking its time on releasing the drivers, and even in the article, there is a lack of any commitment on a date or under what conditions the drivers will be released." Also, someone pointed out that it's worth checking out ndiswrapper for the driver.

An anonymous reader writes " Shortly after Linuxant has released their commercial DriverLoader, Pontus Fuchs has made an NDIS wrapper available under the GPL. Since some vendors refuse to release specifications or even a binary Linux-driver for their Wireless LAN cards he has decided to solve it himself by making a kernel module that can load Microsoft-Windows NDIS drivers. ndiswrapper has been tested with some BroadCom miniPCI cards and it seems to work on some laptops . With some more work it should be possible to support more cards. Hopefully this will be the case for the many owners of Linux laptops based on Intel's Centrino technology. Please contact Pontus if you are interested in helping out!"

cRueLio writes "The latest release of Linuxant's DriverLoader can now load Centrino drivers. This is very useful, because Intel has been resisting the release of Linux Centrino drivers. For those of you who don't know, DriverLoader is practically a wrapper for Windows wireless drivers."

sniggly writes "The Inquirer has an article about how Montreal, CA based Linuxant has created a 'compatibility wrapper' allowing standard Windows NDIS 5.0 drivers to work on linux. After pointing to another project allowing windows printer drivers to work on OS/2 the author asks 'Are printer and network card drivers going to become, over time, a commodity with Win32 drivers one day the 'de-facto standard' run via wrappers?"