Hi:
On a VAIO with debian9 (stretch), wicd, Zyxel router WPA 1/2 pass, wired connection is OK, also on long connection to far clusters and remote visualization. In contrast, wireless connection normally fails. However, when it is established, it is as reliable as wired.

When wireless fails, the terminal reads:

Launching wicd-client or wicd-curses normally raises empty windows.

When I am in Austria, with the same vaio, never experienced problems with wi-fy from another router. Otherwise, as I said, when wirelles is established through the Zyxels, it never fails on constant RMV with far cluster.

Thanks for advice, should what I reported being enough for grasping the problem.

chiendarret

Ceni bails me out when wicd fails to connect for whatever reason. It is command line used in a terminal. Real small also.

To install

In case of dependecy errors

to launch it

It takes up hardly any space and I have had wicd fail where the router and wicd showed connected. But the router needed to be reset before wicd would interface with it. Hint: I also learned bad password in Wicd means reset the router also. You can try CENI or not. Just giving choice here.

Next time you get this problem in Wicd. A

May not hurt to be posted either. WICD has been pretty good using my Samsung S7 Edge as a router out in the wilderness when I am on my motorcycle.

Here on failure to connect with wicd. Thanks

Well. Looks like wlan0 is seen. How about posting a last 20 or so lines relating to wicd and wlan0 running dmesg in terminal when it fails.

Just to be sure. I'll include sudo.

Here it is:

"wlan0: link becomes ready": that is always seen, no matter whether wireless connection occurs or not (when "# dhclient" is silent, also "startx" only raises X11 for xfce.

Might wanna google search

My results

Gotta admit. This is a toughy for me.

Just curious. Anything spit out when you run.

I'm wondering if this is a hardware limitation having to do with

and

Just to make sure yours matches mine.

Mine has

START_DAEMON=yes

DAEMON_ARGS=”–keep-connection”

when wireless connection is established

You left out the pipe symbol in that command.

Anyways. Everything looks like it is good to me. I suspect your problem lies between your Zyxel router and your Internet Provider Servers that get you on the net.

I run into this from time time myself. Usually resetting my router and running wicd again fixes this. I am not sure if it is my router starting to fail because it is years old or my crappy ISP provider server is dropping out for what ever reason.

Like I said. A short walk. Unplug my router for 10 seconds. Plug it back in. Usually fixes this for me. Unless somebody ran into a telephone pole or my ISP is down for scheduled maintenance.

Living in the boon docks. I live with compromises.

Last October in Austria I had a wireless-only router of unknown brand, got from the Internet provider. Never a failure to establish wireless connection with my vaio. That points to your suspicion about Zyxel-Italian provider. Switching off both Zyxel and vaio, and restarting them in the given order, wireless connection was established:

Switching off vaio only, and restarting it, no wireless connection:

Restarting the router was no cure, however there must be something wrong with my Zyxel-Provider.

However, I forgot to mention that my Lenny3 smart-phone with Android 6.0, never had problems with my Zyxel.

I know you said re-starting the vaio don't help plus restarting the router don't help. But then re-setting both at once does.

But. My next trouble shooting step if this was my gear would be to suspect the wireless card is getting hot in the vaio and dropping out. Then after it cools off. It connects again. I've seen this before on older gear also. Vaio might need cleaning with can of compressed air.

I don't think you have a wicd problem . I could be wrong. But we covered a lot of commands and text files. Things look OK to me as far as how wicd is working, and, ath9k driver has a good track record also.

Cleaning my vintage vaio laptop from dust is a good idea. An additional move I am thinking about is updating the firmware (currently V3.40 (AGL3 of 05/29/2001), available V3.40 (AGL10 of 03/04/2013). Delayed to after the week end, when shops are open. Updating the modem is nonsense here in Italy, as we are at the copper age. Luckily my vaio only serves to access the login nodes of a NextScale.
chiendarret
Beer entails a lot of sucrose, far beyond the need, but beer+much bike may be OK.

You were right: cleaning vaio from dust let it access wireless consistently. Now vaio operates without previous noise and heating. Thanks. This is not saying that vaio-Zyxel are in optimal conditions, however. For example:

however,

which, in my opinion, means that BIOS should be updated. Something I have no experience with.

Also, as I wrote, Zyxel's firmware is 16 years old, while a 2013 edition is available. This should be easy to update. Well, this is a vintage notebook from a company that stopped doing PCs. I got it for an ice-cream from people that found it unmanageably slow with recent microsoft software. With amd64 it does what a i3 CPU can do, surely not my computations, but fast enough to access a NextScale, also for remote visualization, or getting Lucio Dalla's Canzone from youtube. If anything, I don't like working without mirror raid, as with vaio, under the prospect that should the single HD get stopped, the OS should be reinstalled.

chiendarret