staging.inyokaproject.org

Wlan Hotspot nach Hardwarewechsel auf PI400

Status: Ungelöst | Ubuntu-Version: Ubuntu 22.04 (Jammy Jellyfish)
Antworten |

ja

Anmeldungsdatum:
30. Juli 2022

Beiträge: 23

Hallo, ich habe ein Problem mit dem Wlan Hotspot im Networkmanager nach einem Hardwarewechsel. Kann mich nicht verbinden. Hier die Ausgabe des kaputten:

root@raspberrypi:/etc# egrep -i 'wlan|firm|reason' /var/log/syslog
May  4 15:46:03 raspberrypi avahi-daemon[7853]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.42.0.1.
May  4 15:46:03 raspberrypi avahi-daemon[7853]: New relevant interface wlan0.IPv4 for mDNS.
May  4 15:46:03 raspberrypi avahi-daemon[7853]: Registering new address record for 10.42.0.1 on wlan0.IPv4.
May  4 15:46:42 raspberrypi NetworkManager[1318]: <info>  [1683208002.5416] device (wlan0): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
May  4 15:46:42 raspberrypi wpa_supplicant[1367]: wlan0: interface state ENABLED->DISABLED
May  4 15:46:42 raspberrypi wpa_supplicant[1367]: wlan0: AP-DISABLED 
May  4 15:46:43 raspberrypi wpa_supplicant[1367]: wlan0: CTRL-EVENT-DISCONNECTED bssid=e4:5f:01:56:67:37 reason=3 locally_generated=1
May  4 15:46:43 raspberrypi wpa_supplicant[1367]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
May  4 15:46:43 raspberrypi NetworkManager[1318]: <info>  [1683208003.0751] device (wlan0): supplicant interface state: completed -> disconnected
May  4 15:46:43 raspberrypi NetworkManager[1318]: <info>  [1683208003.0752] device (p2p-dev-wlan0): supplicant management interface state: completed -> disconnected
May  4 15:46:43 raspberrypi NetworkManager[1318]: <info>  [1683208003.0754] device (wlan0): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
May  4 15:46:43 raspberrypi wpa_supplicant[1367]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May  4 15:46:43 raspberrypi avahi-daemon[7853]: Withdrawing address record for 10.42.0.1 on wlan0.
May  4 15:46:43 raspberrypi avahi-daemon[7853]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.42.0.1.
May  4 15:46:43 raspberrypi avahi-daemon[7853]: Interface wlan0.IPv4 no longer relevant for mDNS.
May  4 15:46:43 raspberrypi wpa_supplicant[1367]: wlan0: Reject scan trigger since one is already pending
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.6631] device (wlan0): Activation: starting connection 'test' (aa393fd4-7a8d-4902-9add-ee1e6c7ead12)
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.6645] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.6666] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.6843] device (wlan0): Activation: (wifi) access point 'test' has security, but secrets are required.
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.6845] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.6913] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.6970] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May  4 15:46:54 raspberrypi NetworkManager[1318]: <info>  [1683208014.7027] device (wlan0): Activation: (wifi) connection 'test' has security, and secrets exist.  No new secrets needed.
May  4 15:46:55 raspberrypi wpa_supplicant[1367]: wlan0: interface state UNINITIALIZED->ENABLED
May  4 15:46:55 raspberrypi wpa_supplicant[1367]: wlan0: AP-ENABLED 
May  4 15:46:55 raspberrypi wpa_supplicant[1367]: wlan0: CTRL-EVENT-CONNECTED - Connection to e4:5f:01:56:67:37 completed [id=0 id_str=]
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.1399] device (wlan0): supplicant interface state: disconnected -> completed
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.1401] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Started Wi-Fi Hotspot "test"
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.1402] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> completed
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.1407] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
May  4 15:46:55 raspberrypi avahi-daemon[7853]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.42.0.1.
May  4 15:46:55 raspberrypi avahi-daemon[7853]: New relevant interface wlan0.IPv4 for mDNS.
May  4 15:46:55 raspberrypi avahi-daemon[7853]: Registering new address record for 10.42.0.1 on wlan0.IPv4.
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.3069] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May  4 15:46:55 raspberrypi dnsmasq[8021]: chown of PID file /run/nm-dnsmasq-wlan0.pid failed: Vorgang nicht zulässig
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.3873] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.3881] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
May  4 15:46:55 raspberrypi NetworkManager[1318]: <info>  [1683208015.3913] device (wlan0): Activation: successful, device activated.

Und hier auf dem zweiten wo es geht:

root@studiopi2:/etc# egrep -i 'wlan|firm|reason' /var/log/syslog
May  4 15:31:38 PiStudio2 NetworkManager[703]: <info>  [1683207098.9983] device (wlan0): Activation: starting connection 'Hotspot' (bd5e6841-2272-416a-9c02-61ed60f56dcb)
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207098.9996] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.0022] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.0033] device (wlan0): Activation: (wifi) access point 'Hotspot' has security, but secrets are required.
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.0034] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.0334] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.0360] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.0383] device (wlan0): Activation: (wifi) connection 'Hotspot' has security, and secrets exist.  No new secrets needed.
May  4 15:31:39 PiStudio2 kernel: [  564.771487] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.4675] device (wlan0): supplicant interface state: disconnected -> completed
May  4 15:31:39 PiStudio2 wpa_supplicant[749]: wlan0: interface state UNINITIALIZED->ENABLED
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.4676] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Started Wi-Fi Hotspot "PiStudio2"
May  4 15:31:39 PiStudio2 wpa_supplicant[749]: wlan0: AP-ENABLED 
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.4677] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> completed
May  4 15:31:39 PiStudio2 wpa_supplicant[749]: wlan0: CTRL-EVENT-CONNECTED - Connection to e4:5f:01:49:ae:e4 completed [id=0 id_str=]
May  4 15:31:39 PiStudio2 NetworkManager[703]: <info>  [1683207099.4682] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
May  4 15:31:40 PiStudio2 avahi-daemon[706]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.42.0.1.
May  4 15:31:40 PiStudio2 avahi-daemon[706]: New relevant interface wlan0.IPv4 for mDNS.
May  4 15:31:40 PiStudio2 avahi-daemon[706]: Registering new address record for 10.42.0.1 on wlan0.IPv4.
May  4 15:31:40 PiStudio2 NetworkManager[703]: <info>  [1683207100.0699] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May  4 15:31:40 PiStudio2 avahi-daemon[706]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::cf12:e06a:3e61:9a22.
May  4 15:31:40 PiStudio2 avahi-daemon[706]: New relevant interface wlan0.IPv6 for mDNS.
May  4 15:31:40 PiStudio2 avahi-daemon[706]: Registering new address record for fe80::cf12:e06a:3e61:9a22 on wlan0.*.
May  4 15:31:40 PiStudio2 dnsmasq[9464]: chown of PID file /run/nm-dnsmasq-wlan0.pid failed: Operation not permitted
May  4 15:31:40 PiStudio2 NetworkManager[703]: <info>  [1683207100.1225] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
May  4 15:31:40 PiStudio2 NetworkManager[703]: <info>  [1683207100.1237] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
May  4 15:31:40 PiStudio2 NetworkManager[703]: <info>  [1683207100.1273] device (wlan0): Activation: successful, device activated.
May  4 15:32:20 PiStudio2 wpa_supplicant[749]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May  4 15:32:20 PiStudio2 wpa_supplicant[749]: wlan0: AP-STA-CONNECTED 4a:ab:4c:a4:fa:b2
May  4 15:32:20 PiStudio2 wpa_supplicant[749]: wlan0: EAPOL-4WAY-HS-COMPLETED 4a:ab:4c:a4:fa:b2
May  4 15:32:23 PiStudio2 dnsmasq-dhcp[9464]: DHCPDISCOVER(wlan0) 4a:ab:4c:a4:fa:b2 
May  4 15:32:23 PiStudio2 dnsmasq-dhcp[9464]: DHCPOFFER(wlan0) 10.42.0.70 4a:ab:4c:a4:fa:b2 
May  4 15:32:23 PiStudio2 dnsmasq-dhcp[9464]: DHCPDISCOVER(wlan0) 4a:ab:4c:a4:fa:b2 
May  4 15:32:23 PiStudio2 dnsmasq-dhcp[9464]: DHCPOFFER(wlan0) 10.42.0.70 4a:ab:4c:a4:fa:b2 
May  4 15:32:23 PiStudio2 dnsmasq-dhcp[9464]: DHCPREQUEST(wlan0) 10.42.0.70 4a:ab:4c:a4:fa:b2 

die Dateien unter /etc/NetworkManager sehen gleich aus. Der Hardwarewechsel bezieht sich auf: von einem Pi400 auf einen anderen PI400. Hat jmd eine Idee?

Moderiert von kB:

Aus dem Forum „Netzwerk und Internetzugang einrichten“ in einen besser passenden Forenbereich verschoben. Bitte beachte die als wichtig markierten Themen („Welche Themen gehören hier her und welche nicht?“) im jeweiligen Forum! Danke.

kB Team-Icon

Supporter, Wikiteam
Avatar von kB

Anmeldungsdatum:
4. Oktober 2007

Beiträge: 7816

Du kannst dem zweiten Zugangspunkt nicht dieselbe IP-Adresse geben wie bereits für den ersten Zugangspunkt vergeben und auch der DHCP-Server des zweiten Zugangspunktes muss einen anderen Adressbereich verwalten als der DHCP-Server des ersten Zugangspunktes.

ja

(Themenstarter)

Anmeldungsdatum:
30. Juli 2022

Beiträge: 23

kB schrieb:

Du kannst dem zweiten Zugangspunkt nicht dieselbe IP-Adresse geben wie bereits für den ersten Zugangspunkt vergeben und auch der DHCP-Server des zweiten Zugangspunktes muss einen anderen Adressbereich verwalten als der DHCP-Server des ersten Zugangspunktes.

Hallo, danke fürs Verschieben und antworten. Der zweite Zugangspunkt ist auf einem zweiten Gerät damit ich einen Vergleich der Protokolldateien bzw. Einstellungen finden kann. Der Zugangspunkt hat lange funktioniert bis ich das gleiche System auf einem anderen Raspi gestartet habe. Hat also iwas mit der Hardware bzw. macadresse zu tun. Ich habe sowas gesucht wie cache löschen oder reset des Networkmanager weil das Löschen der Config Datei nicht hilft.

Antworten |