Comment # 17 on bug 1163771 from Freek de Kruijf

(In reply to Chester Lin from comment #16)
> Hi Freek,
> 
> Did you use wicked to configure wlan0 as well? I just found that
> NetworkManager works fine on wlan0 without having an abnormal disconnection.
> Would you like to try it? Since NetworkManager can work I think this issue
> should not be related to kernel.

Yes, I did use wicked.

I started with a fresh JeOS image.
As was to be expected, wlan0 did not come up, so I replaced wpa_supplicant by
the one from the 15.2 repository. After that wlan0 did not come up, but iwlist
did not show the 2.4 GHz AcessPoint, only 5. I did a reboot and wlan0 did come
up. Did an ifdown eth0, ifdown wlan0 and ifup wlan0 and a ping to the router. I
let it run for 1000 pings without missing a single one.

Did the same with the KDE version, which had a different outcome.
Had a ping session of 4500 pings of which about 500 were successful.
Often there was no answer on the ping, but also I got Destination not
reachable.
On another tty I did, in that case,------------------------ a "wicked ifup
wlan0" after which ping answers did reappear, but shortly after that I got no
answers, which did reappear and vanished again, until Destination not reachable
did appear.

Changed in the KDE image to NetworkManager. Managed to enable the wifi
connection. Started a ping to the router. This ping showed the same behavior as
with wicked.
It looks like NetworkManager detects the Destination unreachable and restarts
the connection. I see about 8 successful pings after which there are no answers
on the ping until about another about 8 pings or Destination unreachable.