TL-WR1043N v4 0.6.2-stable steigt nach kurzer Zeit aus

Zinita · 23. Januar 2019 um 23:13

Hallo, mein

TP-Link TL-WR1043N/ND v4 mit Version 0.6.2-stable.0-20181214

macht gerade etwas Probleme. Nach ein paar Wochen, in denen er vollkommen normal läuft, bekommt er keine Verbindung zum Internet mehr. Ich habe eigentlich den 1043 an meinem LAN angeschlossen. Eine FB4020 ist per mesh on wlan mit der 1043 verbunden, und das alles funktioniert sehr gut. Aber nach ein paar Wochen in Betrieb bekommt die 1043 keine Verbindung zum Internet und 1043 und 4020 sind offline. Ich habe jetzt die 4020 mit LAN versorgt, jetzt ist die 1043 auch wieder per mesh on wlan online. Ich bin gespannt ob diese Konfiguration durchhält, wenn nicht, dann liegt es wohl eher an meinem LAN oder an Unitymedia.
Ich habe auch eine SSH Verbindung zur 1043, also kann ich daran alles überprüfen was ihr mir sagt.

Ich brauche aber Hilft um herauszufinden warum das immer passiert.

Mal wieder vielen Dank im Voraus für die Hilfe

rgr · 24. Januar 2019 um 19:53

Dann mach doch mal “logread” auf der Kiste und schau was sie sagt.
“ip a” ist auch hilfreich um zu schauen, ob sie vom Netzwerk eine gültige ip-Adresse bekommen hat.

Zinita · 26. Januar 2019 um 00:09

Hier schonmal die beiden Ausgaben:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 9e:1d:9f:3f:46:16 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP qlen 1000
    link/ether 98:de:d0:a8:cc:0c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9ade:d0ff:fea8:cc0c/64 scope link 
       valid_lft forever preferred_lft forever
7: br-wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 76:30:03:29:79:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.198.147/24 brd 192.168.198.255 scope global br-wan
       valid_lft forever preferred_lft forever
    inet6 2a02:8071:219c:ba00:7430:3ff:fe29:79b0/64 scope global dynamic 
       valid_lft 6885sec preferred_lft 3285sec
    inet6 fe80::7430:3ff:fe29:79b0/64 scope link 
       valid_lft forever preferred_lft forever
8: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-wan state UP qlen 1000
    link/ether 98:de:d0:a8:cc:0d brd ff:ff:ff:ff:ff:ff
9: local-port@local-node: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-client state UP qlen 1000
    link/ether 98:de:d0:a8:cc:0c brd ff:ff:ff:ff:ff:ff
10: local-node@local-port: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 16:41:95:40:f7:dc brd ff:ff:ff:ff:ff:ff
    inet 10.214.103.254/21 brd 10.214.103.255 scope global local-node
       valid_lft forever preferred_lft forever
    inet6 2001:678:6e3:10b0::1:1/128 scope global deprecated 
       valid_lft forever preferred_lft 0sec
    inet6 fe80::1441:95ff:fe40:f7dc/64 scope link 
       valid_lft forever preferred_lft forever
11: br-client: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 98:de:d0:a8:cc:0c brd ff:ff:ff:ff:ff:ff
    inet6 2001:678:6e3:10b0:9ade:d0ff:fea8:cc0c/64 scope global dynamic 
       valid_lft 86072sec preferred_lft 14072sec
    inet6 fe80::9ade:d0ff:fea8:cc0c/64 scope link 
       valid_lft forever preferred_lft forever
12: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-client state UP qlen 1000
    link/ether 98:de:d0:a8:cc:0c brd ff:ff:ff:ff:ff:ff
13: primary0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1532 qdisc noqueue master bat0 state UNKNOWN qlen 1000
    link/ether 76:30:03:29:79:b3 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::7430:3ff:fe29:79b3/64 scope link 
       valid_lft forever preferred_lft forever
14: bat0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-client state UNKNOWN qlen 1000
    link/ether 98:de:d0:a8:cc:0c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9ade:d0ff:fea8:cc0c/64 scope link 
       valid_lft forever preferred_lft forever
15: mesh0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532 qdisc noqueue master bat0 state UP qlen 1000
    link/ether 76:30:03:29:79:b1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::7430:3ff:fe29:79b1/64 scope link 
       valid_lft forever preferred_lft forever
16: client0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-client state UP qlen 1000
    link/ether 76:30:03:29:79:b0 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::7430:3ff:fe29:79b0/64 scope link 
       valid_lft forever preferred_lft forever
17: mesh-vpn: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1406 qdisc fq_codel master bat0 state UNKNOWN qlen 1000
    link/ether 76:30:03:29:79:b7 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::7430:3ff:fe29:79b7/64 scope link 
       valid_lft forever preferred_lft forever

logread ist etwas arg lang, gibt es da einen wichtigen Teil, auf den ich achten sollte?

Zinita · 26. Januar 2019 um 00:13

Hier mal ein kleiner Ausschnitt

Fri Jan 25 20:34:56 2019 daemon.info fastd[2151]: refreshing session with <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 20:34:57 2019 daemon.info fastd[2151]: sending handshake to <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200]...
Fri Jan 25 20:34:57 2019 daemon.info fastd[2151]: received handshake response from <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200] using fastd v18
Fri Jan 25 20:34:57 2019 daemon.info fastd[2151]: 185.65.241.21:10200 authorized as <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 20:34:57 2019 daemon.info fastd[2151]: new session with <mesh_vpn_backbone_peer_alb0> established using method `salsa2012+umac'.
Fri Jan 25 20:36:40 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: authenticated
Fri Jan 25 20:36:40 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: associated (aid 1)
Fri Jan 25 20:36:40 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:37:35 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: disconnected due to excessive missing ACKs
Fri Jan 25 20:37:35 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:38:05 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 20:39:19 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: authenticated
Fri Jan 25 20:39:19 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: associated (aid 1)
Fri Jan 25 20:39:19 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:48:12 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:48:12 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: disassociated due to inactivity
Fri Jan 25 20:48:13 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 20:50:18 2019 daemon.info hostapd: client0: STA 94:65:2d:c2:92:b8 IEEE 802.11: authenticated
Fri Jan 25 20:50:18 2019 daemon.info hostapd: client0: STA 94:65:2d:c2:92:b8 IEEE 802.11: associated (aid 1)
Fri Jan 25 20:50:18 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED 94:65:2d:c2:92:b8
Fri Jan 25 20:52:17 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: authenticated
Fri Jan 25 20:52:17 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: associated (aid 2)
Fri Jan 25 20:52:17 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:55:16 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: authenticated
Fri Jan 25 20:55:16 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: associated (aid 2)
Fri Jan 25 20:55:16 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:57:01 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: authenticated
Fri Jan 25 20:57:01 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: associated (aid 2)
Fri Jan 25 20:57:01 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:57:39 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 94:65:2d:c2:92:b8
Fri Jan 25 20:57:39 2019 daemon.info hostapd: client0: STA 94:65:2d:c2:92:b8 IEEE 802.11: disassociated due to inactivity
Fri Jan 25 20:57:40 2019 daemon.info hostapd: client0: STA 94:65:2d:c2:92:b8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 20:58:52 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: disconnected due to excessive missing ACKs
Fri Jan 25 20:58:52 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 20:59:22 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 21:09:56 2019 daemon.info hostapd: client0: STA c0:d0:12:85:81:19 IEEE 802.11: authenticated
Fri Jan 25 21:09:56 2019 daemon.info hostapd: client0: STA c0:d0:12:85:81:19 IEEE 802.11: associated (aid 1)
Fri Jan 25 21:09:56 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED c0:d0:12:85:81:19
Fri Jan 25 21:10:57 2019 daemon.info hostapd: client0: STA 40:9c:28:a8:51:53 IEEE 802.11: authenticated
Fri Jan 25 21:10:57 2019 daemon.info hostapd: client0: STA 40:9c:28:a8:51:53 IEEE 802.11: associated (aid 2)
Fri Jan 25 21:10:57 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED 40:9c:28:a8:51:53
Fri Jan 25 21:14:28 2019 daemon.info hostapd: client0: STA 40:9c:28:a8:51:53 IEEE 802.11: disconnected due to excessive missing ACKs
Fri Jan 25 21:14:28 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 40:9c:28:a8:51:53
Fri Jan 25 21:14:58 2019 daemon.info hostapd: client0: STA 40:9c:28:a8:51:53 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 21:16:29 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED c0:d0:12:85:81:19
Fri Jan 25 21:16:29 2019 daemon.info hostapd: client0: STA c0:d0:12:85:81:19 IEEE 802.11: disassociated due to inactivity
Fri Jan 25 21:16:30 2019 daemon.info hostapd: client0: STA c0:d0:12:85:81:19 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 21:22:02 2019 kern.info kernel: [352320.063202] IPv6: ADDRCONF(NETDEV_UP): tmp.mesh0: link is not ready
Fri Jan 25 21:23:16 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: authenticated
Fri Jan 25 21:23:16 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: associated (aid 1)
Fri Jan 25 21:23:16 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 21:26:03 2019 daemon.info hostapd: client0: STA d0:65:ca:2a:be:b9 IEEE 802.11: authenticated
Fri Jan 25 21:26:03 2019 daemon.info hostapd: client0: STA d0:65:ca:2a:be:b9 IEEE 802.11: associated (aid 2)
Fri Jan 25 21:26:03 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d0:65:ca:2a:be:b9
Fri Jan 25 21:28:47 2019 daemon.info fastd[2151]: refreshing session with <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 21:28:47 2019 daemon.info fastd[2151]: sending handshake to <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200]...
Fri Jan 25 21:28:47 2019 daemon.info fastd[2151]: received handshake response from <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200] using fastd v18
Fri Jan 25 21:28:47 2019 daemon.info fastd[2151]: 185.65.241.21:10200 authorized as <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 21:28:47 2019 daemon.info fastd[2151]: new session with <mesh_vpn_backbone_peer_alb0> established using method `salsa2012+umac'.
Fri Jan 25 21:29:33 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 21:29:33 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: disassociated due to inactivity
Fri Jan 25 21:29:34 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 21:32:25 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED d0:65:ca:2a:be:b9
Fri Jan 25 21:32:25 2019 daemon.info hostapd: client0: STA d0:65:ca:2a:be:b9 IEEE 802.11: disassociated due to inactivity
Fri Jan 25 21:32:26 2019 daemon.info hostapd: client0: STA d0:65:ca:2a:be:b9 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 22:08:30 2019 daemon.info hostapd: client0: STA c8:d7:b0:9b:ea:72 IEEE 802.11: authenticated
Fri Jan 25 22:08:30 2019 daemon.info hostapd: client0: STA c8:d7:b0:9b:ea:72 IEEE 802.11: associated (aid 1)
Fri Jan 25 22:08:30 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED c8:d7:b0:9b:ea:72
Fri Jan 25 22:16:10 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED c8:d7:b0:9b:ea:72
Fri Jan 25 22:16:10 2019 daemon.info hostapd: client0: STA c8:d7:b0:9b:ea:72 IEEE 802.11: disassociated due to inactivity
Fri Jan 25 22:16:11 2019 daemon.info hostapd: client0: STA c8:d7:b0:9b:ea:72 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 22:18:27 2019 daemon.info hostapd: client0: STA 90:06:28:bd:1a:f1 IEEE 802.11: authenticated
Fri Jan 25 22:18:27 2019 daemon.info hostapd: client0: STA 90:06:28:bd:1a:f1 IEEE 802.11: associated (aid 1)
Fri Jan 25 22:18:27 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED 90:06:28:bd:1a:f1
Fri Jan 25 22:19:27 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 90:06:28:bd:1a:f1
Fri Jan 25 22:19:49 2019 daemon.info hostapd: client0: STA e4:e4:ab:6b:55:12 IEEE 802.11: authenticated
Fri Jan 25 22:19:49 2019 daemon.info hostapd: client0: STA e4:e4:ab:6b:55:12 IEEE 802.11: associated (aid 1)
Fri Jan 25 22:19:49 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:6b:55:12
Fri Jan 25 22:19:52 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:6b:55:12
Fri Jan 25 22:19:52 2019 daemon.info hostapd: client0: STA e4:e4:ab:6b:55:12 IEEE 802.11: disassociated
Fri Jan 25 22:19:53 2019 daemon.info hostapd: client0: STA e4:e4:ab:6b:55:12 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Jan 25 22:21:29 2019 daemon.info fastd[2151]: refreshing session with <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 22:21:29 2019 daemon.info fastd[2151]: sending handshake to <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200]...
Fri Jan 25 22:21:30 2019 daemon.info fastd[2151]: received handshake response from <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200] using fastd v18
Fri Jan 25 22:21:30 2019 daemon.info fastd[2151]: 185.65.241.21:10200 authorized as <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 22:21:30 2019 daemon.info fastd[2151]: new session with <mesh_vpn_backbone_peer_alb0> established using method `salsa2012+umac'.
Fri Jan 25 23:16:22 2019 daemon.info fastd[2151]: refreshing session with <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 23:16:22 2019 daemon.info fastd[2151]: sending handshake to <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200]...
Fri Jan 25 23:16:22 2019 daemon.info fastd[2151]: received handshake response from <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200] using fastd v18
Fri Jan 25 23:16:22 2019 daemon.info fastd[2151]: 185.65.241.21:10200 authorized as <mesh_vpn_backbone_peer_alb0>
Fri Jan 25 23:16:22 2019 daemon.info fastd[2151]: new session with <mesh_vpn_backbone_peer_alb0> established using method `salsa2012+umac'.
Fri Jan 25 23:37:04 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: authenticated
Fri Jan 25 23:37:04 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: associated (aid 1)
Fri Jan 25 23:37:04 2019 daemon.notice hostapd: client0: AP-STA-CONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 23:38:55 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: disconnected due to excessive missing ACKs
Fri Jan 25 23:38:55 2019 daemon.notice hostapd: client0: AP-STA-DISCONNECTED d4:a3:3d:0e:1c:ce
Fri Jan 25 23:39:25 2019 daemon.info hostapd: client0: STA d4:a3:3d:0e:1c:ce IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Jan 26 00:09:37 2019 daemon.info fastd[2151]: refreshing session with <mesh_vpn_backbone_peer_alb0>
Sat Jan 26 00:09:37 2019 daemon.info fastd[2151]: sending handshake to <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200]...
Sat Jan 26 00:09:37 2019 daemon.info fastd[2151]: received handshake response from <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200] using fastd v18
Sat Jan 26 00:09:37 2019 daemon.info fastd[2151]: 185.65.241.21:10200 authorized as <mesh_vpn_backbone_peer_alb0>
Sat Jan 26 00:09:37 2019 daemon.info fastd[2151]: new session with <mesh_vpn_backbone_peer_alb0> established using method `salsa2012+umac'.
Sat Jan 26 00:22:03 2019 kern.info kernel: [363120.502196] IPv6: ADDRCONF(NETDEV_UP): tmp.mesh0: link is not ready
Sat Jan 26 01:00:13 2019 daemon.info fastd[2151]: refreshing session with <mesh_vpn_backbone_peer_alb0>
Sat Jan 26 01:00:13 2019 daemon.info fastd[2151]: sending handshake to <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200]...
Sat Jan 26 01:00:13 2019 daemon.info fastd[2151]: received handshake response from <mesh_vpn_backbone_peer_alb0>[185.65.241.21:10200] using fastd v18
Sat Jan 26 01:00:13 2019 daemon.info fastd[2151]: 185.65.241.21:10200 authorized as <mesh_vpn_backbone_peer_alb0>
Sat Jan 26 01:00:13 2019 daemon.info fastd[2151]: new session with <mesh_vpn_backbone_peer_alb0> established using method `salsa2012+umac'.
Sat Jan 26 01:01:52 2019 authpriv.info dropbear[32671]: Child connection from 2a02:8071:219c:ba00:1b:52c9:48ac:5685:46750
Sat Jan 26 01:01:58 2019 authpriv.notice dropbear[32671]: Pubkey auth succeeded for 'root' with key md5 5f:65:4a:91:65:17:44:37:43:63:c3:88:18:b7:a4:0d from 2a02:8071:219c:ba00:1b:52c9:48ac:5685:46750

rgr · 26. Januar 2019 um 21:21

Spannend sind zusammen mit der Aussage “hat keine Verbindung zum Internet mehr” die Angaben von fastd. Fastd kann über das Internet eine Verbindung zum supernode aufnehmen.

Was genau meinst Du mit " bekommt er keine Verbindung zum Internet mehr."?

Zinita · 27. Januar 2019 um 16:23

Ja, ich sollte wohl direkt daran mit dem Lankabel arbeiten und den zweiten Router ausschalten. Denn aktuell bekommt er ja über den zweiten Router Internetzugriff… Also werde ich das morgen nochmal anschauen und dann die entsprechenden Ausgaben nochmal Posten.
Edit: ich werde ihn wohl einfach irgendwann rausschmeißen… Wenn es Probleme gibt, dann komme ich auch nichtmehr drauf, aber wenn ich darauf zugreifen kann, dann gibt es auch keine Probleme mehr.