☰

NetworkManagerは引き続き接続され、切断されます。この問題をどのように解決できますか？

tag-icon • tag-icon networkmanager
NetworkManagerは引き続き接続され、切断されます。この問題をどのように解決できますか？

私は次の最新バージョンと最新のシステムを使用しています：Archカーネル5.6.4-arch1-1、Openbox 3.6.1、NetworkManager 1.24.0-1、wpa_supplicant v2.9。

私は3つの地理的な場所でラップトップを使用しています。各場所には、一意のSSIDに接続できる一意のWi-Fiネットワークがあります。ノートブックはWPA and WPA2 Personalプロトコルを使用して3つの場所すべてに接続します。

3つの場所のうちの2つでは、私のラップトップWiFiは常に問題なく迅速かつスムーズで完全に接続されています。

3番目の場所（3番目の場所のみ）私のラップトップは、次の手順で説明するように、10秒ごとにWiFi接続を切断して再接続するループを続けます。

  1. Web検索で5秒
  2. ネットワーク接続に1秒
  3. 4秒、切断
  4. 1に行って再起動してください...

上記のリストで説明したように、3番目の場所でインターネットへのネットワーク接続を取得できましたが、約10秒に1回でした。

これにより、第三の場所で働くことが不可能になりました。

3番目の場所では、ルーターは他のすべてのデバイスに完全なWiFiを提供します。そうすれば、ルーターには問題がないようです。

nm-applettint2 taskbarGUIを使用して3番目の場所のネットワーク管理者接続プロファイルを削除し、正しいパスワードなどを使用して3番目の場所SSIDに再接続しようとしました。しかし、そうすると問題は変わりません。

sudo killall -STOP NetworkManager ループを正常に停止し、接続を維持するために、上記の2段階の途中でこのコマンドラインを使用しましたが、動作は停止しました。

これで、イーサネットケーブルがラップトップに接続され、ノートブックの側面の実際のラップトップWiFiスイッチがオフになります。付属のイーサネットケーブルでインターネットに接続しましたが、10秒間に5秒間接続が切断されました。つまり、WiFiのように接続をオン/オフするプロセスを繰り返します。繰り返しますが、これは3番目の位置でのみ発生します。一度接続すると、sudo killall -STOP NetworkManager ループを停止するために接続が確立され、再び使用されます。

これは、3番目の場所のラップトップWi-Fi設定に関連しているようです。

ADDED：システムが切断されたときにシステムログから出力期間を次のように追加しました。

コマンドはjournalctl -ef次の出力を生成します。

network is down. This is the end of last connection / disconnection cycle and the beginning of the next

May 23 13:46:52 t430 dhcpcd[5050]: ps_bpf_recvbpf: Network is down

preamble

May 23 13:46:52 t430 kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
May 23 13:46:52 t430 kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0

registering ipv4 address

May 23 13:46:52 t430 avahi-daemon[451]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.106.
May 23 13:46:52 t430 avahi-daemon[451]: New relevant interface wlp3s0.IPv4 for mDNS.
May 23 13:46:52 t430 avahi-daemon[451]: Registering new address record for 192.168.1.106 on wlp3s0.IPv4.

withdrawing ipv4 address

May 23 13:46:52 t430 avahi-daemon[451]: Withdrawing address record for 192.168.1.106 on wlp3s0.
May 23 13:46:52 t430 avahi-daemon[451]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.106.
May 23 13:46:52 t430 avahi-daemon[451]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
May 23 13:46:52 t430 dhcpcd[492]: wlp3s0: deleting route to 192.168.1.0/24
May 23 13:46:52 t430 dhcpcd[492]: wlp3s0: deleting default route via 192.168.1.1
May 23 13:46:52 t430 NetworkManager[454]: <warn>  [1590238012.8707] device (wlp3s0): Activation: failed for connection 'datastream5'

registering ipv4 address again

May 23 13:46:52 t430 avahi-daemon[451]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.106.
May 23 13:46:52 t430 wpa_supplicant[570]: wlp3s0: Reject scan trigger since one is already pending
May 23 13:46:52 t430 NetworkManager[454]: <info>  [1590238012.8775] device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

