TP-Link WR940N: Problem mit Firmware

Hallo,

habe hier einen TP-Link WR940N mit der aktuellen (Beta) Firmware stehen.
Im Config-Mode ist der Router über 192.168.1.1 auf einem der gelben internen Ports erreichbar.
Beim Abschluss der Konfiguration über das Webinterface mit dem Wizard wird einem der Key nicht angezeigt.
Nach einem Reboot ist der Router über eine per DHCP bezogene Adresse auf dem WAN-Port (blau) erreichbar.
Per SSH habe ich überprüfen können das ein Key eingetragen wurde.
Aber der Router scheint nicht über den WAN-Port kommunizieren zu können.
Das Wifi mit SSID „Freifunk“ wird ausgestrahlt aber bei Verbindung mit diesem erhält man keine IP.

Damit bin ich dann aber auch erst mal mit meinem Latein am Ende, da noch FF-Neuling.

Weiß jemand weiter?

Grüße

Stephan

Das kann ein temporaeres Problem sein. Besonders abends, wen das Netz recht voll ist, kann es zu Problemen bei IPv4 DHCP geben. Meist funktioniert die Adressvergabe dann einige Minuten spaeter wieder.

Hallo @stephan.kueppers!

Du kannst Dich ja mal per SSH über die v4 Adresse auf dem WAN Interface auf dem Router einloggen.
Nach dem Login bitte einmal logread aufrufen und die ausgabe hier posten bzw. in ein Pastebin kippen.

Gruß,
Philip

Hallo @pberndro,
hier die Ausgabe von logread:

Thu Feb 25 01:28:45 2016 user.notice firewall: Reloading firewall due to ifup of wan (br-wan)
Thu Feb 25 01:28:46 2016 daemon.info dnsmasq[1105]: reading /var/gluon/wan-dnsmasq/resolv.conf
Thu Feb 25 01:28:46 2016 daemon.info dnsmasq[1105]: using nameserver 10.111.0.254#53
Thu Feb 25 01:28:50 2016 daemon.info hostapd: client0: STA 60:c5:47:90:16:b2 IEEE 802.11: authenticated
Thu Feb 25 01:28:50 2016 daemon.info hostapd: client0: STA 60:c5:47:90:16:b2 IEEE 802.11: associated (aid 1)
Thu Feb 25 01:28:50 2016 daemon.notice netifd: Interface ‚client‘ is now up
Thu Feb 25 01:28:50 2016 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Thu Feb 25 01:28:57 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:28:57 2016 daemon.info fastd[1391]: resolved hostnode02-1.freifunk-essen.net’ successfully
Thu Feb 25 01:28:58 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:28:58 2016 daemon.info fastd[1391]: resolved hostnode02-2.freifunk-essen.net’ successfully
Thu Feb 25 01:28:59 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:28:59 2016 daemon.info fastd[1391]: resolved hostnode01-1.freifunk-essen.net’ successfully
Thu Feb 25 01:28:59 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:28:59 2016 daemon.info fastd[1391]: resolved hostnode01-2.freifunk-essen.net’ successfully
Thu Feb 25 01:29:05 2016 kern.notice kernel: [ 53.210000] random: nonblocking pool is initialized
Thu Feb 25 01:29:12 2016 authpriv.info dropbear[2091]: Child connection from 10.111.0.200:59297
Thu Feb 25 01:29:15 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node02>[85.14.253.228:10000]…
Thu Feb 25 01:29:15 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:29:15 2016 daemon.info fastd[1391]: resolving hostnode02-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:29:16 2016 daemon.info hostapd: client0: STA 60:c5:47:90:16:b2 IEEE 802.11: authenticated
Thu Feb 25 01:29:16 2016 daemon.info hostapd: client0: STA 60:c5:47:90:16:b2 IEEE 802.11: associated (aid 1)
Thu Feb 25 01:29:18 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node02>[185.46.137.143:10000]…
Thu Feb 25 01:29:18 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:29:18 2016 daemon.info fastd[1391]: resolving hostnode02-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:29:19 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node01>[151.80.64.184:10000]…
Thu Feb 25 01:29:19 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:29:19 2016 daemon.info fastd[1391]: resolving hostnode01-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:29:20 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node01>[151.80.64.185:10000]…
Thu Feb 25 01:29:20 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:29:20 2016 daemon.info fastd[1391]: resolving hostnode01-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:29:29 2016 authpriv.warn dropbear[2091]: Bad password attempt for ‚root‘ from 10.111.0.200:59297
Thu Feb 25 01:29:30 2016 authpriv.warn dropbear[2091]: Bad password attempt for ‚root‘ from 10.111.0.200:59297
Thu Feb 25 01:29:33 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:29:33 2016 daemon.info fastd[1391]: resolved hostnode02-1.freifunk-essen.net’ successfully
Thu Feb 25 01:29:37 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:29:37 2016 daemon.info fastd[1391]: resolved hostnode02-2.freifunk-essen.net’ successfully
Thu Feb 25 01:29:37 2016 authpriv.notice dropbear[2091]: Password auth succeeded for ‚root‘ from 10.111.0.200:59297
Thu Feb 25 01:29:38 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:29:38 2016 daemon.info fastd[1391]: resolved hostnode01-2.freifunk-essen.net’ successfully
Thu Feb 25 01:29:40 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:29:40 2016 daemon.info fastd[1391]: resolved hostnode01-1.freifunk-essen.net’ successfully
Thu Feb 25 01:29:53 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node02>[85.14.253.228:10000]…
Thu Feb 25 01:29:53 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:29:53 2016 daemon.info fastd[1391]: resolving hostnode02-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:29:56 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node01>[151.80.64.185:10000]…
Thu Feb 25 01:29:56 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:29:56 2016 daemon.info fastd[1391]: resolving hostnode01-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:29:57 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node02>[185.46.137.143:10000]…
Thu Feb 25 01:29:57 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:29:57 2016 daemon.info fastd[1391]: resolving hostnode02-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:29:59 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node01>[151.80.64.184:10000]…
Thu Feb 25 01:29:59 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:29:59 2016 daemon.info fastd[1391]: resolving hostnode01-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:30:13 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:30:13 2016 daemon.info fastd[1391]: resolved hostnode02-1.freifunk-essen.net’ successfully
Thu Feb 25 01:30:17 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:30:17 2016 daemon.info fastd[1391]: resolved hostnode01-2.freifunk-essen.net’ successfully
Thu Feb 25 01:30:17 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:30:17 2016 daemon.info fastd[1391]: resolved hostnode02-2.freifunk-essen.net’ successfully
Thu Feb 25 01:30:21 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:30:21 2016 daemon.info fastd[1391]: resolved hostnode01-1.freifunk-essen.net’ successfully
Thu Feb 25 01:30:32 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node02>[85.14.253.228:10000]…
Thu Feb 25 01:30:32 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:30:32 2016 daemon.info fastd[1391]: resolving hostnode02-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:30:38 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node01>[151.80.64.185:10000]…
Thu Feb 25 01:30:38 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:30:38 2016 daemon.info fastd[1391]: resolving hostnode01-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:30:39 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node02>[185.46.137.143:10000]…
Thu Feb 25 01:30:39 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:30:39 2016 daemon.info fastd[1391]: resolving hostnode02-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:30:42 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node01>[151.80.64.184:10000]…
Thu Feb 25 01:30:42 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:30:42 2016 daemon.info fastd[1391]: resolving hostnode01-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:30:53 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:30:53 2016 daemon.info fastd[1391]: resolved hostnode02-1.freifunk-essen.net’ successfully
Thu Feb 25 01:30:58 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:30:58 2016 daemon.info fastd[1391]: resolved hostnode01-2.freifunk-essen.net’ successfully
Thu Feb 25 01:31:00 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:31:00 2016 daemon.info fastd[1391]: resolved hostnode02-2.freifunk-essen.net’ successfully
Thu Feb 25 01:31:01 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:31:01 2016 daemon.info fastd[1391]: resolved hostnode01-1.freifunk-essen.net’ successfully
Thu Feb 25 01:31:12 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node02>[85.14.253.228:10000]…
Thu Feb 25 01:31:12 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:31:12 2016 daemon.info fastd[1391]: resolving hostnode02-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:31:17 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node01>[151.80.64.185:10000]…
Thu Feb 25 01:31:17 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:31:17 2016 daemon.info fastd[1391]: resolving hostnode01-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:31:18 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node02>[185.46.137.143:10000]…
Thu Feb 25 01:31:18 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:31:18 2016 daemon.info fastd[1391]: resolving hostnode02-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:31:23 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node01>[151.80.64.184:10000]…
Thu Feb 25 01:31:23 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:31:23 2016 daemon.info fastd[1391]: resolving hostnode01-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:31:33 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:31:33 2016 daemon.info fastd[1391]: resolved hostnode02-1.freifunk-essen.net’ successfully
Thu Feb 25 01:31:36 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:31:36 2016 daemon.info fastd[1391]: resolved hostnode02-2.freifunk-essen.net’ successfully
Thu Feb 25 01:31:36 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:31:36 2016 daemon.info fastd[1391]: resolved hostnode01-2.freifunk-essen.net’ successfully
Thu Feb 25 01:31:41 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:31:41 2016 daemon.info fastd[1391]: resolved hostnode01-1.freifunk-essen.net’ successfully
Thu Feb 25 01:31:50 2016 daemon.info hostapd: client0: STA f4:09:d8:60:8a:f6 IEEE 802.11: authenticated
Thu Feb 25 01:31:50 2016 daemon.info hostapd: client0: STA f4:09:d8:60:8a:f6 IEEE 802.11: associated (aid 2)
Thu Feb 25 01:31:54 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node02>[185.46.137.143:10000]…
Thu Feb 25 01:31:54 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:31:54 2016 daemon.info fastd[1391]: resolving hostnode02-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:31:55 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node02>[85.14.253.228:10000]…
Thu Feb 25 01:31:55 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:31:55 2016 daemon.info fastd[1391]: resolving hostnode02-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:31:58 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node01>[151.80.64.185:10000]…
Thu Feb 25 01:31:58 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:31:58 2016 daemon.info fastd[1391]: resolving hostnode01-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:31:59 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node01>[151.80.64.184:10000]…
Thu Feb 25 01:31:59 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:31:59 2016 daemon.info fastd[1391]: resolving hostnode01-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:32:14 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:32:14 2016 daemon.info fastd[1391]: resolved hostnode02-2.freifunk-essen.net’ successfully
Thu Feb 25 01:32:16 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:32:16 2016 daemon.info fastd[1391]: resolved hostnode02-1.freifunk-essen.net’ successfully
Thu Feb 25 01:32:18 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:32:18 2016 daemon.info fastd[1391]: resolved hostnode01-2.freifunk-essen.net’ successfully
Thu Feb 25 01:32:18 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:32:18 2016 daemon.info fastd[1391]: resolved hostnode01-1.freifunk-essen.net’ successfully
Thu Feb 25 01:32:21 2016 daemon.info hostapd: client0: STA f4:09:d8:60:8a:f6 IEEE 802.11: disassociated
Thu Feb 25 01:32:22 2016 daemon.info hostapd: client0: STA f4:09:d8:60:8a:f6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Feb 25 01:32:23 2016 daemon.info hostapd: client0: STA f4:09:d8:60:8a:f6 IEEE 802.11: authenticated
Thu Feb 25 01:32:23 2016 daemon.info hostapd: client0: STA f4:09:d8:60:8a:f6 IEEE 802.11: associated (aid 2)
Thu Feb 25 01:32:33 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node02>[185.46.137.143:10000]…
Thu Feb 25 01:32:33 2016 daemon.info fastd[1391]: resolving host node02-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node02>... Thu Feb 25 01:32:33 2016 daemon.info fastd[1391]: resolving hostnode02-2.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:32:36 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node02>[85.14.253.228:10000]…
Thu Feb 25 01:32:36 2016 daemon.info fastd[1391]: resolving host node02-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node02>... Thu Feb 25 01:32:36 2016 daemon.info fastd[1391]: resolving hostnode02-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:32:36 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_1_peer_node01>[151.80.64.184:10000]…
Thu Feb 25 01:32:36 2016 daemon.info fastd[1391]: resolving host node01-1.freifunk-essen.net' for peer <mesh_vpn_backbone_1_peer_node01>... Thu Feb 25 01:32:36 2016 daemon.info fastd[1391]: resolving hostnode01-1.freifunk-essen.net’ failed: Name or service not known
Thu Feb 25 01:32:39 2016 daemon.info fastd[1391]: sending handshake to <mesh_vpn_backbone_2_peer_node01>[151.80.64.185:10000]…
Thu Feb 25 01:32:39 2016 daemon.info fastd[1391]: resolving host node01-2.freifunk-essen.net' for peer <mesh_vpn_backbone_2_peer_node01>... Thu Feb 25 01:32:39 2016 daemon.info fastd[1391]: resolving hostnode01-2.freifunk-essen.net’ failed: Name or service not known

Gruß
Stephan

Hallo zusammen,

ich habe seit gestern genau den selben Router mit haargenau dem selben Problem. Auch mein logread sieht quasi gleich aus.

Viele Grüße
André

Hallo @stephan.kueppers!

Es kann gut sein, dass hier ein Zusammenhang besteht.

Gruß,
Philip

1 Like

Hallo zusammen,

bei funktioniert jetzt der neue Router. Er konnte sich verbinden und taucht auch auf der Karte auf.

Viele Grüße
André

Auch hier läuft der Router seit gestern Abend. Und taucht natürlich auch in der Karte auf.

Grüße

Stephan