Why is wireless networking so difficult in Linux?

Hi,

I was just wondering why wireless networking is so hard to set up in
linux.
Wired networking seems to be really easy - most distros just install
and networking works. Why doesn't this happen with wireless in linux?

Just curious!
squelch41

(E-Mail Removed) wrote:
> Hi,
>
> I was just wondering why wireless networking is so hard to set up in
> linux.
> Wired networking seems to be really easy - most distros just install
> and networking works. Why doesn't this happen with wireless in linux?
>
> Just curious!
> squelch41
>

You can thank that to the companies that make the equipment as they do
NOT provide the necessary drivers for their equipment and Linux. If you
are having problems, what equipment do you have (make and model) and
what is it that you are exactly trying to do?

--
MicroSoft's NEW Motto: "Good enough." When you're on top, that's the
only standard that matters.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi,
>
> I was just wondering why wireless networking is so hard to set up in
> linux.
> Wired networking seems to be really easy - most distros just install
> and networking works. Why doesn't this happen with wireless in linux?
>
> Just curious!
> squelch41
>
Wireless networking is not any more difficult in Linux than in other OS's.
(OK, I don't do OSX, but I do Win and Linux.) In both OS's you need to
activate the wireless card, and set it up. (Both with security and which
network that it should connect to.) So, I have no idea why you say it is
more difficult. Perhaps you are not using a new distro. I have set up
wireless with the following disto's with Linksys, Dlink, Oinoco, and Belkin
cards with no problem:

Xandros 4 Pro
Ubuntu 6.06 and 6.10
Suse 10
Mandrake
Knoppix

So, maybe you need to try one of the above.

(E-Mail Removed) hath wroth:

>I was just wondering why wireless networking is so hard to set up in
>linux.

Because if it were easy, it would be no fun.

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

On Fri, 19 Jan 2007 12:36:58 -0800, David <(E-Mail Removed)> wrote:

<snip>
>
>You can thank that to the companies that make the equipment as they do
>NOT provide the necessary drivers for their equipment and Linux. If you
>are having problems, what equipment do you have (make and model) and
>what is it that you are exactly trying to do?

It's not even that, it's that they won't release ANY of the specs. Linux hackers
would write the drivers themselves if they could, but the manufacturers won't
release any specs, and so the coders are relegated to trying to reverse engineer
the hardware which is MUCH harder than just writing a driver.

Johann Beretta <(E-Mail Removed)> hath wroth:

>It's not even that, it's that they won't release ANY of the specs. Linux hackers
>would write the drivers themselves if they could, but the manufacturers won't
>release any specs, and so the coders are relegated to trying to reverse engineer
>the hardware which is MUCH harder than just writing a driver.

Actually, reverse engineering is often *MORE* accurate than using the
published specs. I've been ensnarled in at least 2 debates over
whether to build wireless devices in accordance to the specs, or to
built them to match the goofy hardware de jure which doesn't quite
follow the specs. Lots of fun. It's interesting to note that the
best drivers seem to be the ones that either include company support
(Prism, Atheros), or the limited number of devices that have been
revese engineered (Broadcom).

For what little I know about (which is not every chipset on the
planet). I have clues on the others (Atmel, Intel, Prism, Marvell,
RealTek, Zydas) but prefer to let the Linux experts doing the
complaining. Nice article on the current open source wireless mess:
<http://www.thejemreport.com/mambo/content/view/293/>
Well, maybe not so current. The ar5k Atheros driver is obselete under
Linux.

Broadcom: Doesn't supply any info except under NDA. Does not support
open source. Ships drivers in the form of binary APL's. However, it
has been reverse engineered quite successfully:
http://bcm-specs.sipsolutions.net
http://bcm-v4.sipsolutions.net
http://bcm43xx.berlios.de

Atheros: Generally supports open source drivers for Linux and
FreeBSD.
http://www.atheros.com/news/linux.html



--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

OK - thanks. So it is basically the fact that the drivers are extremely
difficult to find/make.
That would certainly fit with my experience where, under windows,
things are reasonably easy as you just install the manufacturer's
driver, but for linux, you have to hunt around for chipset type, then
try the driver which often doesnt work, etc.

Thanks again,
squelch41


Jeff Liebermann wrote:

> Johann Beretta <(E-Mail Removed)> hath wroth:
>
> >It's not even that, it's that they won't release ANY of the specs. Linux hackers
> >would write the drivers themselves if they could, but the manufacturers won't
> >release any specs, and so the coders are relegated to trying to reverse engineer
> >the hardware which is MUCH harder than just writing a driver.
>
> Actually, reverse engineering is often *MORE* accurate than using the
> published specs. I've been ensnarled in at least 2 debates over
> whether to build wireless devices in accordance to the specs, or to
> built them to match the goofy hardware de jure which doesn't quite
> follow the specs. Lots of fun. It's interesting to note that the
> best drivers seem to be the ones that either include company support
> (Prism, Atheros), or the limited number of devices that have been
> revese engineered (Broadcom).
>
> For what little I know about (which is not every chipset on the
> planet). I have clues on the others (Atmel, Intel, Prism, Marvell,
> RealTek, Zydas) but prefer to let the Linux experts doing the
> complaining. Nice article on the current open source wireless mess:
> <http://www.thejemreport.com/mambo/content/view/293/>
> Well, maybe not so current. The ar5k Atheros driver is obselete under
> Linux.
>
> Broadcom: Doesn't supply any info except under NDA. Does not support
> open source. Ships drivers in the form of binary APL's. However, it
> has been reverse engineered quite successfully:
> http://bcm-specs.sipsolutions.net
> http://bcm-v4.sipsolutions.net
> http://bcm43xx.berlios.de
>
> Atheros: Generally supports open source drivers for Linux and
> FreeBSD.
> http://www.atheros.com/news/linux.html
>
>
>
> --
> Jeff Liebermann (E-Mail Removed)
> 150 Felker St #D http://www.LearnByDestroying.com
> Santa Cruz CA 95060 http://802.11junk.com
> Skype: JeffLiebermann AE6KS 831-336-2558

(E-Mail Removed) wrote:
> OK - thanks. So it is basically the fact that the drivers are extremely
> difficult to find/make.
> That would certainly fit with my experience where, under windows,
> things are reasonably easy as you just install the manufacturer's
> driver, but for linux, you have to hunt around for chipset type, then
> try the driver which often doesnt work, etc.
>
> Thanks again,
> squelch41
>

Well you could just try using NDISwrapper and the native windows driver.

--
MicroSoft's NEW Motto: "Good enough." When you're on top, that's the
only standard that matters.

David wrote:
> (E-Mail Removed) wrote:
>> OK - thanks. So it is basically the fact that the drivers are extremely
>> difficult to find/make.
>> That would certainly fit with my experience where, under windows,
>> things are reasonably easy as you just install the manufacturer's
>> driver, but for linux, you have to hunt around for chipset type, then
>> try the driver which often doesnt work, etc.
>>
>> Thanks again,
>> squelch41
>>
>
> Well you could just try using NDISwrapper and the native windows driver.

The downside of that approach is that no kernel developer will even look at any oops that you have
as long as that Windows binary "taints" your system.

Once you solve the driver problem, and I'm part of the group working on the bcm43xx driver, using
NetworkManager to connect is even easier then Windows. When you try to connect with a new, encrypted
AP, up pops a box asking for your encryption key, which is then stored in your KDE wallet.

Larry

Larry Finger wrote:

> ...I'm part of the group working on the bcm43xx driver...

Could you give me an update on where things are with the bug that causes
it to crash on an AMD64 machine with a gigabyte or more of RAM? Kind of
a hassle to drag out the old PC Card 802.11b adapter when I want to boot
into Linux.