May 23 13:46:52 t430 avahi-daemon[451]: New relevant interface wlp3s0.IPv4 for mDNS.
May 23 13:46:52 t430 avahi-daemon[451]: Registering new address record for 192.168.1.106 on wlp3s0.IPv4.
May 23 13:46:52 t430 NetworkManager[454]: <info>  [1590238012.8778] dhcp4 (wlp3s0): canceled DHCP transaction
May 23 13:46:52 t430 wpa_supplicant[570]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 23 13:46:52 t430 NetworkManager[454]: <info>  [1590238012.8778] dhcp4 (wlp3s0): state changed bound -> done

registering ipv6 address

May 23 13:46:52 t430 avahi-daemon[451]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::fd81:7780:6410:e759.
May 23 13:46:52 t430 avahi-daemon[451]: New relevant interface wlp3s0.IPv6 for mDNS.
May 23 13:46:52 t430 avahi-daemon[451]: Registering new address record for fe80::fd81:7780:6410:e759 on wlp3s0.*.

May 23 13:46:52 t430 avahi-daemon[451]: Withdrawing address record for fe80::fd81:7780:6410:e759 on wlp3s0.
May 23 13:46:52 t430 NetworkManager[454]: <info>  [1590238012.8822] device (wlp3s0): supplicant interface state: completed -> scanning
May 23 13:46:52 t430 avahi-daemon[451]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::fd81:7780:6410:e759.
May 23 13:46:52 t430 avahi-daemon[451]: Interface wlp3s0.IPv6 no longer relevant for mDNS.

`withdrawing ipv4 address`
May 23 13:46:52 t430 avahi-daemon[451]: Withdrawing address record for 192.168.1.106 on wlp3s0.
May 23 13:46:52 t430 avahi-daemon[451]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.106.
May 23 13:46:52 t430 avahi-daemon[451]: Interface wlp3s0.IPv4 no longer relevant for mDNS.

new ipv4 mac address

May 23 13:46:52 t430 dhcpcd[492]: wlp3s0: new hardware address: ca:b3:01:7c:20:73

disconnected

May 23 13:46:56 t430 NetworkManager[454]: <info>  [1590238016.0852] device (wlp3s0): supplicant interface state: scanning -> disconnected

NetworkManager succeeds at something

May 23 13:47:00 t430 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
May 23 13:47:00 t430 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

May 23 13:47:00 t430 kernel: audit: type=1131 audit(1590238020.888:153): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.4312] policy: auto-activating connection 'datastream5' (4c200721-a84a-4619-9d08-319531f8c338)
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.4322] device (wlp3s0): Activation: starting connection 'datastream5' (4c200721-a84a-4619-9d08-319531f8c338)
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.4324] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.4335] manager: NetworkManager state is now CONNECTING

May 23 13:47:02 t430 dhcpcd[492]: wlp3s0: new hardware address: 6c:88:14:62:84:3c
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.4486] device (wlp3s0): set-hw-addr: reset MAC address to 6C:88:14:62:84:3C (preserve)

scanning for connection

May 23 13:47:02 t430 kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
May 23 13:47:02 t430 kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0

May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8441] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8450] device (wlp3s0): Activation: (wifi) access point 'datastream5' has security, but secrets are required.
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8451] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8491] device (wlp3s0): supplicant interface state: disconnected -> interface_disabled
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8512] device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8519] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8525] device (wlp3s0): Activation: (wifi) connection 'datastream5' has security, and secrets exist.  No new secrets needed.
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8526] Config: added 'ssid' value 'datastream5'
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8526] Config: added 'scan_ssid' value '1'
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8526] Config: added 'bgscan' value 'simple:30:-70:86400'
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8527] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8527] Config: added 'auth_alg' value 'OPEN'
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8527] Config: added 'psk' value '<hidden>'
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8794] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
May 23 13:47:02 t430 NetworkManager[454]: <info>  [1590238022.8920] device (wlp3s0): supplicant interface state: inactive -> scanning
May 23 13:47:06 t430 wpa_supplicant[570]: wlp3s0: SME: Trying to authenticate with 70:4f:57:97:52:06 (SSID='datastream5' freq=2447 MHz)
May 23 13:47:06 t430 kernel: wlp3s0: authenticate with 70:4f:57:97:52:06
May 23 13:47:06 t430 kernel: wlp3s0: send auth to 70:4f:57:97:52:06 (try 1/3)
May 23 13:47:06 t430 kernel: wlp3s0: authenticated
May 23 13:47:06 t430 kernel: wlp3s0: associate with 70:4f:57:97:52:06 (try 1/3)
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1197] device (wlp3s0): supplicant interface state: scanning -> authenticating
May 23 13:47:06 t430 wpa_supplicant[570]: wlp3s0: Trying to associate with 70:4f:57:97:52:06 (SSID='datastream5' freq=2447 MHz)
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1226] device (wlp3s0): supplicant interface state: authenticating -> associating
May 23 13:47:06 t430 kernel: wlp3s0: RX AssocResp from 70:4f:57:97:52:06 (capab=0x1011 status=0 aid=3)
May 23 13:47:06 t430 wpa_supplicant[570]: wlp3s0: Associated with 70:4f:57:97:52:06
May 23 13:47:06 t430 wpa_supplicant[570]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 23 13:47:06 t430 kernel: wlp3s0: associated
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1533] device (wlp3s0): supplicant interface state: associating -> 4way_handshake
May 23 13:47:06 t430 wpa_supplicant[570]: wlp3s0: WPA: Key negotiation completed with 70:4f:57:97:52:06 [PTK=CCMP GTK=TKIP]
May 23 13:47:06 t430 wpa_supplicant[570]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 70:4f:57:97:52:06 completed [id=0 id_str=]
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: carrier acquired
May 23 13:47:06 t430 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1680] device (wlp3s0): supplicant interface state: 4way_handshake -> completed

