Router Online, keine Verbindung der Clients

Technik Störungen & Netzprobleme
1

Hallo,
seit ein paar Tagen (genauer kann ich es leider nicht sagen) sind unsere beiden Futros gestört.

Es geht zum Beispiel um den folgenden Knoten: https://karte.freifunk-muensterland.de/map/#!v:m;n:001999b07664

IPv6-Adressen werden an den Clients verteilt, eine Verbindung (z.B. Ping) ins Internet läuft aber nicht.

Vom Futro selber bekomme ich eine Verbindung (ping v4) ins Internet. DNS funktioniert hingegen nicht.
Vermutlich kennt jemand schon, ohne das ich hier hunderte weitere Details poste, das Problem?

brctl show
bridge name bridge id STP enabled interfaces
br-client 7fff.10feed038530 no eth0.212
local-port
bat0
br-mesh_lan 7fff.365d511415b4 no eth0.2
br-wan 7fff.365d511415b0 no eth1

Ifconfig
bat0 Link encap:Ethernet HWaddr 10:FE:ED:03:85:30
inet6 addr: fe80::12fe:edff:fe03:8530/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:34 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368 (4.2 KiB) TX bytes:758 (758.0 B)

br-client Link encap:Ethernet  HWaddr 10:FE:ED:03:85:30  
          inet6 addr: fe80::12fe:edff:fe03:8530/64 Scope:Link
          inet6 addr: 2a03:2260:115:4600:12fe:edff:fe03:8530/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:184 errors:0 dropped:0 overruns:0 frame:0
          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:23162 (22.6 KiB)  TX bytes:14936 (14.5 KiB)

br-mesh_lan Link encap:Ethernet  HWaddr 36:5D:51:14:15:B4  
          inet6 addr: fe80::345d:51ff:fe14:15b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:368 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:21564 (21.0 KiB)

br-wan    Link encap:Ethernet  HWaddr 36:5D:51:14:15:B0  
          inet addr:10.20.0.9  Bcast:10.20.0.255  Mask:255.255.255.0
          inet6 addr: fe80::345d:51ff:fe14:15b0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2174 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1995 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:177798 (173.6 KiB)  TX bytes:203963 (199.1 KiB)

eth0      Link encap:Ethernet  HWaddr 00:19:99:B0:76:64  
          inet6 addr: fe80::219:99ff:feb0:7664/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1141 errors:0 dropped:31 overruns:0 frame:0
          TX packets:589 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:160663 (156.8 KiB)  TX bytes:34630 (33.8 KiB)

eth0.2    Link encap:Ethernet  HWaddr 00:19:99:B0:76:64  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:368 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:21564 (21.0 KiB)

eth0.212  Link encap:Ethernet  HWaddr 00:19:99:B0:76:64  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:269 errors:0 dropped:0 overruns:0 frame:0
          TX packets:214 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:50032 (48.8 KiB)  TX bytes:12240 (11.9 KiB)

eth1      Link encap:Ethernet  HWaddr 00:AD:24:90:3C:26  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2477 errors:0 dropped:31 overruns:0 frame:0
          TX packets:1995 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:283275 (276.6 KiB)  TX bytes:203963 (199.1 KiB)

local-node Link encap:Ethernet  HWaddr DE:AD:BE:EF:08:01  
          inet addr:10.5.0.1  Bcast:10.5.255.255  Mask:255.255.0.0
          inet6 addr: 2a03:2260:115:500::1/128 Scope:Global
          inet6 addr: fe80::dcad:beff:feef:801/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:151 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:17478 (17.0 KiB)  TX bytes:13330 (13.0 KiB)

local-port Link encap:Ethernet  HWaddr 10:FE:ED:03:85:30  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:151 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:13330 (13.0 KiB)  TX bytes:17478 (17.0 KiB)

primary0  Link encap:Ethernet  HWaddr AE:68:7D:90:08:0B  
          inet6 addr: fe80::ac68:7dff:fe90:80b/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1532  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:13848 (13.5 KiB)

Die verwendete Config sieht wie folgt aus:

