Re: wicd trouble -- continued
On Thursday 28 July 2016 14:35:09 Mike McGinn wrote:
> On 07/28/2016 07:36 AM, Brian wrote:
> > On Wed 27 Jul 2016 at 22:36:01 -0600, Glenn English wrote:
> >>> 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.
> >
> > Indeed; presumably it has decided association and authentication with
> > the access point has successfully taken place and the interface has got
> > an IP number. However, there does not appear to be routing between the
> > interface and the AP.
> >
> > The issue is whether it is something in your setup or due to wicd.
> >
> >>> 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.
> >
> > I'd suggest you test the association, authentication and obtaining of
> > an IP stages without using wicd. It shouldn't be necessary to stop it
> > but
> >
> > systemctl stop wicd.service
> >
> > will do just that.
> >
> > Obtain the wireless interface name with
> >
> > ifconfig -a
> >
> > and start the supplicant in one terminal with
> >
> > wpa_supplicant -i <interface> -C /run/wpa_supplicant
> >
> > Read
> >
> > https://lists.debian.org/debian-user/2016/07/msg00130.html
> >
> > and use wpa_cli as directed. After association do
> >
> > dhclient -v <interface>
> >
> > How does that go?
> >
> >> 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.
> >
> > It is wpa_supplicant which does the association and authentication. I
> > assume dhclient is used to get an IP and set up routing. If wicd manages
> > these processes correctly one would expect pinging the AP to work.
> >
> >> Does anybody have any idea why this might be happening?
> >
> > Me? Not really. :)
>
> I had some trouble with wicd which I cured by making sure that network
> manager was not running. Make sure NM is stopped and does not start.
... by uninstalling it.
Lisi
Reply to: