Neueste Beiträge

#11

FRITZ!Box / Aw: Keine stabile FRITZBOX Ver...

Letzter Beitrag von @tango - 23 Januar 2026, 21:02:42

Hi danke
ich bin inzwischen auch bei

joutnalctl gelandet:

habe mittels

    journalctl -S '2026-01-23 00:21:10' -U '2026-01-23 00:22:04'

das folgende erhalten:
Deinen Hinweis schaue ich mir noch genaujer an.

Code Auswählen Erweitern

Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3233] device (eth0): carrier: link connected
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3238] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3251] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3262] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:14 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3265] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3272] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3276] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3285] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3295] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3334] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3343] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3461] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3506] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3511] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3519] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3526] device (eth0): Activation: successful, device activated.
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3536] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:15 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:17 raspismart3 NetworkManager[586]: <info>  [1769124077.3954] device (eth0): carrier: link connected
Jan 23 00:21:17 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:18 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:24 raspismart3 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4230] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4385] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4386] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4386] dhcp4 (eth0): state changed no lease
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4839] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:21:24 raspismart3 dbus-daemon[528]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=586 comm="/usr/sbin/NetworkManager --no-daemon")
Jan 23 00:21:24 raspismart3 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Jan 23 00:21:24 raspismart3 dbus-daemon[528]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 23 00:21:24 raspismart3 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Jan 23 00:21:32 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7558] device (eth0): carrier: link connected
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7567] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7598] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7628] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7633] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7646] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7655] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7672] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7689] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7735] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7754] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7965] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8056] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8067] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8084] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8098] device (eth0): Activation: successful, device activated.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8121] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:34 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8070] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8305] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8306] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8307] dhcp4 (eth0): state changed no lease
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8849] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0681] device (eth0): carrier: link connected
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0696] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0721] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0742] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0747] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0759] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0766] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0783] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0801] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0848] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0866] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1034] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1131] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1141] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1160] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1174] device (eth0): Activation: successful, device activated.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1196] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:47 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.0934] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1185] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1185] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1186] dhcp4 (eth0): state changed no lease
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1635] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2353] device (eth0): carrier: link connected
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2359] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2372] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2383] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:53 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2386] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2392] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2397] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2407] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2416] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2452] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2462] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2594] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2648] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2653] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2662] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2669] device (eth0): Activation: successful, device activated.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2680] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:54 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2617] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2745] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2746] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2746] dhcp4 (eth0): state changed no lease
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.3396] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4034] device (eth0): carrier: link connected
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4042] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4055] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:22:00 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4066] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4068] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4073] manager: NetworkManager state is now CONNECTING
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4077] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4086] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4095] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4147] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4156] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4264] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4314] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4320] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4329] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4335] device (eth0): Activation: successful, device activated.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4346] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:22:01 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down



#12

FRITZ!Box / Aw: Keine stabile FRITZBOX Ver...

Letzter Beitrag von JoWiemann - 23 Januar 2026, 20:38:13

Da hilft die KI

Übersicht mit KI



+3
Netzwerk-Logs auf einem Raspberry Pi (Linux/Raspberry Pi OS) werden primär über journalctl verwaltet. Die wichtigsten Befehle zur Analyse sind journalctl -u systemd-networkd (Netzwerkstatus) und journalctl -u wpa_supplicant (WLAN). Protokolldateien finden sich unter /var/log/, z.B. für SSH-Verbindungen in /var/log/auth.log. Mit journalctl -f können Logs in Echtzeit verfolgt werden.
Wichtige Befehle und Log-Speicherorte:
Netzwerkdienste: journalctl -u systemd-networkd zeigt Logs zum Netzwerkstart und IP-Vergabe.
WLAN (WiFi): journalctl -u wpa_supplicant protokolliert WLAN-Verbindungen, -Abbrüche und Authentifizierungsfehler.
Netzwerk-Schnittstellen: Mit dmesg oder cat /var/log/syslog können Ereignisse zu eth0 (Ethernet) oder wlan0 (WLAN) gefunden werden.
Authentifizierung (SSH): Die Datei /var/log/auth.log speichert Verbindungsversuche und Logins.
Echtzeit-Verfolgung: journalctl -f zeigt neue Einträge sofort an.
Hintergrund:
Log-Verwaltung: Moderne Raspberry Pi OS Versionen (Debian-basiert) nutzen systemd-journald, wodurch Logs im Binärformat gespeichert und über journalctl abgerufen werden.
Netzwerk-Identifikation: Zur Prüfung, ob das Gerät im Netzwerk aktiv ist, hilft ein Blick auf die Zuweisung von IP-Adressen in den Logs.
Die Protokolle helfen bei der Fehlersuche, wenn der Pi keine Verbindung zum Netzwerk aufbaut, das WLAN trennt oder Verbindungsanfragen abgewiesen werden.

