Problema con conexión a WiFi en Ubuntu 20.04 -- etworking campo con wireless campo con network-manager camp askubuntu Relacionados El problema

Problem with connection to wifi on Ubuntu 20.04


0
vote

problema

Español

Estoy usando Ubuntu 20.04.2 LTS. Kernel: 5.4.0-65-genérico

Tengo un problema para conectarme a mi adaptador WiFi. Cada vez que intento conectarlo, muestra estas líneas en / var / log / syslog.

  Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'ssid' value 'HUAWEI-m33t-5G' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'scan_ssid' value '1' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'bgscan' value 'simple:30:-70:86400' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'auth_alg' value 'OPEN' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'psk' value '<hidden>' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4061] device (wlp1s0): supplicant interface state: ready -> authenticating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4061] device (p2p-dev-wlp1s0): supplicant management interface state: ready -> authenticating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4120] device (wlp1s0): supplicant interface state: authenticating -> associating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4120] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4277] device (wlp1s0): supplicant interface state: associating -> associated Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4278] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> associated Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4435] device (wlp1s0): supplicant interface state: associated -> 4-way handshake Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4435] device (p2p-dev-wlp1s0): supplicant management interface state: associated -> 4-way handshake Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4647] device (wlp1s0): supplicant interface state: 4-way handshake -> completed Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4648] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "HUAWEI-m33t-5G" Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4648] device (p2p-dev-wlp1s0): supplicant management interface state: 4-way handshake -> completed Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4649] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4653] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.5089] dhcp4 (wlp1s0): state changed unknown -> expire Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7427] dhcp4 (wlp1s0): option dhcp_lease_time      => '259200' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7428] dhcp4 (wlp1s0): option domain_name_servers  => '192.168.100.1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7428] dhcp4 (wlp1s0): option expiry               => '1613778908' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option ip_address           => '192.168.100.16' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_broadcast_address => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_domain_name => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_domain_name_servers => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_domain_search => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_host_name  => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_interface_mtu => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_ms_classless_static_routes => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_nis_domain => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_nis_servers => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_ntp_servers => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_rfc3442_classless_static_routes => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_root_path  => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_routers    => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_static_routes => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_subnet_mask => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_time_offset => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): option requested_wpad       => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): option routers              => '192.168.100.1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): option subnet_mask          => '255.255.255.0' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): state changed expire -> bound Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7491] device (wlp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:08 ws16-silhavik dbus-daemon[1044]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.131' (uid=0 pid=5597 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Feb 17 00:55:08 ws16-silhavik systemd[1]: Starting Network Manager Script Dispatcher Service... Feb 17 00:55:08 ws16-silhavik systemd[1]: Started Network Manager Script Dispatcher Service. Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7817] device (wlp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7819] device (wlp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7824] manager: NetworkManager state is now CONNECTED_LOCAL Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7914] manager: NetworkManager state is now CONNECTED_SITE Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7916] policy: set 'HUAWEI-m33t-5G' (wlp1s0) as default for IPv4 routing and DNS Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7922] device (wlp1s0): Activation: successful, device activated. Feb 17 00:55:09 ws16-silhavik NetworkManager[5597]: <info>  [1613519709.4119] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 17 00:55:09 ws16-silhavik whoopsie[1720]: [00:55:09] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/56 Feb 17 00:55:09 ws16-silhavik whoopsie[1720]: [00:55:09] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/56 Feb 17 00:55:09 ws16-silhavik whoopsie[1720]: [00:55:09] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/56 Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.0706] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.0724] policy: set 'HUAWEI-m33t-5G' (wlp1s0) as default for IPv6 routing and DNS Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.1438] dhcp6 (wlp1s0): option dhcp6_name_servers   => 'fe80::1' Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.1439] dhcp6 (wlp1s0): state changed unknown -> bound **Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <warn>  [1613519717.8735] sup-iface[0x55e24cba1930,wlp1s0]: connection disconnected (reason -4)** Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.8952] device (wlp1s0): supplicant interface state: completed -> disconnected Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.8953] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> disconnected Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.9788] device (wlp1s0): supplicant interface state: disconnected -> scanning Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.9789] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning Feb 17 00:55:22 ws16-silhavik systemd[1]: NetworkManager-dispatcher.service: Succeeded. Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <warn>  [1613519733.0658] device (wlp1s0): link timed out. Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.0692] device (wlp1s0): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed') Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.0698] manager: NetworkManager state is now DISCONNECTED Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <warn>  [1613519733.0705] device (wlp1s0): Activation: failed for connection 'HUAWEI-m33t-5G' Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.0712] device (wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:33 ws16-silhavik dbus-daemon[1044]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.131' (uid=0 pid=5597 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Feb 17 00:55:33 ws16-silhavik systemd[1]: Starting Network Manager Script Dispatcher Service... **Feb 17 00:55:33 ws16-silhavik org.kde.kdeconnect.daemon.desktop[2687]: "No such interface "org.freedesktop.DBus.Properties"  on object at path** /org/freedesktop/NetworkManager/ActiveConnection/56" Feb 17 00:55:33 ws16-silhavik systemd[1]: Started Network Manager Script Dispatcher Service. Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1068] dhcp4 (wlp1s0): canceled DHCP transaction Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1068] dhcp4 (wlp1s0): state changed bound -> done Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1070] dhcp6 (wlp1s0): canceled DHCP transaction Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1070] dhcp6 (wlp1s0): state changed bound -> done Feb 17 00:55:37 ws16-silhavik NetworkManager[5597]: <info>  [1613519737.1337] device (wlp1s0): supplicant interface state: scanning -> inactive Feb 17 00:55:37 ws16-silhavik NetworkManager[5597]: <info>  [1613519737.1341] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> inactive   

Creo que podría ser un problema con alguna interfaz o algo más. Funciona correctamente de cualquier otro dispositivo (iPhones, Mac), pero el único problema es con mi Dell con Ubuntu 20.04.

No sé si está relacionado, pero cada vez que intenté conectarme con WiFi Otros dispositivos perdidos de conexión durante un par de minutos. Parece que mi intento reinicia el adaptador WiFi. Lo mismo sucedió cuando intenté la conexión por cable.

Gracias por cualquier sugerencia.

Original en ingles

I am using Ubuntu 20.04.2 LTS. Kernel: 5.4.0-65-generic

I have a problem to connect to my wifi adapter. Everytime i try to connect it shows these lines in /var/log/syslog.

Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'ssid' value 'HUAWEI-m33t-5G' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'scan_ssid' value '1' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'bgscan' value 'simple:30:-70:86400' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'auth_alg' value 'OPEN' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.3710] Config: added 'psk' value '<hidden>' Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4061] device (wlp1s0): supplicant interface state: ready -> authenticating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4061] device (p2p-dev-wlp1s0): supplicant management interface state: ready -> authenticating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4120] device (wlp1s0): supplicant interface state: authenticating -> associating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4120] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4277] device (wlp1s0): supplicant interface state: associating -> associated Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4278] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> associated Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4435] device (wlp1s0): supplicant interface state: associated -> 4-way handshake Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4435] device (p2p-dev-wlp1s0): supplicant management interface state: associated -> 4-way handshake Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4647] device (wlp1s0): supplicant interface state: 4-way handshake -> completed Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4648] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "HUAWEI-m33t-5G" Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4648] device (p2p-dev-wlp1s0): supplicant management interface state: 4-way handshake -> completed Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4649] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.4653] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Feb 17 00:55:06 ws16-silhavik NetworkManager[5597]: <info>  [1613519706.5089] dhcp4 (wlp1s0): state changed unknown -> expire Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7427] dhcp4 (wlp1s0): option dhcp_lease_time      => '259200' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7428] dhcp4 (wlp1s0): option domain_name_servers  => '192.168.100.1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7428] dhcp4 (wlp1s0): option expiry               => '1613778908' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option ip_address           => '192.168.100.16' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_broadcast_address => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_domain_name => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_domain_name_servers => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_domain_search => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7429] dhcp4 (wlp1s0): option requested_host_name  => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_interface_mtu => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_ms_classless_static_routes => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_nis_domain => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_nis_servers => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7430] dhcp4 (wlp1s0): option requested_ntp_servers => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_rfc3442_classless_static_routes => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_root_path  => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_routers    => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_static_routes => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_subnet_mask => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7431] dhcp4 (wlp1s0): option requested_time_offset => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): option requested_wpad       => '1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): option routers              => '192.168.100.1' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): option subnet_mask          => '255.255.255.0' Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7432] dhcp4 (wlp1s0): state changed expire -> bound Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7491] device (wlp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:08 ws16-silhavik dbus-daemon[1044]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.131' (uid=0 pid=5597 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Feb 17 00:55:08 ws16-silhavik systemd[1]: Starting Network Manager Script Dispatcher Service... Feb 17 00:55:08 ws16-silhavik systemd[1]: Started Network Manager Script Dispatcher Service. Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7817] device (wlp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7819] device (wlp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7824] manager: NetworkManager state is now CONNECTED_LOCAL Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7914] manager: NetworkManager state is now CONNECTED_SITE Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7916] policy: set 'HUAWEI-m33t-5G' (wlp1s0) as default for IPv4 routing and DNS Feb 17 00:55:08 ws16-silhavik NetworkManager[5597]: <info>  [1613519708.7922] device (wlp1s0): Activation: successful, device activated. Feb 17 00:55:09 ws16-silhavik NetworkManager[5597]: <info>  [1613519709.4119] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 17 00:55:09 ws16-silhavik whoopsie[1720]: [00:55:09] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/56 Feb 17 00:55:09 ws16-silhavik whoopsie[1720]: [00:55:09] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/56 Feb 17 00:55:09 ws16-silhavik whoopsie[1720]: [00:55:09] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/56 Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.0706] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.0724] policy: set 'HUAWEI-m33t-5G' (wlp1s0) as default for IPv6 routing and DNS Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.1438] dhcp6 (wlp1s0): option dhcp6_name_servers   => 'fe80::1' Feb 17 00:55:12 ws16-silhavik NetworkManager[5597]: <info>  [1613519712.1439] dhcp6 (wlp1s0): state changed unknown -> bound **Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <warn>  [1613519717.8735] sup-iface[0x55e24cba1930,wlp1s0]: connection disconnected (reason -4)** Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.8952] device (wlp1s0): supplicant interface state: completed -> disconnected Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.8953] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> disconnected Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.9788] device (wlp1s0): supplicant interface state: disconnected -> scanning Feb 17 00:55:17 ws16-silhavik NetworkManager[5597]: <info>  [1613519717.9789] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning Feb 17 00:55:22 ws16-silhavik systemd[1]: NetworkManager-dispatcher.service: Succeeded. Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <warn>  [1613519733.0658] device (wlp1s0): link timed out. Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.0692] device (wlp1s0): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed') Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.0698] manager: NetworkManager state is now DISCONNECTED Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <warn>  [1613519733.0705] device (wlp1s0): Activation: failed for connection 'HUAWEI-m33t-5G' Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.0712] device (wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 17 00:55:33 ws16-silhavik dbus-daemon[1044]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.131' (uid=0 pid=5597 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Feb 17 00:55:33 ws16-silhavik systemd[1]: Starting Network Manager Script Dispatcher Service... **Feb 17 00:55:33 ws16-silhavik org.kde.kdeconnect.daemon.desktop[2687]: "No such interface xe2x80x9corg.freedesktop.DBus.Propertiesxe2x80x9d on object at path** /org/freedesktop/NetworkManager/ActiveConnection/56" Feb 17 00:55:33 ws16-silhavik systemd[1]: Started Network Manager Script Dispatcher Service. Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1068] dhcp4 (wlp1s0): canceled DHCP transaction Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1068] dhcp4 (wlp1s0): state changed bound -> done Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1070] dhcp6 (wlp1s0): canceled DHCP transaction Feb 17 00:55:33 ws16-silhavik NetworkManager[5597]: <info>  [1613519733.1070] dhcp6 (wlp1s0): state changed bound -> done Feb 17 00:55:37 ws16-silhavik NetworkManager[5597]: <info>  [1613519737.1337] device (wlp1s0): supplicant interface state: scanning -> inactive Feb 17 00:55:37 ws16-silhavik NetworkManager[5597]: <info>  [1613519737.1341] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> inactive 

I think that could be a problem with some interface or something else. It works properly from any other devices (iPhones, mac) but the only problem is with my Dell with Ubuntu 20.04.

I don't know if it is related but every time I tried to connect to wifi other devices lost connection for a couple of minutes. It looks like my attempt restarts the wifi adapter. The same thing happened when I tried wired connection.

Thank you for any suggestion.

        

Lista de respuestas

0
 
vote

La información agregada sobre cómo otros dispositivos pueden conectarse al punto de acceso inalámbrico, sin embargo, su (Dell) con Ubuntu no puede fue muy útil. Esto podría ser debido a un par de razones: se podría ser que el canal está en uso pesado para la red en la que desea conectarse, el otro sería defectuoso /etc/networkmanager/networkmanager.conf usando (configurado como) Supplicante WPA en lugar de IWD.


1. El SSID que está tratando de conectarse con demasiados usuarios en esa configuración de canal en particular y hay interferencia de otros puntos de acceso inalámbrico.

Puede encontrar esto escribiendo escribiendo:
sudo nmcli dev wifi list

Esto le permitirá observar el canal establecido de varias redes y la intensidad de la señal. < br />
2. por cualquier motivo que el administrador de la red en su configuración no pudo hacerlo bien con WPA-Supplicant y, en lugar de eso, necesita IWD.

Primera instalación iwd con sudo apt-get update && sudo apt-get install iwd

Garantizar la conexión al servicio por
ABCDEFGHIJKLMNABCDEFGHIJKLMN4

ABCDEFGHIJKLMNABCDEFGHIJKLMN5

Siguiente Abrir ABCDEFGHIJKLMNABCDEFGHIJKLMN6 y Agregar Después de un reinicio, esto producirá una conexión positiva si se guardaron todos los cambios. Si no, también podría haber algún parámetro de administrador de red que debe modificarse en ese mismo archivo que evita la conexión.

 

The added information about how other devices can connect to the wireless access point however your (Dell) with Ubuntu cannot was very helpful. This could be because of a couple reasons however: One could be that the Channel is in heavy use for the Network you want to connect on, the other would be faulty /etc/NetworkManager/NetworkManager.conf using (configured as) wpa-supplicant instead of iwd.


1. The SSID you are trying to connect to has too many users on that particular channel setup and there is interference from other wireless access points.

You can find this out by typing:
sudo nmcli dev wifi list

This will allow you to observe set channel of various networks and signal strength.

2. For whatever reason the Network-Manager on your setup could not do well with wpa-supplicant and instead needs iwd instead.

First install iwd with sudo apt-get update && sudo apt-get install iwd

then ensure connection to the service by
sudo systemctl enable iwd.service

sudo systemctl start iwd.service

Next open /etc/NetworkManager/NetworkManager.conf and add wifi.backend=iwd to the [DEVICES] section.
After a reboot this will yield a positive connection if all changes were saved. If not there could also be some Network-Manager parameter that needs to be modified in that same file that prevents connection.

 
 

Relacionados problema

0  En Ubuntu 16.04 Conexión por cable que pierde Internet después de un tiempo y necesita volver a conectarse  ( In ubuntu 16 04 wired connection losing the internet after a while and need to r ) 
Estoy usando Ubuntu 16.04 LTS y todo se actualiza y se actualiza en mi sistema. Pero cuando estoy usando Internet con Conexión por cable ¡perderé Intern...

3  ¿Alguno de los complementos VPN de NetworkManager admite IPv6?  ( Do any networkmanager vpn plugins support ipv6 ) 
¿Alguno de los complementos VPN de NetworkManager admite IPv6? Los dos que he intentado hasta ahora (PPTP y Strongswan) solo muestran una pestaña "IPv4". ¿Hab...

0  ¿Cómo conseguir mi eth0 arriba y correr? He intentado todo, pero ninguno, trae esto  ( How to get my eth0 up and running i have tried all but none bring this up ) 
Ubuntu 11.04. ¿Por qué se reduce el Eth0, no hay herramientas ni script para traerlo? Intenté varias maneras, pero ninguna trabajó. ¿Alguna idea? 1) VIM /...

