Re: dlink dwa-556
On Tue, Dec 08, 2009 at 08:38:04PM -0500, Celejar wrote:
> On Tue, 8 Dec 2009 23:18:42 +0100
> lee <email@example.com> wrote:
> > Hm, at least wicd seems to have set the ESSID and to have found a
> > cell.
> ?? This output has nothing to do with wicd.
Not exactly, but it was one of the programs I tried out, and
apparently it left the device like half configured.
> If you're not using dhcp, then no dhclient process should be running.
> You should find out what's invoking it and stop it.
It's not running anymore. It was probably the kde network manager
trying to use dhcp.
> When debugging, we really don't want anything running except the most
> basic of command line utilities - I recommend that you stop all the
> higher level managers while we try to figure out the basic issues. In
> any event, you should never have multiple network managers running -
> they can (and probably will) interfere with each other and you'll get
I was trying out different programs while attempting to solve the
problems. I wouldn't want those as a permanent way to set up the
network card anyway.
> AFAIK, Debian doesn't modify wpa_supplicant, but when you properly
> configure /etc/network/interfaces, then the Debian network scripts will
> create the appropriate wpa_supplicant config file (on the fly?) and
> properly invoke wpa_supplicant, pointing it at the appropriate config
> file. When this works, you can see what Debian's done by grepping
> through the output of 'ps ax' for 'wpa_supplicant'.
It seems that Debian has provided scripts that read entries from
/etc/network/interfaces and then use wpa_supplicant to set
up the wireless networking accordingly. That way, there is no need for
And it's working fine now :) It's even pretty easy once you know how
to do it, but this was the first time I've set up a wireless
card/connection. Maybe I can improve on the documentation in the
Debian wiki ... and make an article about setting up this particular
network card or something ...