On another x64-bit machine, wireless was working fine a couple of days ago. I did a clean install of OpenSuse Leap 42.3 x64-bit. The wireless network is detected, but I cannot connect to the wireless at all!
As root, the command **ifup **yields: *network is managed by ‘NetworkManager.service’ -> skipping
*As root, the command **ifstatus **yields: *network is managed by ‘NetworkManager.service’ -> skipping
*The password being entered is correct, as the machine I am using now is on the network! Any ideas would be greatly appreciated. Thanks.
Can you confirm that you have configured your connection via the NetworkManager connection editor?
Open a terminal window and run the following to monitor NetworkManager output
sudo journalctl -fu NetworkManager
then try connecting to your wireless AP and capture the output generated. Report back with the relevant info.
deano_ferrari:
Can you confirm that you have configured your connection via the NetworkManager connection editor?
Open a terminal window and run the following to monitor NetworkManager output
sudo journalctl -fu NetworkManager
then try connecting to your wireless AP and capture the output generated. Report back with the relevant info.
Ok, I did as you instructed. The output is as follows:
-- Logs begin at Mon 2017-09-25 16:20:22 MDT. --
Sep 26 15:56:29 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Sep 26 15:56:29 linux-ama4 NetworkManager[1121]: <info> ModemManager available in the bus
Sep 26 15:56:29 linux-ama4 NetworkManager[1121]: <info> wpa_supplicant running
Sep 26 15:56:29 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: init -> starting
Sep 26 15:56:29 linux-ama4 NetworkManager[1121]: <info> (wlan0) supports 4 scan SSIDs
Sep 26 15:56:29 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: starting -> ready
Sep 26 15:56:29 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Sep 26 15:56:30 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: ready -> inactive
Sep 26 15:56:34 linux-ama4 NetworkManager[1121]: <info> startup complete
Sep 26 15:57:47 linux-ama4 NetworkManager[1121]: <info> connectivity: check for uri 'http://conncheck.opensuse.org' failed with 'Error resolving 'conncheck.opensuse.org': Name or service not known'
Sep 26 16:01:30 linux-ama4 NetworkManager[1121]: <info> (wlan0): Activation: starting connection 'BTHub6-R6HP' (79f4ee8b-cefc-428e-a3db-0fb988959290)
Sep 26 16:01:30 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 26 16:01:30 linux-ama4 NetworkManager[1121]: <info> NetworkManager state is now CONNECTING
Sep 26 16:01:30 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 26 16:01:30 linux-ama4 NetworkManager[1121]: <info> (wlan0): Activation: (wifi) access point 'BTHub6-R6HP' has security, but secrets are required.
Sep 26 16:01:30 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> (wlan0): Activation: (wifi) connection 'BTHub6-R6HP' has security, and secrets exist. No new secrets needed.
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> Config: added 'ssid' value 'BTHub6-R6HP'
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> Config: added 'scan_ssid' value '1'
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> Config: added 'psk' value '<omitted>'
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> Config: set interface ap_scan to 1
Sep 26 16:01:31 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: inactive -> scanning
Sep 26 16:01:32 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Sep 26 16:01:32 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: authenticating -> associating
Sep 26 16:01:32 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: associating -> associated
Sep 26 16:01:41 linux-ama4 NetworkManager[1121]: <warn> Connection disconnected (reason 15)
Sep 26 16:01:41 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: associated -> disconnected
Sep 26 16:01:41 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Sep 26 16:01:42 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Sep 26 16:01:42 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: authenticating -> associating
Sep 26 16:01:42 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: associating -> associated
Sep 26 16:01:51 linux-ama4 NetworkManager[1121]: <warn> Connection disconnected (reason 15)
Sep 26 16:01:51 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: associated -> disconnected
Sep 26 16:01:51 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Sep 26 16:01:52 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Sep 26 16:01:52 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: authenticating -> associating
Sep 26 16:01:52 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: associating -> associated
Sep 26 16:01:56 linux-ama4 NetworkManager[1121]: <warn> (wlan0): Activation: (wifi) association took too long
Sep 26 16:01:56 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Sep 26 16:01:56 linux-ama4 NetworkManager[1121]: <warn> (wlan0): Activation: (wifi) asking for new secrets
Sep 26 16:01:56 linux-ama4 NetworkManager[1121]: <warn> Connection disconnected (reason -3)
Sep 26 16:01:56 linux-ama4 NetworkManager[1121]: <info> (wlan0): supplicant interface state: associated -> disconnected
Sep 26 16:01:56 linux-ama4 NetworkManager[1121]: <warn> Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Sep 26 16:02:10 linux-ama4 NetworkManager[1121]: <warn> (wlan0): User canceled the secrets request.
Sep 26 16:02:10 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Sep 26 16:02:10 linux-ama4 NetworkManager[1121]: <info> NetworkManager state is now DISCONNECTED
Sep 26 16:02:10 linux-ama4 NetworkManager[1121]: <warn> (wlan0): Activation: failed for connection 'BTHub6-R6HP'
Sep 26 16:02:10 linux-ama4 NetworkManager[1121]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
It then asks me for the password, like before. I enter the correct one, and it then asks me for it again, and so on. After the first time, I canceled the password request to produce the above code.
NetworkManager[1121]: <warn> Connection disconnected (reason 15)
This ‘disconnection reason’ is associated with ‘NM_DEVICE_STATE_REASON_DHCP_START_FAILED DHCP client failed to start’. I’m not sure why that is occurring though.
Reference:https://wiki.ubuntu.com/DebuggingNetworkManager/ReasonCodes
deano_ferrari:
NetworkManager[1121]: <warn> Connection disconnected (reason 15)
This ‘disconnection reason’ is associated with ‘NM_DEVICE_STATE_REASON_DHCP_START_FAILED DHCP client failed to start’. I’m not sure why that is occurring though.
Reference:DebuggingNetworkManager/ReasonCodes - Ubuntu Wiki
Thanks for the reference. It worked before when on Leap 42.2 until three nights ago (I think after an update). I installed Leap 42.3, and have the same problem. I will try to find something. Hopefully someone else has an idea and responds to this thread! Thanks again for your help.
What does the following return?
ps -A|grep dh
Try starting ‘dhclient’ manually.
sudo dhclient
Any errors? Check that the process is active.
deano_ferrari:
What does the following return?
ps -A|grep dh
Try starting ‘dhclient’ manually.
sudo dhclient
Any errors? Check that the process is active.
ps -A|grep dh runs without issue, nothing is produced when I enter it in the terminal.
**sudo dhclient **takes a bit of time once entered in the terminal, I tried to connect afterward, and the same issue occurred, in which my password was requested. This is despite my password already being saved in the network settings.