2  Problemas inalámbricos en 16.04 con RTL8821AE, ASUS E202S  ( Wireless issues on 16 04 with rtl8821ae asus e202s ) 
Recientemente he comprado una computadora de escritorio ASUS E202S e intentó instalar Ubuntu 16.04 en él. No tuve problemas para instalar o hacer un Dualboot ...

5  DNSMASQ - ¿Por qué está funcionando?  ( Dnsmasq why is this running ) 
Entonces, estaba asomando a HTOP, y miré qué procesos se estaban ejecutando. Por alguna razón, se está ejecutando un proceso llamado DNSMASQ. El comando compl...

11  Ubuntu 18.04 LTS PROBLEMAS DE WIFI  ( Ubuntu 18 04 lts wifi problems ) 
Desde que compré una nueva computadora portátil, durante ya dos años, tengo problemas infinitos con WiFi en mi computadora portátil (Lenovo Y50-70) en Ubuntu ...

8  ¿Cómo puedo hacer que el administrador de red se conecte automáticamente a una nueva red?  ( How can i make the network manager automatically connect to a new network ) 
Si mi computadora está encendida sin una conexión de red (por ejemplo, el enrutador se reinicia, el cable de red está desenchufado, etc.), no se conectará en ...

1  Falló la verificación de la conexión de NMCLI  ( Nmcli connection verification failed ) 
Pegaré la secuencia de comandos que estoy tratando de ejecutar para configurar el escritorio Ubuntu 18.04 NetworkManager de acuerdo con la respuesta En esta ...

10  ¿Por qué Network-Manager comienza en el arranque?  ( Why doesnt network manager start at boot ) 
Creo que esto comenzó a suceder hace un par de meses cuando actualicé de 10.04 a 12.04. Cada vez que se reinicie, el administrador de red no se inicia. Teng...

40  ¿Dónde están guardados los archivos de configuración de VPN importados por Administrador de red?  ( Where are vpn configuration files imported by network manager saved ) 
He importado un archivo de configuración de OpenVPN que se comporta de manera diferente al intentar conectarse desde el Administrador de red y la línea de com...




© 2022 respuesta.top Reservados todos los derechos. Centro de preguntas y respuestas reservados todos los derechos