Alex Grim - 2008-12-11

I hope that this is not the wrong forum, but i wanted to offer assistance for those who may be having the same problem, and ask the devs if there is a way to edit this behavior:

When scanning for networks with my "Intel Corporation PRO/Wireless 3945ABG Network...", wlassistant can correctly SEE, LIST and provide info on all networks available. But, when trying to connect to one, even an unencrypted network, it fails.

I started wlassistant from the command line, so that i could see the output, and here is what i found:
====CODE====
ACTION: CONNECT.
Running DHCP client found.
kill_dhcp: /sbin/dhclient -r wlan0
==>stderr: ipcalc: netmask or prefix expected
Usage: ipcalc [OPTION...]
  -b, --broadcast     Display calculated broadcast address
  -h, --hostname      Show hostname determined via DNS
  -m, --netmask       Display default netmask for IP (class A, B, or C)
  -n, --network       Display network address
  -p, --prefix        Display network prefix
  -s, --silent        Don't ever display error messages

Help options:
  -?, --help          Show this help message
  --usage             Display brief usage message
Nothing to flush.
No pre-connection command specified.
iwconfig_set: /sbin/iwconfig wlan0 mode managed channel 6 key open xxxxxxxxxx essid Ionisis
iwconfig_ap: /sbin/iwconfig wlan0 ap 00:16:B6:0B:37:05
ifconfig_dhcp: /sbin/dhclient wlan0
==>stderr: Nothing to flush.
Running DHCP client found.
kill_dhcp: /sbin/dhclient -r wlan0
==>stderr: ipcalc: netmask or prefix expected
Usage: ipcalc [OPTION...]
  -b, --broadcast     Display calculated broadcast address
  -h, --hostname      Show hostname determined via DNS
  -m, --netmask       Display default netmask for IP (class A, B, or C)
  -n, --network       Display network address
  -p, --prefix        Display network prefix
  -s, --silent        Don't ever display error messages

Help options:
  -?, --help          Show this help message
  --usage             Display brief usage message
CONNECTION FAILED.
disconnect: /sbin/iwconfig wlan0 mode managed key off ap off essid off
[^v^]#
====CODE====

As you can see, when it is notified that there is nothing to flush for the dhclient command, it fails. This can be fixed by ignoring the "nothing to flush" error, and continuing. As proof, wait for it to fail, then exit out of wlassistant, and in the terminal, type "dhclient wlan0", and it will say the same thing, "nothing to flush", and then it will finish, and return you to the prompt. You are then connected to the network.

So, my question is, how can i edit this behavior in wlassistant so that it will continue, despite the "nothing to flush" error? I don't mind this little inconvinience myself, but this is a laptop that i am repairing for a friend who barely knows how to check her email, so if wlassistant's gui cannot connect for her, she's screwed.

Thanx