Group: comp.os.linux.networking
From: Shadow_7
Date: Thursday, March 27, 2008 10:16 AM
Subject: Re: Wireless connection woes.

> a) First configure the channel manually.
> b) Set the mode to "ad-hoc"
> c) Try to connect to the access point again.

I don't know if it's the driver or if it's dhcpcd / dhclient3. There's a
number of sites where I have to set the mode, rate, essid, key, and channel
before dhclient3 works for me. Using a BCM4318 chipset and ndiswrapper.
Although there are other locations where dhclient3 works out of the box,
no prep work involved. So it may not be anything linux related. Just (as
windows would say) lazy admins that never upgraded.

But once connected it works flawlessly and much faster than that redmond
OS. In the sense that there's no needless netbeui packets, windows update
packets, and whatever worm/virus of the month spewing packets out to where
ever. Just watch the internal interface with tcpdump on a linux router
connected to the internet and you'll see what I mean. Only connected to a
linux machine and all's quiet on the western front. Connect a windows
machine and golly, no wonder we need gigabit network adapters these days.

Safety Articles | Usenet Groups | Usenet News | Bluegrass