Comment 18 for bug 64841

Revision history for this message
Steve Kowalik (stevenk) wrote : Re: wireless assisant does not connect in edgy

I have also worked on this, and have a patch that somewhat encompasses Ryan's changes, but also makes wlassistant work for me. There is in fact more than one problem, and I'm sure that the second and third problems would have come up during testing.

The problems:
1. wlassistant fires off dhclient, which complains about a zero length PID file on stderr. wlassistant takes any output on stderr as being a problem, and so kills dhclient.
2. wlassistant then parses dhclient's leases file, which could contain any number of leases, picks the first default gateway and tries to ping it. And gets upset if it fails.
3. Even commenting out that block, it then runs route, and looks for 'default' followed by an IP address, which is only the case if your default gateway doesn't reverse resolve.

Due to these three problems, I think this bug should be solved in Edgy, given it has the potential to affect every Kubuntu Edgy user that runs wlassistant.

Attached is a debdiff which solves all three of these problems. I have tested this (over and over, sigh) and it works for me.