Complementing previous information, a power glitch that affected the AP router caused the same kind of behaviour by just disconnecting the link and reconnecting again:
from /var/log/daemon.log Sep 27 17:26:49 RJASTEC-06374 wpa_supplicant[836]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Sep 27 17:26:49 RJASTEC-06374 NetworkManager: <info> (eth1): supplicant connection state: completed -> disconnected Sep 27 17:26:50 RJASTEC-06374 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Same information in syslog.
To return I had to remove wl module and modprobed it.
NetworkManager had a segfault after the remove/insert of wl module, but the operation recorered:
[24651.585609] NetworkManager[766]: segfault at 50 ip 00007f7fef0e9ec0 sp 00007fff561a5c38 error 4 in libnl.so.1.1[7f7fef0c6000+4c000]
Hope this information is of some help to diagnose the bug.
Complementing previous information, a power glitch that affected the AP router caused the same kind of behaviour by just disconnecting the link and reconnecting again:
from /var/log/daemon.log 836]: CTRL-EVENT- DISCONNECTED - Disconnect event - remove keys
Sep 27 17:26:49 RJASTEC-06374 wpa_supplicant[
Sep 27 17:26:49 RJASTEC-06374 NetworkManager: <info> (eth1): supplicant connection state: completed -> disconnected
Sep 27 17:26:50 RJASTEC-06374 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Same information in syslog.
To return I had to remove wl module and modprobed it.
NetworkManager had a segfault after the remove/insert of wl module, but the operation recorered:
[24651.585609] NetworkManager[ 766]: segfault at 50 ip 00007f7fef0e9ec0 sp 00007fff561a5c38 error 4 in libnl.so. 1.1[7f7fef0c600 0+4c000]
Hope this information is of some help to diagnose the bug.