config interface ‚loopback‘
option ifname ‚lo‘
option proto ‚static‘
option ipaddr ‚127.0.0.1‘
option netmask ‚255.0.0.0‘

config globals ‚globals‘
option ula_prefix ‚fd88:a3ea:4221::/48‘

config interface ‚wan6‘
option proto ‚dhcpv6‘
option sourcefilter ‚0‘
option ifname ‚br-wan‘
option ip6table ‚1‘
option peerdns ‚0‘

config interface ‚wan‘
option igmp_snooping ‚1‘
option ifname ‚eth1‘
option multicast_querier ‚0‘
option peerdns ‚0‘
option auto ‚1‘
option type ‚bridge‘
option proto ‚dhcp‘
option macaddr ‚36:5d:51:14:15:b1‘

config rule6 ‚wan6_lookup‘
option mark ‚0x01/0x01‘
option lookup ‚1‘

config route6 ‚wan6_unreachable‘
option type ‚unreachable‘
option table ‚1‘
option target ‚::/0‘
option metric ‚65535‘
option gateway ‚::‘
option interface ‚loopback‘

config interface ‚mesh_wan‘
option ifname ‚br-wan‘
option auto ‚0‘
option transitive ‚1‘
option fixed_mtu ‚1‘
option proto ‚gluon_mesh‘

config interface ‚mesh_lan‘
option igmp_snooping ‚0‘
option ifname ‚eth0.213‘ ###<<<<<<<<<<<<hier VLAN2 Meschnetz
option transitive ‚1‘
option fixed_mtu ‚1‘
option proto ‚gluon_mesh‘
option type ‚bridge‘
option auto ‚1‘
option macaddr ‚36:5d:51:14:15:b5‘

config interface ‚client‘
option igmp_snooping ‚1‘
option type ‚bridge‘
option auto ‚1‘
option multicast_querier ‚1‘
option macaddr ‚10:fe:ed:03:85:31‘
option ipv6 ‚1‘
option keep_ra_dnslifetime ‚1‘
option sourcefilter ‚0‘
option peerdns ‚0‘
option robustness ‚3‘
option reqprefix ‚no‘
option query_interval ‚2000‘
option query_response_interval ‚500‘
option proto ‚dhcpv6‘
list ifname ‚local-port‘
list ifname ‚bat0‘
list ifname ‚eth0.212‘ ###<<<<<<<<<<<< VLAN3 Clientnetz

config device ‚local_node_dev‘
option type ‚veth‘
option name ‚local-node‘
option peer_name ‚local-port‘
option macaddr ‚de:ad:be:ef:08:02‘
option peer_macaddr ‚10:fe:ed:03:85:31‘

config interface ‚local_node‘
option ifname ‚local-node‘
option ipaddr ‚10.5.0.1/16‘
option ip6addr ‚2a03:2260:115:500::1/128‘
option ip6deprecated ‚1‘
option proto ‚static‘

config interface ‚gluon_bat0‘
option proto ‚gluon_bat0‘

config interface ‚bat0‘
option multicast_router ‚2‘
option ifname ‚bat0‘
option auto ‚1‘
option macaddr ‚10:fe:ed:03:85:31‘
option learning ‚1‘
option proto ‚none‘

config route6 ‚local_node_route6‘
option target ‚2a03:2260:115:500::/64‘
option gateway ‚::‘
option interface ‚client‘

config interface ‚mesh_vpn‘
option ifname ‚mesh-vpn‘
option transitive ‚1‘
option mtu ‚1364‘
option macaddr ‚36:5d:51:14:15:b8‘
option fixed_mtu ‚1‘
option proto ‚gluon_mesh‘

Viele Grüße
Linus

2

Hallo Linus,

zeig mal bitte die Ausgabe von

logread | grep td-client

Grüße
Matthias

3

EDIT: Ich habe eine Idee - melde mich wenn ich nicht klar komme.
Das untere kann erstmal ignoriert werden.

Hi,
auf dem Testsystem mit neuer Firmware:

Thu Aug 8 17:12:44 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:12:44 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:12:44 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:12:47 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:47 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:47 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:47 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:48 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:12:48 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:12:48 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:12:48 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:12:51 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:51 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:51 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:51 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:51 2019 daemon.err td-client: No suitable brokers found. Retrying in 5 seconds
Thu Aug 8 17:12:56 2019 daemon.info td-client: Performing broker selection…
Thu Aug 8 17:12:59 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:59 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:59 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:12:59 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:13:00 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:13:00 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:13:00 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:13:00 2019 daemon.info td-client: Reinitializing tunnel context.

Auf dem Futro der schon länger unangetastet läuft:

Wed Aug 7 07:44:54 2019 daemon.info td-client: Selected domaene46-a.servers.freifunk-muensterland.de:20046 as the best broker.
Wed Aug 7 07:44:55 2019 daemon.info td-client: Tunnel successfully established.
Wed Aug 7 07:45:00 2019 daemon.warn td-client: Got termination signal, shutting down tunnel…
Wed Aug 7 07:45:01 2019 daemon.info td-client: Performing broker selection…
Wed Aug 7 07:45:01 2019 daemon.debug td-client: Broker usage: 0x823d5d0 domaene46-a.servers.freifunk-muensterland.de 1983
Wed Aug 7 07:45:01 2019 daemon.debug td-client: Broker usage: 0x8241e78 domaene46-a.servers.freifunk-muensterland.net 1983
Wed Aug 7 07:45:22 2019 daemon.info td-client: Selected domaene46-a.servers.freifunk-muensterland.de:20046 as the best broker.
Wed Aug 7 07:45:23 2019 daemon.warn td-client: Received error response from broker!
Wed Aug 7 07:45:26 2019 daemon.warn td-client: Received error response from broker!
Wed Aug 7 07:45:29 2019 daemon.info td-client: Tunnel successfully established.
Wed Aug 7 08:42:06 2019 daemon.warn td-client: Tunnel has timed out, closing down interface.
Wed Aug 7 08:42:06 2019 daemon.err td-client: Connection to domaene46-a.servers.freifunk-muensterland.de lost.
Wed Aug 7 08:42:06 2019 daemon.info td-client: Performing broker selection…
Wed Aug 7 08:42:06 2019 daemon.debug td-client: Broker usage: 0x8241978 domaene46-b.servers.freifunk-muensterland.de 1919
Wed Aug 7 08:42:06 2019 daemon.debug td-client: Broker usage: 0x8241fe8 domaene46-b.servers.freifunk-muensterland.net 1919
Wed Aug 7 08:42:27 2019 daemon.info td-client: Selected domaene46-b.servers.freifunk-muensterland.de:20046 as the best broker.
Wed Aug 7 08:42:28 2019 daemon.warn td-client: Received error response from broker!
Wed Aug 7 08:42:31 2019 daemon.warn td-client: Received error response from broker!
Wed Aug 7 08:42:34 2019 daemon.info td-client: Tunnel successfully established.
Wed Aug 7 08:45:45 2019 daemon.warn td-client: Tunnel has timed out, closing down interface.
Wed Aug 7 08:45:45 2019 daemon.err td-client: Connection to domaene46-b.servers.freifunk-muensterland.de lost.
Wed Aug 7 08:45:45 2019 daemon.info td-client: Performing broker selection…
Wed Aug 7 08:46:06 2019 daemon.info td-client: Selected domaene46-a.servers.freifunk-muensterland.de:20046 as the best broker.
Wed Aug 7 08:46:11 2019 daemon.info td-client: Tunnel successfully established.
Wed Aug 7 09:14:29 2019 daemon.err td-client: Broker sent us a teardown request, closing tunnel with errorcode 2!
Wed Aug 7 09:14:29 2019 daemon.info td-client: Reinitializing tunnel context.
Wed Aug 7 09:15:00 2019 daemon.warn td-client: Got termination signal, shutting down tunnel…
Wed Aug 7 09:15:01 2019 daemon.info td-client: Performing broker selection…
Wed Aug 7 09:15:01 2019 daemon.debug td-client: Broker usage: 0x9d8c978 domaene46-b.servers.freifunk-muensterland.de 2623
Wed Aug 7 09:15:01 2019 daemon.debug td-client: Broker usage: 0x9d8cfe8 domaene46-b.servers.freifunk-muensterland.net 2623
Wed Aug 7 09:15:22 2019 daemon.info td-client: Selected domaene46-b.servers.freifunk-muensterland.de:20046 as the best broker.
Wed Aug 7 09:15:23 2019 daemon.info td-client: Tunnel successfully established.
Wed Aug 7 10:32:30 2019 daemon.warn td-client: Tunnel has timed out, closing down interface.
Wed Aug 7 10:32:30 2019 daemon.err td-client: Connection to domaene46-b.servers.freifunk-muensterland.de lost.
Wed Aug 7 10:32:30 2019 daemon.info td-client: Performing broker selection…
Wed Aug 7 10:32:30 2019 daemon.debug td-client: Broker usage: 0x9d8ce78 domaene46-a.servers.freifunk-muensterland.net 0
Wed Aug 7 10:32:30 2019 daemon.debug td-client: Broker usage: 0x9d885d0 domaene46-a.servers.freifunk-muensterland.de 0
Wed Aug 7 10:32:51 2019 daemon.info td-client: Selected domaene46-a.servers.freifunk-muensterland.de:20046 as the best broker.
Wed Aug 7 10:32:52 2019 daemon.info td-client: Tunnel successfully established.

