Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

nmcli do NOT sees my ssid

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
alexanderbeerhoff
Posts: 35
Joined: 2017-09-05 11:52

nmcli do NOT sees my ssid

#1 Post by alexanderbeerhoff »

Hi, I'm on debian testing with kernel 10.5.23. Since few weeks can't get up my wifi connection and running "nmcli d w l" can's see my ssid while from other devices they are reachable. Sometimes I resolve the problem deleting the connection in nmcli with "nmcli c del con-name" but now this do not work anymore.

Here related from syslog

Code: Select all

Oct  3 19:59:20 old68pound dhclient[518]: receive_packet failed on wls5: Network is down
Oct  3 19:59:20 old68pound NetworkManager[377]: <info>  [1633283960.6370] manager: rfkill: Wi-Fi hardware radio set disabled
Oct  3 19:59:20 old68pound NetworkManager[377]: <info>  [1633283960.6413] audit: op="radio-control" arg="wireless-enabled" pid=1063 uid=1000 result="success"
Oct  3 19:59:20 old68pound NetworkManager[377]: <info>  [1633283960.6421] manager: rfkill: Wi-Fi now disabled by radio killswitch
Oct  3 19:59:20 old68pound systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct  3 19:59:20 old68pound systemd[1]: Started Load/Save RF Kill Switch Status.
Oct  3 19:59:22 old68pound NetworkManager[377]: <info>  [1633283962.6082] manager: rfkill: Wi-Fi hardware radio set enabled
Oct  3 19:59:22 old68pound NetworkManager[377]: <info>  [1633283962.6086] audit: op="radio-control" arg="wireless-enabled" pid=1069 uid=1000 result="success"
Oct  3 19:59:22 old68pound NetworkManager[377]: <info>  [1633283962.6103] manager: rfkill: Wi-Fi now enabled by radio killswitch
Oct  3 19:59:27 old68pound systemd[1]: systemd-rfkill.service: Succeeded.
Oct  3 20:00:42 old68pound dhclient[518]: DHCPDISCOVER on wls5 to 255.255.255.255 port 67 interval 6
Oct  3 20:00:48 old68pound dhclient[518]: DHCPDISCOVER on wls5 to 255.255.255.255 port 67 interval 6
Oct  3 20:00:48 old68pound kernel: [  387.029734] sky2 0000:0c:00.0 enp12s0: disabling interface
Oct  3 20:00:54 old68pound dhclient[518]: DHCPDISCOVER on wls5 to 255.255.255.255 port 67 interval 14
Oct  3 20:01:03 old68pound dhclient[518]: receive_packet failed on wls5: Network is down
Oct  3 20:01:03 old68pound NetworkManager[377]: <info>  [1633284063.6456] manager: rfkill: Wi-Fi hardware radio set disabled
Oct  3 20:01:03 old68pound NetworkManager[377]: <info>  [1633284063.6470] audit: op="radio-control" arg="wireless-enabled" pid=1143 uid=1000 result="success"
Oct  3 20:01:03 old68pound NetworkManager[377]: <info>  [1633284063.6503] manager: rfkill: Wi-Fi now disabled by radio killswitch
Oct  3 20:01:03 old68pound systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct  3 20:01:03 old68pound systemd[1]: Started Load/Save RF Kill Switch Status.
Oct  3 20:01:05 old68pound NetworkManager[377]: <info>  [1633284065.7661] manager: rfkill: Wi-Fi hardware radio set enabled
Oct  3 20:01:05 old68pound NetworkManager[377]: <info>  [1633284065.7666] audit: op="radio-control" arg="wireless-enabled" pid=1149 uid=1000 result="success"
Oct  3 20:01:05 old68pound NetworkManager[377]: <info>  [1633284065.7679] manager: rfkill: Wi-Fi now enabled by radio killswitch
Oct  3 20:01:08 old68pound dhclient[518]: DHCPDISCOVER on wls5 to 255.255.255.255 port 67 interval 15
Oct  3 20:01:08 old68pound dhclient[518]: send_packet: Network is down
Oct  3 20:01:08 old68pound dhclient[518]: dhclient.c:2446: Failed to send 300 byte long packet over wls5 interface.
Oct  3 20:01:10 old68pound systemd[1]: systemd-rfkill.service: Succeeded.
Oct  3 20:01:23 old68pound dhclient[518]: DHCPDISCOVER on wls5 to 255.255.255.255 port 67 interval 15
Oct  3 20:01:23 old68pound dhclient[518]: send_packet: Network is down
Oct  3 20:01:23 old68pound dhclient[518]: dhclient.c:2446: Failed to send 300 byte long packet over wls5 interface.
Oct  3 20:01:38 old68pound dhclient[518]: DHCPDISCOVER on wls5 to 255.255.255.255 port 67 interval 5
Oct  3 20:01:43 old68pound dhclient[518]: No DHCPOFFERS received.
Oct  3 20:01:43 old68pound dhclient[518]: No working leases in persistent database - sleeping.
Oct  3 20:01:53 old68pound dhclient[518]: receive_packet failed on wls5: Network is down
Oct  3 20:01:53 old68pound NetworkManager[377]: <info>  [1633284113.2602] manager: rfkill: Wi-Fi hardware radio set disabled
Oct  3 20:01:53 old68pound NetworkManager[377]: <info>  [1633284113.2605] audit: op="radio-control" arg="wireless-enabled" pid=1199 uid=1000 result="success"
Oct  3 20:01:53 old68pound NetworkManager[377]: <info>  [1633284113.2640] manager: rfkill: Wi-Fi now disabled by radio killswitch
Oct  3 20:01:53 old68pound systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct  3 20:01:53 old68pound systemd[1]: Started Load/Save RF Kill Switch Status.
Oct  3 20:01:55 old68pound NetworkManager[377]: <info>  [1633284115.3236] manager: rfkill: Wi-Fi hardware radio set enabled
Oct  3 20:01:55 old68pound NetworkManager[377]: <info>  [1633284115.3243] audit: op="radio-control" arg="wireless-enabled" pid=1205 uid=1000 result="success"
Oct  3 20:01:55 old68pound NetworkManager[377]: <info>  [1633284115.3285] manager: rfkill: Wi-Fi now enabled by radio killswitch
Here the interfaces:

Code: Select all

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eql: <MASTER> mtu 576 qdisc noop state DOWN mode DEFAULT group default qlen 5
    link/slip 
3: enp12s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:1e:c2:01:e0:80 brd ff:ff:ff:ff:ff:ff
4: wls5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether 0e:ff:90:4b:98:37 brd ff:ff:ff:ff:ff:ff permaddr 00:1e:52:73:de:f4
    altname wlp11s0
    
Suggestion?
Thanks for attention and best regards.

reinob
Posts: 1189
Joined: 2014-06-30 11:42
Has thanked: 97 times
Been thanked: 45 times

Re: nmcli do NOT sees my ssid

#2 Post by reinob »

From your log it seems your interface keeps being enabled and disabled by rfkill. Maybe you should address that first..

alexanderbeerhoff
Posts: 35
Joined: 2017-09-05 11:52

Re: nmcli do NOT sees my ssid

#3 Post by alexanderbeerhoff »

Hi, I forgot to say that can see ssid different from the two I use for 2,4 and 5 Ghz band.
Looking in the log likily what invoke rfkill is "nmcli radio wifi off/on" which I run to see if solve the problem.
Running

Code: Select all

nmcli radio wifi off
nmcli radio wifi on
I have in syslog (now I'm using ethernet):

Code: Select all

Oct  6 14:35:38 old68pound NetworkManager[417]: <info>  [1633523738.3147] manager: rfkill: Wi-Fi hardware radio set disabled
Oct  6 14:35:38 old68pound wpa_supplicant[438]: rfkill: WLAN soft blocked
Oct  6 14:35:38 old68pound NetworkManager[417]: <info>  [1633523738.3148] device (wls5): state change: disconnected -> unavailable (reason 'none', sys-iface-state: 'managed')
Oct  6 14:35:38 old68pound NetworkManager[417]: <info>  [1633523738.3186] audit: op="radio-control" arg="wireless-enabled" pid=37665 uid=1000 result="success"
Oct  6 14:35:38 old68pound NetworkManager[417]: <info>  [1633523738.3204] device (p2p-dev-wls5): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
Oct  6 14:35:38 old68pound systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct  6 14:35:38 old68pound NetworkManager[417]: <info>  [1633523738.3409] manager: rfkill: Wi-Fi now disabled by radio killswitch
Oct  6 14:35:38 old68pound wpa_supplicant[438]: nl80211: deinit ifname=wls5 disabled_11b_rates=0
Oct  6 14:35:38 old68pound systemd[1]: Started Load/Save RF Kill Switch Status.
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9269] manager: rfkill: Wi-Fi hardware radio set enabled
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9441] audit: op="radio-control" arg="wireless-enabled" pid=37672 uid=1000 result="success"
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9534] manager: rfkill: Wi-Fi now enabled by radio killswitch
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9671] device (wls5): supplicant interface state: internal-starting -> disconnected
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9673] device (p2p-dev-wls5): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9779] Wi-Fi P2P device controlled by interface wls5 created
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9788] manager: (p2p-dev-wls5): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/8)
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9805] device (p2p-dev-wls5): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9826] device (wls5): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct  6 14:35:40 old68pound NetworkManager[417]: <info>  [1633523740.9852] device (p2p-dev-wls5): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct  6 14:35:41 old68pound NetworkManager[417]: <warn>  [1633523741.0129] sup-iface[676a625642e46d9f,3,wls5]: call-p2p-cancel: failed with P2P cancel failed
Oct  6 14:35:45 old68pound systemd[1]: systemd-rfkill.service: Succeeded.

alexanderbeerhoff
Posts: 35
Joined: 2017-09-05 11:52

Re: nmcli do NOT sees my ssid

#4 Post by alexanderbeerhoff »

Hi, as suggested by a reply to this post, it's a problem related to me using custom kernel, as explained here:

Code: Select all

$ more /usr/share/doc/wireless-regdb/README.Debian
wireless-regdb for Debian
-------------------------

wireless-regdb provides a machine-readable database of legal
regulations on radio emissions that affect use of wireless networking.
The Linux kernel and drivers use this to maintain compliance with
those regulations.

The database may be loaded by either crda (in the crda package) or by
the kernel.  Kernel loading was implemented in Linux 4.15, but only
enabled in the Debian package from 5.5 onward.

If you use a custom kernel built from upstream source, it will only
trust this database if it is signed by the upstream maintainer of
wireless-regdb.  To use the upstream database and signature instead of
the Debian version, run:

    update-alternatives --set regulatory.db \
        /lib/firmware/regulatory.db-upstream

Post Reply