Re: wicd trouble -- continued
> On Jul 25, 2016, at 5:53 PM, Glenn English <ghe@slsware.net> wrote:
>
> What does "Verifying access point association" mean
After some looking around, I found that a failure in that phase of connecting means that wicd tried to ping the AP 10 times, and failed.
> what do you do to make it OK?
I still have no idea. The one suggestion I've received was to look at some websites I'd already looked at.
Wicd converses with the AP enough to find the ESSID, to check that the MAC is OK, and to verify the password. But ping fails, regularly. I'd think that if it could do all that, ping ought to work.
Does anybody have any idea why this might be happening?
And does anybody know why wicd's logging is on for a while, then goes off, then back on. For no apparent reason (the 'logging' param in wicd's config is set to 1). Or is it wpa_supplicant.conf? I've replaced and edited so much stuff that I don't remember anymore.
Below is the original question. I understand a little of what's happening now; but still no idea how to fix it...
> I have several Debian boxes, Wheezy and Jessie. Wired and wireless (3 wireless -- wicd manged). 2 of then are Raspberry Pi 3's the other is a GoBook laptop. All 3 are Jessie. All are XFCE4.
>
> A few days ago, for no reason I can think of but surely something (I futz with my computers all the time, but I swear I did nothing to the laptop), their wicd started failing to connect with the AP. Everything went smoothly until that step ("Verifying access point association"). Then they stayed there for a long time, then said it couldn't connect.
>
> When I shut down the laptop one night, all was well. When it started the next morning, WiFi was bent.
>
> All have ethernet connectors, and all work successfully on Ethernet -- all connected by wicd.
>
> I replaced the chip in one of the Pi's with a backup, and it started working. I've copied its wicd directory and its wpa-supplicant directory to the laptop (and rebooted after each), with no success. I've looked on the 'Net for anything that could be causing this, nada.
>
> The Apple AP is OK, I think, because one of the Pi's and the MacAir works. The other 2 Debians worked until recently.
>
> Any explanation(s) would be gratefully appreciated. Reinstalling on the Pi's is reasonable, although its OS has been modified a bit. But the laptop would be a major job.
--
Glenn English
Reply to: