Router-Probleme: Keine IP-Vergabe, keine Verbindung

Technik Rheinufer
1

Hallo,

ich betreibe einen Freifunk-Router (in Neuss). Der lief auch einwandfrei, als ich ihn damals eingerichtet habe. Irgendwann lief er nicht mehr, aber ich hatte nie Zeit, mich darum zu kümmern. Nun, da ich bei der Einrichtung eines pi-holes in meinem privaten Netzwerk Probleme mit IPv6 habe, kam mir der Gedanke, dass das möglicherweise zusammenhängt. Mein Provider ist Unitymedia, vielleicht hat es auch mit DS-Lite zu tun? Das übersteigt leider meine Kenntnisse.

Also hier mal ein paar Infos:
ich habe ein Modem/WLAN-Router (TC7200U), wenn ich mich recht erinnere), der ein älteres Gerät ersetzte. Ich bin mir leider nicht mal sicher, ob der FF-Router damit jemals funktionierte.
Da der UM-Router ziemlicher Schrott ist, habe ich daran meinen Netgear-Router für das private Netzwerk. Daran wiederum hängt der FF-Router (TP-Link WR841N). Direkt am UM-Router eingestöpselt funktioniert der FF aber auch nicht.

In der FF-Firmware ist kein Mesh on LAN oder WAN aktiviert und es war die Gluon beta eingestellt. Habe ich nun umgestellt auf stable.

Ich kann nicht ausschließen, dass es eine Fehlkonfiguration in einem der vorgeschalteten anderen Router ist. Dummerweise lässt sich im UM-Router nicht viel einstellen. Im Netgear-Router wiederum weiß ich nicht, was ich dort bei IPv6 einstellen soll. 6to4-Tunnel? Automatische Konfiguration? Aber ich kriege allenfalls lokal eine Antwort auf einen ping6.

Natürlich habe ich schon gegoogelt und diverses gelesen. Möglicherweise fehlt mir Background, um das alles einzuordnen. Wie auch immer, ich dachte mir, dass das Problem mit Unitymedia und FF vielleicht bekannt sein sollte, wenn das überhaupt das Problem ist. Wenn ich aber erfahre, dass das mit UM und FF (und eventuell auch mit genau diesem Modem) generell klappt, hilft mir das auch schon mal weiter.

Ich habe verschiedene Test-Seiten, auch für IPv6, über die verschiedenen Router aufgerufen und bekomme nirgends eine IPv6-Verbindung. Allerdings ist es natürlich nur eine Vermutung, dass die Probleme zusammenhängen.

Wenn da jemand vielleicht einen Tipp für mich hat oder bereits entsprechende Erfahrungen gemacht hat, die mir vielleicht weiterhelfen können, wäre ich dankbar.

LG

2

Inzwischen habe ich in anderen Threads dazu gelesen, aber bislang hat mir nichts geholfen. Ich habe im FF-Router mal DHCP für IPv6 deaktiviert, die Firewalls im UM-Router ausgeschaltet und die IP-Vergabe so gestaltet, wie in einem anderen Thread als Lösung angegeben, doch bei mir funktioniert das leider nicht. Der FF-Router hat einfach kein Internet. Ping und Ping6 aus der Busybox heraus gehen auch nicht.

Ich glaube auch nicht, dass es am Netgear-Router liegt, da es auch nicht funzt, wenn der FF-Router direkt am UM-Router hängt.

Im nächsten Beitrag werde ich mal die Ausgabe von dmesg und logread posten.

3

dmesg:

[ 0.000000] Linux version 3.10.49 (cyrus@lambdacore) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r46287) ) #2 Thu Sep 10 09:47:33 CEST 2015
[ 0.000000] MyLoader: sysp=aef732b1, boardp=949e7cfd, parts=5c19680a
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 0001974c (MIPS 74Kc)
[ 0.000000] SoC: Atheros AR9341 rev 3
[ 0.000000] Clocks: CPU:535.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x01ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x01ffffff]
[ 0.000000] On node 0 totalpages: 8192
[ 0.000000] free_area_init_node: node 0, pgdat 80334b60, node_mem_map 81000000
[ 0.000000] Normal zone: 64 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 8192 pages, LIFO batch:0
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
[ 0.000000] Kernel command line: board=TL-WR841N-v8 console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 28588k/32768k available (2369k kernel code, 4180k reserved, 621k data, 272k init, 0k highmem)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.070000] Calibrating delay loop… 266.64 BogoMIPS (lpj=1333248)
[ 0.080000] pid_max: default: 32768 minimum: 301
[ 0.080000] Mount-cache hash table entries: 512
[ 0.090000] NET: Registered protocol family 16
[ 0.100000] MIPS: machine is TP-LINK TL-WR841N/ND v8
[ 0.510000] bio: create slab at 0
[ 0.520000] Switching to clocksource MIPS
[ 0.530000] NET: Registered protocol family 2
[ 0.530000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[ 0.530000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[ 0.540000] TCP: Hash tables configured (established 512 bind 512)
[ 0.540000] TCP: reno registered
[ 0.550000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.550000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.560000] NET: Registered protocol family 1
[ 0.560000] PCI: CLS 0 bytes, default 32
[ 0.580000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.590000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.600000] msgmni has been set to 55
[ 0.600000] io scheduler noop registered
[ 0.600000] io scheduler deadline registered (default)
[ 0.610000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.640000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
[ 0.650000] console [ttyS0] enabled, bootconsole disabled
[ 0.660000] ath79-spi ath79-spi: master is unqueued, this is deprecated
[ 0.670000] m25p80 spi0.0: found s25sl032p, expected m25p80
[ 0.680000] m25p80 spi0.0: s25sl032p (4096 Kbytes)
[ 0.680000] 5 tp-link partitions found on MTD device spi0.0
[ 0.690000] Creating 5 MTD partitions on „spi0.0“:
[ 0.690000] 0x000000000000-0x000000020000 : „u-boot“
[ 0.700000] 0x000000020000-0x00000012e7b8 : „kernel“
[ 0.710000] mtd: partition „kernel“ must either start or end on erase block boundary or be smaller than an erase block – forcing read-only
[ 0.720000] 0x00000012e7b8-0x0000003f0000 : „rootfs“
[ 0.730000] mtd: partition „rootfs“ must either start or end on erase block boundary or be smaller than an erase block – forcing read-only
[ 0.740000] mtd: device 2 (rootfs) set to be root filesystem
[ 0.750000] 1 squashfs-split partitions found on MTD device rootfs
[ 0.750000] 0x000000360000-0x0000003f0000 : „rootfs_data“
[ 0.760000] 0x0000003f0000-0x000000400000 : „art“
[ 0.770000] 0x000000020000-0x0000003f0000 : „firmware“
[ 0.790000] libphy: ag71xx_mdio: probed
[ 1.350000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:00 [uid=004dd042, driver=Generic PHY]
[ 1.360000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[ 1.910000] ag71xx-mdio.1: Found an AR934X built-in switch
[ 2.950000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[ 2.960000] TCP: cubic registered
[ 2.960000] NET: Registered protocol family 17
[ 2.970000] Bridge firewalling registered
[ 2.970000] 8021q: 802.1Q VLAN Support v1.8
[ 2.980000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[ 2.990000] Freeing unused kernel memory: 272K (8034c000 - 80390000)
[ 7.520000] eth1: link up (1000Mbps/Full duplex)
[ 10.250000] jffs2: notice: (330) jffs2_build_xattr_subsystem: complete building xattr subsystem, 34 of xdatum (1 unchecked, 33 orphan) and 47 of xref (0 dead, 33 orphan) found.
[ 10.480000] eth1: link down
[ 12.350000] NET: Registered protocol family 10
[ 12.360000] tun: Universal TUN/TAP device driver, 1.6
[ 12.360000] tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.com
[ 12.380000] nf_conntrack version 0.5.0 (450 buckets, 1800 max)
[ 12.390000] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 12.420000] batman_adv: B.A.T.M.A.N. advanced 2013.4.0 (compatibility version 14) loaded
[ 12.440000] u32 classifier
[ 12.440000] input device check on
[ 12.440000] Actions configured
[ 12.450000] Mirror/redirect action on
[ 12.460000] netem: version 1.3
[ 12.470000] Failed to load ipt action
[ 12.490000] Loading modules backported from Linux version master-2014-05-22-0-gf2032ea
[ 12.500000] Backport generated by backports.git backports-20140320-37-g5c33da0
[ 12.540000] Ebtables v2.0 registered
[ 12.540000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 12.650000] xt_time: kernel timezone is -0000
[ 12.710000] cfg80211: Calling CRDA to update world regulatory domain
[ 12.710000] cfg80211: World regulatory domain updated:
[ 12.720000] cfg80211: DFS Master region: unset
[ 12.720000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 12.730000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.740000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.750000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.760000] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.770000] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 12.770000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 12.780000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.790000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 12.910000] ath: EEPROM regdomain: 0x0
[ 12.910000] ath: EEPROM indicates default country code should be used
[ 12.910000] ath: doing EEPROM country->regdmn map search
[ 12.910000] ath: country maps to regdmn code: 0x3a
[ 12.910000] ath: Country alpha2 being used: US
[ 12.910000] ath: Regpair used: 0x3a
[ 12.920000] ieee80211 phy0: Selected rate control algorithm ‚minstrel_ht‘
[ 12.930000] cfg80211: Calling CRDA for country: US
[ 12.930000] cfg80211: Regulatory domain changed to country: US
[ 12.940000] cfg80211: DFS Master region: FCC
[ 12.950000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 12.960000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[ 12.960000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
[ 12.970000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (0 s)
[ 12.980000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[ 12.990000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 13.000000] ieee80211 phy0: Atheros AR9340 Rev:0 mem=0xb8100000, irq=47
[ 28.550000] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 28.550000] device eth1 entered promiscuous mode
[ 28.590000] IPv6: ADDRCONF(NETDEV_UP): br-client: link is not ready
[ 28.640000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 28.650000] device eth0 entered promiscuous mode
[ 28.690000] br-wan: port 1(eth0) entered forwarding state
[ 28.700000] br-wan: port 1(eth0) entered forwarding state
[ 28.760000] device br-client entered promiscuous mode
[ 28.770000] IPv6: ADDRCONF(NETDEV_UP): local-node: link is not ready
[ 29.150000] eth1: link up (1000Mbps/Full duplex)
[ 29.150000] br-client: port 1(eth1) entered forwarding state
[ 29.160000] br-client: port 1(eth1) entered forwarding state
[ 29.170000] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 29.250000] IPv6: ADDRCONF(NETDEV_CHANGE): br-client: link becomes ready
[ 29.350000] IPv6: ADDRCONF(NETDEV_CHANGE): local-node: link becomes ready
[ 29.560000] batman_adv: bat0: Adding interface: mesh-vpn
[ 29.560000] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1406) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1528 would solve the problem.
[ 29.590000] batman_adv: bat0: Interface activated: mesh-vpn
[ 29.590000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled
[ 29.610000] device bat0 entered promiscuous mode
[ 29.610000] br-client: port 2(bat0) entered forwarding state
[ 29.620000] br-client: port 2(bat0) entered forwarding state
[ 29.640000] br-wan: port 1(eth0) entered disabled state
[ 31.110000] eth0: link up (100Mbps/Full duplex)
[ 31.160000] br-client: port 1(eth1) entered forwarding state
[ 31.160000] br-wan: port 1(eth0) entered forwarding state
[ 31.170000] br-wan: port 1(eth0) entered forwarding state
[ 31.170000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 31.240000] cfg80211: Calling CRDA for country: DE
[ 31.280000] cfg80211: Regulatory domain changed to country: DE
[ 31.280000] cfg80211: DFS Master region: ETSI
[ 31.290000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 31.300000] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 31.300000] cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 31.310000] cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
[ 31.320000] cfg80211: (5470000 KHz - 5725000 KHz @ 80000 KHz), (N/A, 2700 mBm), (0 s)
[ 31.330000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 31.620000] br-client: port 2(bat0) entered forwarding state
[ 32.000000] batman_adv: bat0: Changing gw mode from: off to: client
[ 32.020000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15
[ 32.020000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000
[ 33.170000] br-wan: port 1(eth0) entered forwarding state
[ 33.560000] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
[ 33.590000] device client0 entered promiscuous mode
[ 34.720000] br-client: port 3(client0) entered forwarding state
[ 34.730000] br-client: port 3(client0) entered forwarding state
[ 34.740000] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
[ 35.140000] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
[ 35.170000] mesh0: Created IBSS using preconfigured BSSID 32:ca:ff:ee:ba:be
[ 35.180000] mesh0: Creating new IBSS network, BSSID 32:ca:ff:ee:ba:be
[ 35.200000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
[ 35.480000] batman_adv: bat0: Adding interface: mesh0
[ 35.480000] batman_adv: bat0: Interface activated: mesh0
[ 36.730000] br-client: port 3(client0) entered forwarding state
[ 1003.590000] eth1: link down
[ 1003.590000] br-client: port 1(eth1) entered disabled state

logread:

Sun Jun 4 15:31:43 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer2>... Sun Jun 4 15:31:43 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:45 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer8>... Sun Jun 4 15:31:45 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:47 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer3>... Sun Jun 4 15:31:47 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:47 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer9>... Sun Jun 4 15:31:47 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:47 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer10>... Sun Jun 4 15:31:47 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:48 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer1>... Sun Jun 4 15:31:48 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:48 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer12>... Sun Jun 4 15:31:48 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:48 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer6>... Sun Jun 4 15:31:48 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:49 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer5>... Sun Jun 4 15:31:49 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:51 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer0>... Sun Jun 4 15:31:51 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:55 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer11>... Sun Jun 4 15:31:55 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:31:57 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: disassociated
Sun Jun 4 15:31:58 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Jun 4 15:32:00 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer2>... Sun Jun 4 15:32:00 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:01 2017 daemon.info hostapd: client0: STA c8:85:50:66:41:72 IEEE 802.11: authenticated
Sun Jun 4 15:32:01 2017 daemon.info hostapd: client0: STA c8:85:50:66:41:72 IEEE 802.11: associated (aid 1)
Sun Jun 4 15:32:02 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer4>... Sun Jun 4 15:32:02 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:04 2017 daemon.info fastd[1201]: resolving host rheinufer7.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer7>... Sun Jun 4 15:32:04 2017 daemon.info fastd[1201]: resolving host rheinufer7.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:04 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer3>... Sun Jun 4 15:32:04 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:05 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer9>... Sun Jun 4 15:32:05 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:05 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer8>... Sun Jun 4 15:32:05 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:05 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer1>... Sun Jun 4 15:32:05 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:07 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer10>... Sun Jun 4 15:32:07 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:10 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: authenticated
Sun Jun 4 15:32:10 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: associated (aid 2)
Sun Jun 4 15:32:10 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer12>... Sun Jun 4 15:32:10 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:11 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer6>... Sun Jun 4 15:32:11 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:11 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer5>... Sun Jun 4 15:32:11 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:13 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer0>... Sun Jun 4 15:32:13 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:16 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer11>... Sun Jun 4 15:32:16 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:21 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer2>... Sun Jun 4 15:32:21 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:22 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer4>... Sun Jun 4 15:32:22 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:23 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer9>... Sun Jun 4 15:32:23 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:24 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer3>... Sun Jun 4 15:32:24 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:25 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer10>... Sun Jun 4 15:32:25 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:25 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer1>... Sun Jun 4 15:32:25 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:26 2017 daemon.info fastd[1201]: resolving host rheinufer7.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer7>... Sun Jun 4 15:32:26 2017 daemon.info fastd[1201]: resolving host rheinufer7.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:28 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer8>... Sun Jun 4 15:32:28 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:30 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer6>... Sun Jun 4 15:32:30 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:31 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer12>... Sun Jun 4 15:32:31 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:34 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer5>... Sun Jun 4 15:32:34 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:34 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer0>... Sun Jun 4 15:32:34 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:38 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer11>... Sun Jun 4 15:32:38 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:41 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer4>... Sun Jun 4 15:32:41 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:41 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer2>... Sun Jun 4 15:32:41 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:41 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer3>... Sun Jun 4 15:32:41 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:44 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer9>... Sun Jun 4 15:32:44 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:46 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer10>... Sun Jun 4 15:32:46 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:46 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: disassociated
Sun Jun 4 15:32:47 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Jun 4 15:32:47 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer1>... Sun Jun 4 15:32:47 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:48 2017 daemon.info fastd[1201]: resolving host rheinufer7.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer7>... Sun Jun 4 15:32:48 2017 daemon.info fastd[1201]: resolving host rheinufer7.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:48 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer8>... Sun Jun 4 15:32:48 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:49 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer12>... Sun Jun 4 15:32:49 2017 daemon.info fastd[1201]: resolving host rheinufer12.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:50 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer6>... Sun Jun 4 15:32:50 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:52 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer5>... Sun Jun 4 15:32:52 2017 daemon.info fastd[1201]: resolving host rheinufer5.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:52 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer0>... Sun Jun 4 15:32:52 2017 daemon.info fastd[1201]: resolving host rheinufer0.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:58 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer11>... Sun Jun 4 15:32:58 2017 daemon.info fastd[1201]: resolving host rheinufer11.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:32:58 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: authenticated
Sun Jun 4 15:32:58 2017 daemon.info hostapd: client0: STA 50:01:d9:fd:1c:2c IEEE 802.11: associated (aid 2)
Sun Jun 4 15:32:59 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer4>... Sun Jun 4 15:32:59 2017 daemon.info fastd[1201]: resolving host rheinufer4.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:33:01 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer2>... Sun Jun 4 15:33:01 2017 daemon.info fastd[1201]: resolving host rheinufer2.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:33:02 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer3>... Sun Jun 4 15:33:02 2017 daemon.info fastd[1201]: resolving host rheinufer3.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:33:04 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer9>... Sun Jun 4 15:33:04 2017 daemon.info fastd[1201]: resolving host rheinufer9.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:33:06 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer10>... Sun Jun 4 15:33:06 2017 daemon.info fastd[1201]: resolving host rheinufer10.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:33:06 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer1>... Sun Jun 4 15:33:06 2017 daemon.info fastd[1201]: resolving host rheinufer1.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:33:08 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer6>... Sun Jun 4 15:33:08 2017 daemon.info fastd[1201]: resolving host rheinufer6.freifunk-rheinland.net’ failed: Name or service not known
Sun Jun 4 15:33:08 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net' for peer <mesh_vpn_backbone_peer_rheinufer8>... Sun Jun 4 15:33:08 2017 daemon.info fastd[1201]: resolving host rheinufer8.freifunk-rheinland.net’ failed: Name or service not known

4

Hi,

das Gerät hat keinen funktionierenden DNS-Server bekommen. Du könntest behelfsweise die IPs der nicht auflösbaren Namenseinträge aus dem Log in die /etc/hosts eintragen.

Grüße
Matthias

5

Hi Matthias,

jetzt läuft der FF-Router wieder! Das Problem war offenbar die uralte Firmware, die trotz aktiviertem Autoupdate immer noch drauf war. Vermutlich kam er nicht mehr ins Netz, um die Firmware selbst upzudaten, aber das ist nur eine Mutmaßung. Jedenfalls habe ich nun die aktuelle Gluon-Firmware für Neuss und für den 841N v8 herunter geladen und manuell geflasht und voilà: es geht jetzt wieder!

Ehrlich gesagt, habe ich bei all den Berichten über Unitymedia, DS-Lite kaum damit gerechnet, dass es die Firmware ist, habe mich also blenden lassen und gleich die Schuld bei UM gesucht.

Meine anderen Probleme mit IPv6 sind davon aber ja höchstwahrscheinlich unabhängig. Egal, hauptsache der FF-Router läuft wieder. :smile:

LG Oliver

1 „Gefällt mir“
6

Der Router sucht Supernodes, die es schon lange nimmer gibt.

1 „Gefällt mir“