Wenn ich die Firmware ohne eigene config installiere:

Thu Aug 8 17:31:27 2019 daemon.info td-client: Performing broker selection…
Thu Aug 8 17:31:31 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:31 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:31 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:31 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:32 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:32 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:32 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:32 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:35 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:35 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:35 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:35 2019 daemon.err td-client: Hostname resolution timed out.
Thu Aug 8 17:31:35 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:35 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:35 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:35 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:35 2019 daemon.err td-client: Failed to connect to remote endpoint - check WAN connectivity!
Thu Aug 8 17:31:35 2019 daemon.debug td-client: Broker usage of domaene46-b.servers.freifunk-muensterland.de:20046: 2047
Thu Aug 8 17:31:35 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:35 2019 daemon.debug td-client: Broker usage of domaene46-a.servers.freifunk-muensterland.de:20046: 1983
Thu Aug 8 17:31:35 2019 daemon.debug td-client: Broker usage of domaene46-a.servers.freifunk-muensterland.net:20046: 1983
Thu Aug 8 17:31:35 2019 daemon.err td-client: Failed to connect to remote endpoint - check WAN connectivity!
Thu Aug 8 17:31:36 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:36 2019 daemon.err td-client: Failed to connect to remote endpoint - check WAN connectivity!
Thu Aug 8 17:31:37 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:37 2019 daemon.err td-client: Failed to connect to remote endpoint - check WAN connectivity!
Thu Aug 8 17:31:38 2019 daemon.info td-client: Reinitializing tunnel context.
Thu Aug 8 17:31:38 2019 daemon.info td-client: Selected domaene46-a.servers.freifunk-muensterland.de:20046 as the best broker.
Thu Aug 8 17:31:38 2019 daemon.warn td-client: Received error response from broker!
Thu Aug 8 17:31:38 2019 daemon.err td-client: Connection to domaene46-a.servers.freifunk-muensterland.de lost.
Thu Aug 8 17:31:39 2019 daemon.info td-client: Performing broker selection…
Thu Aug 8 17:31:39 2019 daemon.info td-client: Not trying domaene46-a.servers.freifunk-muensterland.de:20046 again as it broke last time we tried.
Thu Aug 8 17:31:40 2019 daemon.err td-client: Failed to connect to remote endpoint - check WAN connectivity!
Thu Aug 8 17:31:40 2019 daemon.err td-client: Failed to connect to remote endpoint - check WAN connectivity!
Thu Aug 8 17:31:40 2019 daemon.info td-client: Reinitializing tunnel context.

4

DNS ist irgendwie kaputt. Das zickt häufiger mal unter Gluon x86.

5

Dieses Thema wurde automatisch 3 Tage nach der letzten Antwort geschlossen. Es sind keine neuen Nachrichten mehr erlaubt.