#########################################################################################################

May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1681] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "datastream5"


May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1683] device (wlp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1688] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
May 23 13:47:06 t430 avahi-daemon[451]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::fd81:7780:6410:e759.
May 23 13:47:06 t430 avahi-daemon[451]: New relevant interface wlp3s0.IPv6 for mDNS.
May 23 13:47:06 t430 avahi-daemon[451]: Registering new address record for fe80::fd81:7780:6410:e759 on wlp3s0.*.
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: IAID 14:62:84:3c
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: adding address fe80::c685:c3d0:8b05:a9e5
May 23 13:47:06 t430 avahi-daemon[451]: Registering new address record for fe80::c685:c3d0:8b05:a9e5 on wlp3s0.*.
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1957] dhcp4 (wlp3s0): option dhcp_lease_time      => '86400'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option domain_name_servers  => '192.168.1.1 0.0.0.0'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option expiry               => '1590324426'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option ip_address           => '192.168.1.106'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option requested_broadcast_address => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option requested_domain_name => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option requested_domain_name_servers => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option requested_domain_search => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1958] dhcp4 (wlp3s0): option requested_host_name  => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_interface_mtu => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_ms_classless_static_routes => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_nis_domain => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_nis_servers => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_ntp_servers => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_rfc3442_classless_static_routes => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_root_path  => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1959] dhcp4 (wlp3s0): option requested_routers    => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1960] dhcp4 (wlp3s0): option requested_static_routes => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1960] dhcp4 (wlp3s0): option requested_subnet_mask => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1960] dhcp4 (wlp3s0): option requested_time_offset => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1960] dhcp4 (wlp3s0): option requested_wpad       => '1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1960] dhcp4 (wlp3s0): option routers              => '192.168.1.1'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1960] dhcp4 (wlp3s0): option subnet_mask          => '255.255.255.0'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1960] dhcp4 (wlp3s0): state changed unknown -> bound
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.1975] device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May 23 13:47:06 t430 avahi-daemon[451]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.106.
May 23 13:47:06 t430 avahi-daemon[451]: New relevant interface wlp3s0.IPv4 for mDNS.
May 23 13:47:06 t430 avahi-daemon[451]: Registering new address record for 192.168.1.106 on wlp3s0.IPv4.
May 23 13:47:06 t430 dbus-daemon[453]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=454 comm="/usr/bin/NetworkManager --no-daemon ")
May 23 13:47:06 t430 systemd[1]: Condition check resulted in First Boot Wizard being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in Create System Users being skipped.
May 23 13:47:06 t430 systemd[1]: Condition check resulted in Update is Completed being skipped.
May 23 13:47:06 t430 systemd[1]: Starting Network Manager Script Dispatcher Service...
May 23 13:47:06 t430 dbus-daemon[453]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 23 13:47:06 t430 systemd[1]: Started Network Manager Script Dispatcher Service.
May 23 13:47:06 t430 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.2125] device (wlp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.2128] device (wlp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.2132] manager: NetworkManager state is now CONNECTED_LOCAL
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.2143] manager: NetworkManager state is now CONNECTED_SITE
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.2145] policy: set 'datastream5' (wlp3s0) as default for IPv4 routing and DNS
May 23 13:47:06 t430 kernel: audit: type=1130 audit(1590238026.208:154): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 23 13:47:06 t430 dunst[1185]: WARNING: No icon found in path: 'nm-signal-75'
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.2232] device (wlp3s0): Activation: successful, device activated.
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: rebinding lease of 192.168.1.106
May 23 13:47:06 t430 NetworkManager[454]: <info>  [1590238026.3305] manager: NetworkManager state is now CONNECTED_GLOBAL
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: leased 192.168.1.106 for 86400 seconds
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: adding route to 192.168.1.0/24
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: adding default route via 192.168.1.1
May 23 13:47:06 t430 systemd[1]: systemd-hostnamed.service: Succeeded.
May 23 13:47:06 t430 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 23 13:47:06 t430 kernel: audit: type=1131 audit(1590238026.351:155): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 23 13:47:06 t430 audit: AUDIT1334 prog-id=19 op=UNLOAD
May 23 13:47:06 t430 audit: AUDIT1334 prog-id=18 op=UNLOAD
May 23 13:47:06 t430 kernel: audit: type=1334 audit(1590238026.391:156): prog-id=19 op=UNLOAD
May 23 13:47:06 t430 kernel: audit: type=1334 audit(1590238026.391:157): prog-id=18 op=UNLOAD
May 23 13:47:06 t430 wpa_supplicant[570]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=13000
May 23 13:47:06 t430 dhcpcd[492]: wlp3s0: soliciting an IPv6 router
May 23 13:47:08 t430 dhcpcd[492]: wlp3s0: Router Advertisement from fe80::724f:57ff:fe97:5206
May 23 13:47:08 t430 NetworkManager[454]: <info>  [1590238028.0508] dhcp6 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
May 23 13:47:08 t430 NetworkManager[454]: <warn>  [1590238028.0510] device (wlp3s0): failure to start DHCPv6: failed to start client: Address already in use
May 23 13:47:08 t430 NetworkManager[454]: <info>  [1590238028.0510] device (wlp3s0): state change: activated -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')


May 23 13:47:08 t430 NetworkManager[454]: <info>  [1590238028.0526] manager: NetworkManager state is now DISCONNECTED
May 23 13:47:08 t430 kernel: wlp3s0: deauthenticating from 70:4f:57:97:52:06 by local choice (Reason: 3=DEAUTH_LEAVING)
May 23 13:47:08 t430 dunst[1185]: WARNING: No icon found in path: 'nm-no-connection'
May 23 13:47:08 t430 dhcpcd[492]: wlp3s0: soliciting a DHCPv6 lease
May 23 13:47:08 t430 wpa_supplicant[570]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=70:4f:57:97:52:06 reason=3 locally_generated=1
May 23 13:47:08 t430 dhcpcd[492]: wlp3s0: carrier lost



May 23 13:47:08 t430 avahi-daemon[451]: Interface wlp3s0.IPv6 no longer relevant for mDNS.
May 23 13:47:08 t430 avahi-daemon[451]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::fd81:7780:6410:e759.
May 23 13:47:08 t430 avahi-daemon[451]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
May 23 13:47:08 t430 avahi-daemon[451]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.106.
May 23 13:47:08 t430 NetworkManager[454]: <info>  [1590238028.0927] device (wlp3s0): set-hw-addr: set MAC address to 66:51:DB:82:D6:15 (scanning)
May 23 13:47:08 t430 avahi-daemon[451]: Withdrawing address record for fe80::c685:c3d0:8b05:a9e5 on wlp3s0.
May 23 13:47:08 t430 avahi-daemon[451]: Withdrawing address record for fe80::fd81:7780:6410:e759 on wlp3s0.
May 23 13:47:08 t430 avahi-daemon[451]: Withdrawing address record for 192.168.1.106 on wlp3s0.


May 23 13:47:08 t430 dhcpcd[5441]: ps_bpf_recvbpf: Network is down

答え1

上記の質問に対する@eblockのコメントは、システムログを調べることを提案しました。

私はこのタスクを実行し、上記のように問題のある3番目の場所に対する動作する解決策を少なくとも部分的に確認しました。

ネットワーク接続ループが停止し、接続が安定しています。