#13

FRITZ!Box / Aw: Keine stabile FRITZBOX Ver...

Letzter Beitrag von @tango - 23 Januar 2026, 20:29:57

Hi,
alle Raspis hängen per LAN-Kabel über einen kleinen Renkforce Switch an der Fritzbox.
Solakon über WLAN:

Als WLAN Ereignis finde ich als Besonderheit ca. 7 mal einen Eintrag wie

Code Auswählen Erweitern

23.01.26 17:49:28 [RepeaterGabiszimmer] Eine sehr starke Störquelle wurde auf Kanal 1 (Frequenz 2.412 GHz) erkannt, automatischer Kanalwechsel ausgeführt. [2 Meldungen seit 23.01.26 17:49:28]
Die Zeiten passen eher nicht zu den Eiträgen im FHEM-Log.
Die Internetverbindung wurde wie üblich in der Nacht neu aufgebaut.

Code Auswählen Erweitern

23.01.26 04:43:15 Internetverbindung wurde getrennt.
23.01.26 04:43:15 Internetverbindung IPv6 wurde getrennt, Präfix nicht mehr gültig.
Es erfolgen erheblich mehr als 100 erfolgreiche Anmeldungen vom FHEM Raspi an der Fritzbox mittels IP4 und IP6 unter verschiedenen user-Namen (abhängig vom device-type).
Keine Mißerfolge zu sehen.

Ich brauche einen Tip zu linux wo ich nachsehen soll.

Gerhard

#14

Anfängerfragen / Aw: Katzenklo mit Internetansc...

Letzter Beitrag von Gisbert - 23 Januar 2026, 20:27:17

Hallo pah,

es gibt in Fhem eine lokale Tuya-Anwendung: https://forum.fhem.de/index.php?topic=127441.0
Ich hab einen Luftentfeuchter und 2 schaltbare Steckdosen mit Leistungsmessung damit laufen. Beabsichtigt hatte ich die Integration des Luftbefeuchters in Fhem nicht, da ich beim Kauf davon noch nichts wusste.
Es funktioniert alles. Zwischenzeitlich hatte ich noch 2 schaltbare Steckdosen gekauft. Ob ich die Integration von Tuya in Fhem empfehlen kann - eher nicht. Es ist doch arg kompliziert. Jedenfalls plane ich keine weiteren Geräte mit Tuya anzuschaffen.

Viele Grüße Gisbert

#15

Solaranlagen / Aw: Anbindung Solakon One mit ...

Letzter Beitrag von nitrogen75 - 23 Januar 2026, 20:23:52

Hallo,
ein Zwischenstand von mir:
Leider tauchen bei mir keine Readings auf. Ich musste ohnehin die Definition anpassen, nach der Adresse noch ein "-reading" hinzu. Ein anderes Gerät läuft mit nahezu identischer Definition problemlos.
Hier mal meine Test-Def, natürlich mit korrekter IP-Adresse:

Code Auswählen Erweitern

define SolakonOne ModbusAttr 1 60 192.168.xx.yy:502 TCP
attr SolakonOne enableControlSet 1
attr SolakonOne event-min-interval .*:600
attr SolakonOne event-on-change-reading .*
attr SolakonOne group Elektrik
attr SolakonOne icon solar
attr SolakonOne maxTimeoutsToReconnect 3
attr SolakonOne obj-h30016-len 16
attr SolakonOne obj-h30016-reading SerialNumber
attr SolakonOne obj-h30016-unpack (a16)
attr SolakonOne obj-h30032-len 16
attr SolakonOne obj-h30032-reading Manufacturer
attr SolakonOne obj-h30032-unpack (a16)
attr SolakonOne obj-h36001-reading master_version
attr SolakonOne obj-h36001-unpack n
attr SolakonOne room Energie
Seltsam ist, dass wenn ich nach Modbusobjekten scannen lasse, dann kommen passende Daten an. Die angelegten "obj" Attribute führen aber wohl nicht zum Anlegen von Readings

Grüße,
Jan

#16

ESP Familie / Aw: Tasmota Rule, ich komm nic...

Letzter Beitrag von andies - 23 Januar 2026, 20:20:40

Ich bin gerade dabei auf analoges Signal (0-5 V) umzusteigen. Vielleicht liegt es ja auch an dem Kemo, dass der kaputt ist? Sobald ich wieder Zeit hab, berichte ich mal.

#17

ESP Familie / Aw: PWM mit ESP8266

Letzter Beitrag von Papa Romeo - 23 Januar 2026, 20:08:43

Was für einen Mosfet? Womöglich langsamer Powermosfet?

Bei der Ansteuerung von MOS-FET´s mit den ESP´s und den Frequenzen hat das weniger mit Geschwindigkeit zu tun.
Die "normalen" MOS-FET´s hätten gern eine Gate-Spannung von 10Volt und drüber, damit sie sauber durchschalten.
Bei den EPS´s ist es daher ratsam auf sogenannte Logik-Level-Fet´s zurückzugreifen um sicher und sauber durchzuschalten.

LG
Papa Romeo

#18

TabletUI / Aw: Positionierung von ftui-ic...

Letzter Beitrag von cruser1800 - 23 Januar 2026, 19:54:01

Nach einigen suchen habe ich es gefunden.

Als einziges Widget (Icon), was ich nutze, ist hier die Lage ohne "style" einzutragen!

Code Auswählen Erweitern

top="400px", left="380px"

Vielleicht braucht es jemand.

#19

FRITZ!Box / Aw: Keine stabile FRITZBOX Ver...

Letzter Beitrag von JoWiemann - 23 Januar 2026, 19:35:24

Hallo Gerhard,

Code Auswählen Erweitern

2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable)
2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 00:21:11 3: XX_FBAHAHTTP: gethostbyname fritz.box failed

Hallo Gerhard,

da auch das XX_FBAHAHTTP Device zu den Zeitpunkten keine Verbindung bekommt, sieht es so aus, als wenn dann der RPi die Verbindung zum Netzwerk verliert.
- Wie ist der RPi auf dem Fhem läuft mit dem Netzwerk verbunden?
- Kannst Du in den Linux Log-Dateien etwas zu Netzwerkzustand finden?
- schau doch mal in den Ereignissen auf der FritzBox, die der Mesh Master ist, ob dort etwas hinterlegt ist.

Grüße Jörg

#20

ESP Familie / Aw: PWM mit ESP8266

Letzter Beitrag von DerD - 23 Januar 2026, 19:26:54

Der DS3502 (digitale Poti 10kOhm) wird unterstützt.

Das probiere ich jetzt mal. Habe mir alles beschafft. Ich wollte zuerst den arduino MKR nehmen, das scheint mir aber mit dem DS3502 nun eher overkill zu sein. Ich berichte. Danke!

Messe aber vorher mal die Spannung die am Stell-Poti liegt. Der DS3502 kann nur max 15V. Und die Doku die ich gefunden habe zu den Kemo Teilen ist wenig erbaulich