On Sunday 03 July 2016 19:59:50 deloptes wrote: > Lisi Reisz wrote: > > I have discovered something I find interesting in this, which does not > > seem to be directly in reply to anything that has gone before - so it was > > difficult > > to place it in the thread. I have deliberately broken the > > "conversation", but not the thread. > > > > From the router's log: Every time I try (once) to connect to the router > > from the laptop with wicd, using the Intel card, it makes two attempts to > > connect > > and the router ALLOWS both. So why, when it is allowed to connect, does > > it > > not do so??? I have checked this out specifically. :-/ > > > > Lisi
Thanks. :-) > I assume you have not changed passwords on the access point recently. Yes, I have - but before the laptop had been told what it was. When I had gone onto the router to add the MAC address of the laptop. But I will try to retype it in the laptop. I am a lousy typist and an almost equally lousy proofreader. Meanwhile, it is now worse than it was before, and is not seeing the access point at all. :-( > What could be an issue is that wicd can not access the password stored > locally or have some other issue. I would look into this direction. perhaps > you can run it with debug enabled and see where it fails. If I can once get it started! I thought that I would start again in the morning. > It could be also > that your wpa_supplicant has issue(s). Yes, I will investigate this. > What I also think you should do, is change the name from eth1 to wlan0 if > using jessie. <gulp>. It would obviously be helpful, but I have always heretofore just accepted the interface name I was given! Google here I come again. Thanks. Lisi
