Network Names (ESSID) discovery faoled
Hello,
I do not know when this started. I rebooted my machine and couldn't
connect to the internet.
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]"
failed.
Exit code: 2
Error output: RTNETLINK answers: Input/output error
I am not sure how to deal with it
The device is a RT-AC3100 router. It has been working flawlessly for
over 2 years. My other devices using wireless do not have any proplems
connecting/
OopenSUSE Leap 15.4
Regards,
--
Boyd Gerber
On Mon, 31 Oct 2022 17:23:08 -0600, Boyd Lynn Gerber
I do not know when this started. I rebooted my machine and couldn't connect to the internet.
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
I am not sure how to deal with it
The device is a RT-AC3100 router. It has been working flawlessly for over 2 years. My other devices using wireless do not have any proplems connecting/
I don't know anything about the error message, but you could try power cycling, or rebooting, the router. -- Robert Webb
On Tuesday 2022-11-01 03:02, Robert Webb wrote:
On Mon, 31 Oct 2022 17:23:08 -0600, Boyd Lynn Gerber
wrote: I do not know when this started. I rebooted my machine and couldn't connect to the internet.
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
I am not sure how to deal with it
The device is a RT-AC3100 router. It has been working flawlessly for over 2 years. My other devices using wireless do not have any proplems connecting/
I don't know anything about the error message, but you could try power cycling, or rebooting, the router.
Done that before posting. Driving me crazy. Google search doesn't
help.
thanks,
--
Boyd Gerber
On Tue, Nov 1, 2022 at 3:10 PM Boyd Lynn Gerber
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
This is maybe a disk or filesystem issue. Are other commands executed properly? Any errors on dmesg?
On Tue, Nov 1, 2022 at 4:10 PM Boyd Lynn Gerber
On Tuesday 2022-11-01 03:02, Robert Webb wrote:
On Mon, 31 Oct 2022 17:23:08 -0600, Boyd Lynn Gerber
wrote: I do not know when this started. I rebooted my machine and couldn't connect to the internet.
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
I am not sure how to deal with it
The device is a RT-AC3100 router. It has been working flawlessly for over 2 years. My other devices using wireless do not have any proplems connecting/
I don't know anything about the error message, but you could try power cycling, or rebooting, the router.
Done that before posting. Driving me crazy. Google search doesn't help.
You could start with explaining where you see this message, what you do before this message appears. Are you using wicked or NetworkManager or something else. Educated guess is that to bring the wireless interface up it has to be associated with the access point which means this message is probably the consequence of a failed association. Also the subject of your post says "discovery failed" but there is absolutely nothing about "discovery" of any kind in your message.
On Tuesday 2022-11-01 16:29, Andrei Borzenkov wrote:
On Tue, Nov 1, 2022 at 4:10 PM Boyd Lynn Gerber
wrote: On Mon, 31 Oct 2022 17:23:08 -0600, Boyd Lynn Gerber
wrote: I do not know when this started. I rebooted my machine and couldn't connect to the internet.
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
I am not sure how to deal with it
The device is a RT-AC3100 router. It has been working flawlessly for over 2 years. My other devices using wireless do not have any proplems connecting/
I don't know anything about the error message, but you could try power cycling, or rebooting, the router.
Done that before posting. Driving me crazy. Google search doesn't help.
You could start with explaining where you see this message, what you do before this message appears. Are you using wicked or NetworkManager or something else.
yast2->Network Setting->Edit wlan0 (Wireless) Choose Network. scanning for Network Window pops up Error Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
Educated guess is that to bring the wireless interface up it has to be associated with the access point which means this message is probably the consequence of a failed association. Also the subject of your post says "discovery failed" but there is absolutely nothing about "discovery" of any kind in your message.
yes the discovery failed. I have 8 other devices that do nothave any
trouble accessibng it with the sames Network Name (ESSID) and
mode/password.
Thanks,
--
Boyd Gerber
On 01.11.2022 17:27, Boyd Lynn Gerber wrote:
On Tuesday 2022-11-01 16:29, Andrei Borzenkov wrote:
On Tue, Nov 1, 2022 at 4:10 PM Boyd Lynn Gerber
wrote: On Mon, 31 Oct 2022 17:23:08 -0600, Boyd Lynn Gerber
wrote: I do not know when this started. I rebooted my machine and couldn't connect to the internet.
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
I am not sure how to deal with it
The device is a RT-AC3100 router. It has been working flawlessly for over 2 years. My other devices using wireless do not have any proplems connecting/
I don't know anything about the error message, but you could try power cycling, or rebooting, the router.
Done that before posting. Driving me crazy. Google search doesn't help.
You could start with explaining where you see this message, what you do before this message appears. Are you using wicked or NetworkManager or something else.
yast2->Network Setting->Edit wlan0 (Wireless)
Choose Network.
scanning for Network
Window pops up
Error Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
Let's assume you are using wicked.
Educated guess is that to bring the wireless interface up it has to be associated with the access point which means this message is probably the consequence of a failed association.
I was wrong. It is possible (and likely necessary) to set device up before doing anything else. So it sounds like device issue. Reboot, and post full output of "journalctl -b" (upload to https://susepaste.org).
Also the subject of your post
says "discovery failed" but there is absolutely nothing about "discovery" of any kind in your message.
yes the discovery failed.
It does not even attempt discovery, so discovery most certainly cannot fail when it is not even started.
I have 8 other devices that do nothave any trouble accessibng it with the sames Network Name (ESSID) and mode/password.
Thanks,
Hello, As seen below every boot and dumping to a file and searching the results of journalctl -xb provieds. On Tuesday 2022-11-01 20:46, Andrei Borzenkov wrote:
On 01.11.2022 17:27, Boyd Lynn Gerber wrote:
On Tuesday 2022-11-01 16:29, Andrei Borzenkov wrote:
On Tue, Nov 1, 2022 at 4:10 PM Boyd Lynn Gerber
wrote: On Mon, 31 Oct 2022 17:23:08 -0600, Boyd Lynn Gerber
wrote: I do not know when this started. I rebooted my machine and couldn't connect to the internet.
Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
I am not sure how to deal with it
The device is a RT-AC3100 router. It has been working flawlessly for over 2 years. My other devices using wireless do not have any proplems connecting/
I don't know anything about the error message, but you could try power cycling, or rebooting, the router.
Done that before posting. Driving me crazy. Google search doesn't help.
You could start with explaining where you see this message, what you do before this message appears. Are you using wicked or NetworkManager or something else.
yast2->Network Setting->Edit wlan0 (Wireless)
Choose Network.
scanning for Network
Window pops up
Error Execution of command "[["/usr/sbin/ip", "link", "set", "wlan0", "up"]]" failed. Exit code: 2 Error output: RTNETLINK answers: Input/output error
Let's assume you are using wicked.
yes, in the results from journalctl -xb p_id 0x00340aff sub 1028:0310 dfs 0 testmode 0 pi 6 features wowlan,ignore-otp,mfp crc32 bf907c7c 0000:00:14.0/usb1/1-1/1-1.2" p_id 0x00340aff sub 1028:0310 dfs 0 testmode 0 pi 6 features wowlan,ignore-otp,mfp crc32 bf907c7c 2812cba otp max-sta 32 raw 0 hwcrypto 1
Educated guess is that to bring the wireless interface up it has to be associated with the access point which means this message is probably the consequence of a failed association.
I was wrong. It is possible (and likely necessary) to set device up before doing anything else. So it sounds like device issue. Reboot, and post full output of "journalctl -b" (upload to https://susepaste.org).
Also the subject of your post
says "discovery failed" but there is absolutely nothing about "discovery" of any kind in your message.
yes the discovery failed.
It does not even attempt discovery, so discovery most certainly cannot fail when it is not even started.
Oct 31 16:05:23 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterface() failed
(fi.w1.wpa_supplicant1.UnknownEError: wpa_supplicant couldn't grab this
inteface.)
Oct 31 16:05:23 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wireless.changeDevice() failed: Invalid argumets
Oct 31 16:05:23 blg wickedd-nanny[4063]: wlan0: failed to bring up
device, still contining
Oct 31 16:05:31 blg wicked[4065]: wlan0 device-not-running
Oct 31 16:05:32 blg vmnetBridge[4886]: RTM_NEWLINK: name:wlan0 index:3
flags:0x00001002
...
Oct 31 16:44:02 blg wickedd[4053]: Wireless disconnect failed - unknown
interface wlan0(3)
...
Oct 31 16:44:10 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterface() failed
(fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this
interface.)
Oct 31 16:44:10 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wireless.changeDevice() failed: Invalid arguments
Oct 31 16:44:10 blg wickedd-nanny[4063]: wlan0: failed to bring up
device, still contining
...
Oct 31 16:44:10 blg wicked[17758]: wlan0 device-ready
Oct 31 16:44:10 blg wicked[17758]: wlan0 device-not-running
Oct 31 16:44:10 blg systemd[1]: Reloaded wicked managed network
interfaces.
...
Oct 31 16:45:28 blg firewalld[3927]: ERROR: UNKNOWN_INTERFACE: 'wlan0'
is not in any zo>e
...
Oct 31 16:45:34 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterface() failed
(fi.w1.wpa_supplicant1.UnknownEError: wpa_supplicant couldn't grab this
inteface.)
Oct 31 16:45:34 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wireless.changeDevice() failed: Invalid arguments
...
Oct 31 16:48:08 blg wickedd[4053]: Wireless disconnect failed - unknown
interface wlan0(3)
Oct 31 16:48:09 blg firewalld[3927]: ERROR: UNKNOWN_INTERFACE: 'wlan0'
is not in any zone
Oct 31 16:48:09 blg wicked[18778]: wlan0 device-ready
Oct 31 16:48:09 blg systemd[1]: Reloaded wicked managed network
interfaces.
...
Oct 31 16:48:09 blg systemd[1]: Reloaded wicked managed network
interfaces.
░░ Subject: A reload job for unit wicked.service has finished
░░ Defined-By: systemd
░░ Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A reload job for unit wicked.service has finished.
░░
░░ The job identifier is 52942 and the job result is done.
...
Oct 31 16:52:21 blg wickedd[4053]: Wireless disconnect failed - unknown
interface wlan0(3)
Oct 31 16:52:21 blg firewalld[3927]: WARNING: NOT_ENABLED: wlan0
Oct 31 16:52:21 blg firewalld[3927]: ERROR: UNKNOWN_INTERFACE: 'wlan0'
is not in any zone
...
Oct 31 16:52:28 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterce() failed
(fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this
interface.)
Oct 31 16:52:28 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wireless.changeDevice() failed: Invalid arguments
...
Oct 31 16:52:28 blg wicked[19863]: wlan0 device-ready
Oct 31 16:52:28 blg wicked[19863]: wlan0 device-not-running
Oct 31 16:52:28 blg systemd[1]: Reloaded wicked managed network
interfaces.
░░ Subject: A reload job for unit wicked.service has finished
░░ Defined-By: systemd
░░ Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A reload job for unit wicked.service has finished.
░░
░░ The job identifier is 52944 and the job result is done.
...
Oct 31 16:55:09 blg wicked[20440]: em1 device-ready
Oct 31 16:55:09 blg wicked[20440]: wlan0 device-ready
Oct 31 16:55:09 blg wicked[20440]: em1 up
Oct 31 16:55:09 blg systemd[1]: Reloaded wicked managed network
interfaces.
░░ Subject: A reload job for unit wicked.service has finished
░░ Defined-By: systemd
░░ Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A reload job for unit wicked.service has finished.
░░
░░ The job identifier is 52946 and the job result is done.
...
Oct 31 17:37:18 blg firewalld[3927]: WARNING: NOT_ENABLED: wlan0
Oct 31 17:37:18 blg kernel: userif-2: sent link down event.
Oct 31 17:37:18 blg kernel: userif-2: sent link up event.
...
repeats
Oct 31 17:37:26 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterf>
Oct 31 17:37:26 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wir
Oct 31 17:37:32 blg wicked[6816]: wlan0 device-ready
Oct 31 17:37:32 blg wicked[6816]: em1 up
Oct 31 17:37:32 blg wicked[6816]: wlan0 device-not-running
Oct 31 17:37:32 blg systemd[1]: Reloaded wicked managed network
interfaces.
░░ Subject: A reload job for unit wicked.service has finished
░░ Defined-By: systemd
░░ Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A reload job for unit wicked.service has finished.
░░
░░ The job identifier is 55886 and the job result is done.
and Nov 01 07:12:47 blg wickedd[4053]: Wireless disconnect failed -
unknown interface wlan0
...
Nov 01 07:12:56 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterf>
Nov 01 07:12:56 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wir
...
Nov 01 07:13:02 blg wicked[32537]: em1 up
Nov 01 07:13:02 blg wicked[32537]: wlan0 device-not-running
Nov 01 07:13:02 blg systemd[1]: Reloaded wicked managed network
interfaces.
░░ Subject: A reload job for unit wicked.service has finished
░░ Defined-By: systemd
░░ Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A reload job for unit wicked.service has finished.
░░
░░ The job identifier is 94086 and the job result is done.
...
Nov 01 08:46:51 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterf
Nov 01 08:46:51 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wir
...
Nov 01 08:46:56 blg wicked[15451]: em1 device-ready
Nov 01 08:46:56 blg wicked[15451]: wlan0 device-ready
Nov 01 08:46:56 blg wicked[15451]: em1 up
Nov 01 08:46:56 blg wicked[15451]: wlan0 device-not-running
Nov 01 08:46:56 blg systemd[1]: Reloaded wicked managed network
interfaces.
░░ Subject: A reload job for unit wicked.service has finished
░░ Defined-By: systemd
░░ Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A reload job for unit wicked.service has finished.
░░
░░ The job identifier is 95846 and the job result is done.
...
repeats
Nov 01 09:09:20 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterf
maually trying to bring it up
TTY=pts/17 ; PWD=/sdahome/gerberb ; USER=root ; COMMAND=/usr/sbin/ifup
wlan0
do:session): session opened for user root by gerberb(uid=1000)
g route not matching any interface: ipv4 192.168.140.0/24 via
192.168.140.1 type unicast table main scope universe protocol boot
g route not matching any interface: ipv4 192.168.1.0/24 via 192.168.1.1
type unicast table main scope universe protocol boot
repeats
Nov 01 09:19:25 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterf
repeats
Nov 01 09:33:22 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterf>
Nov 01 09:33:22 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wir>
...
Nov 01 12:48:16 blg wickedd[4053]: Wireless disconnect failed - unknown
interface wlan0(3)
Nov 01 12:48:17 blg firewalld[3927]: WARNING: NOT_ENABLED: wlan0
Nov 01 12:48:24 blg wickedd[4053]: wlan0: dbus call
/fi/w1/wpa_supplicant1.CreateInterface() failed
(fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this
interface.)
Nov 01 12:48:24 blg wickedd-nanny[4063]: device wlan0: call to
org.opensuse.Network.Wireless.changeDevice() failed: Invalid arguments
Nov 01 12:48:24 blg wicked[27304]: wlan0 device-ready
Nov 01 12:48:24 blg wicked[27304]: wlan0 device-not-running
Nov 01 12:48:24 blg systemd[1]: Reloaded wicked managed network
interfaces.
░░ Subject: A reload job for unit wicked.service has finished
░░ Defined-By: systemd
░░ Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A reload job for unit wicked.service has finished.
░░
░░ The job identifier is 102305 and the job result is done.
The device is changing from ready to device-not-running.
Regards,
--
Boyd Gerber
Hello,
I stilld get the error if I stry to scan, but if I use the last known
/etc/sysconfig/network/ifcfg-wlan0
from August 18th 2022 and just boot and nottry to change it in yast I
get a working WIFI connection to the device.
Thanks everyone for suggestions and responses.
--
Boyd Gerber
participants (4)
-
Andrei Borzenkov
-
Boyd Lynn Gerber
-
Robert Webb
-
Stratos Zolotas