それでも問題の原因を見つけたという意味ではありませんが、おそらく見つけたでしょう。

これが私の解決策です。

  1. ノートパソコンを再起動し、Wi-Fiネットワーク接続のオン/オフを切り替えます。

  2. ターミナルでは、journalctl -ef上記で説明した接続と切断ステップを介して、システムのライブログ出力ループを入力して観察します。

  3. ログをテキストファイルに出力journalctl -ef > journal_output.txt

  4. このファイルをテキストエディタで開き、vim接続と切断を介して1サイクルに関連する部分のみを識別し、約14秒の情報しか含まれていません。

修正として、上記の質問にこのsyslog出力を追加しました。

この出力では、ルータがipv6アドレスを発行していないか、何らかの理由でラップトップがipv6アドレスを設定できず、NetworkManagerがネットワーク接続を切断したことを確認できました。

この問題は、最近のルーターファームウェアのアップグレードによって引き起こされる可能性がありますが、このネットワーク接続の問題がないほとんど同じソフトウェアがインストールされているのと同じノートブックがあります。さらに、ルータLANの他のデバイスでは、これらのループ接続/切断の問題は発生しません。つまり、この問題はルーターのファームウェアのアップグレード中に発生し始めたようですが、わかりません。

修理する この問題を解決するために、nm-applet3 番目の場所の [ネットワーク管理者の GUI] タブで Wi-Fi 接続とイーサネット ケーブル接続の両方で ipv6 接続を無効にしました。無効にすると、Wi-Fi 接続と有線イーサネット接続の両方が接続と切断を繰り返すことなく、継続的かつ一貫した方法でネットワークに接続されます。

答え2

デバッグ

問題をデバッグするもう1つの方法は、次のように変更してロギングレベルを上げることです/etc/NetworkManager/NetworkManager.conf。

[logging]
level=DEBUG

その後、より良いニュースを得るには、次のコマンドを実行します/var/log/syslog。

sudo systemctl restart NetworkManager

私が管理している4〜5台のUbuntuコンピュータで同じ問題が発生しますが、有線接続があるデスクトップでは発生します。ほとんどのシステムでは、NetworkManagerステータスループは次のメッセージを表示します。

Dec  7 01:36:56 vandebun-home whoopsie[1483]: [01:36:56] offline
Dec  7 01:36:56 vandebun-home dbus-daemon[890]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=891 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Dec  7 01:36:56 vandebun-home systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec  7 01:36:56 vandebun-home dbus-daemon[890]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec  7 01:36:56 vandebun-home systemd[1]: Started Network Manager Script Dispatcher Service.
Dec  7 01:36:57 vandebun-home NetworkManager[891]: <info>  [1638862617.8397] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec  7 01:36:57 vandebun-home whoopsie[1483]: [01:36:57] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Dec  7 01:36:57 vandebun-home whoopsie[1483]: [01:36:57] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Dec  7 01:36:57 vandebun-home whoopsie[1483]: [01:36:57] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Dec  7 01:36:59 vandebun-home whoopsie[1483]: [01:36:59] online
Dec  7 01:37:08 vandebun-home systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec  7 01:45:01 vandebun-home CRON[1667743]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec  7 01:47:17 vandebun-home NetworkManager[891]: <info>  [1638863237.3144] manager: NetworkManager state is now CONNECTED_SITE
Dec  7 01:47:17 vandebun-home whoopsie[1483]: [01:47:17] offline

offline上記のログでは、onlineメッセージとメッセージの違いはwhoopsieわずか数秒です。これらのログで発生する状況を要約するために、NetworkManagerは5分（300秒、参照）ごとに確認をCONNECTIVITY実行します。man NetworkManager.conf接続確認失敗してオフラインになります。その後すぐに別の接続確認を実行し、確認に合格してオンラインに戻ります。これらの特定のログではオンラインに戻るのに数秒しかかかりませんが、他のコンピュータでは数分かかり、問題が発生します。

デバッグロギングを介してNetworkManagerをオフラインにする接続確認中に、以下が表示されます。

Dec  7 14:39:49 vandebun-home gnome-control-c[1709862]: Failed fetch permissions from flatpak permission store: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for location
Dec  7 14:40:17 vandebun-home NetworkManager[1705563]: <debug> [1638909617.4571] ndisc-lndp[0x5634385a0e20,"enp3s0"]: processing libndp events
Dec  7 14:40:20 vandebun-home NetworkManager[1705563]: <debug> [1638909620.1503] connectivity: (tun0,IPv6,142) start request to 'http://connectivity-check.ubuntu.com/' (try resolving 'connectivity-check.ubuntu.com' using systemd-resolved)
Dec  7 14:40:20 vandebun-home NetworkManager[1705563]: <debug> [1638909620.1521] connectivity: (tun0,IPv6,142) can't resolve a name via systemd-resolved: GDBus.Error:org.freedesktop.resolve1.NoNameServers: No appropriate name servers or networks for name found
Dec  7 14:40:20 vandebun-home NetworkManager[1705563]: <debug> [1638909620.3694] connectivity: (tun0,IPv6,142) check completed: LIMITED; check failed: (6) Couldn't resolve host name
Dec  7 14:40:26 vandebun-home NetworkManager[1705563]: <debug> [1638909626.1534] connectivity: (tun0,IPv4,143) skip connectivity check due to no global route configured
Dec  7 14:40:26 vandebun-home NetworkManager[1705563]: <debug> [1638909626.1535] connectivity: (tun0,IPv4,143) check completed: LIMITED; no global route configured
Dec  7 14:41:09 vandebun-home NetworkManager[1705563]: <debug> [1638909669.5394] connectivity: (docker0,IPv6,144) start request to 'http://connectivity-check.ubuntu.com/' (try resolving 'connectivity-check.ubuntu.com' using systemd-resolved)
Dec  7 14:41:09 vandebun-home NetworkManager[1705563]: <debug> [1638909669.5396] connectivity: (enp3s0,IPv6,145) start request to 'http://connectivity-check.ubuntu.com/' (try resolving 'connectivity-check.ubuntu.com' using systemd-resolved)
Dec  7 14:41:09 vandebun-home NetworkManager[1705563]: <debug> [1638909669.5410] connectivity: (docker0,IPv6,144) can't resolve a name via systemd-resolved: GDBus.Error:org.freedesktop.resolve1.NoNameServers: No appropriate name servers or networks for name found
Dec  7 14:41:09 vandebun-home NetworkManager[1705563]: <debug> [1638909669.5509] connectivity: (enp3s0,IPv6,145) can't resolve a name via systemd-resolved: GDBus.Error:org.freedesktop.resolve1.NoSuchRR: 'connectivity-check.ubuntu.com' does not have any RR of the requested type
Dec  7 14:41:09 vandebun-home NetworkManager[1705563]: <debug> [1638909669.9151] connectivity: (docker0,IPv6,144) check completed: LIMITED; check failed: (6) Couldn't resolve host name
Dec  7 14:41:09 vandebun-home NetworkManager[1705563]: <debug> [1638909669.9691] connectivity: (enp3s0,IPv6,145) check completed: LIMITED; check failed: (6) Couldn't resolve host name
Dec  7 14:41:15 vandebun-home NetworkManager[1705563]: <debug> [1638909675.5200] connectivity: (docker0,IPv4,146) skip connectivity check due to no global route configured
Dec  7 14:41:15 vandebun-home NetworkManager[1705563]: <debug> [1638909675.5201] connectivity: (docker0,IPv4,146) check completed: LIMITED; no global route configured
Dec  7 14:43:26 vandebun-home NetworkManager[1705563]: <debug> [1638909806.3332] connectivity: (enp3s0,IPv4,147) start request to 'http://connectivity-check.ubuntu.com/' (try resolving 'connectivity-check.ubuntu.com' using systemd-resolved)

ほとんどのエラーはIPv6これらのログに関連しています。おそらく、あなたのようにすべてのネットワークインターフェイスでIPv6を無効にして問題を解決することができます。

代替ソリューション

別のオプションは、接続確認を無効にすることです。

[connectivity]
interval=0

ラップトップからローミングしていないユーザーの場合は、依存ポータルに触れることができます。これにより、後で IPv6 を単独で動作させることができます。

私の理論は（もちろんわからない）「定期的な」接続確認（マシンがオンラインのときに5分ごとに実行されます）がまだIPv6に対して準備されていないことです。つまり、IPv4接続が十分であることを証明するために、完全性チェックを実行していないようです。 NetworkManagerがオフラインの後に実行される接続チェックは、IPv4（したがってループ）のみを確認します。

関連情報