FFREK in Sinnersdorf läuft derzeit gar nicht

Community Rhein-Erft
1

Hallo ffrek-Leute,
hallo @utzer,

läuft bei euch aktuell Freifunk oder ist es wie bei mir/uns (Sinnersdorf), dass überhaupt nichts läuft?
Damit meine ich, dass die Knoten zwar auf der Map erscheinen und sich Clients wohl auch anmelden können, aber Traffic geht derzeit gar nichts :frowning:

Kann das evtl. mit den DDOS-Angriffen der letzten Zeit zu tun haben (siehe Bandbreitenprobelm ffdus seit So. 25.09 22h10 bis Di 13h42(OVH GRE-Limit) (gelöst) - #15 von adorfer)? Der dort genannte Engpaß gilt als gelöst. Bei uns aber leider nicht. - Wo hängen wir eigentlich dran???

VG Alex für Freifunk Sinnersdorf

2

Rhein-Erft… das ist doch KBU? Da gab es auf der Mailingliste vor kurzem einiges dazu. Im Forum ist KBU quasi inaktiv.

3

Nee @Imperator, ffrek hängt glaube ich an FFRL via Wupper.
Und da hier derzeit überhaupt nichts funktionert nehme ich nun alle unsere Knoten vom Netz :frowning:

4

:frowning:

Wir hängen [hier][1] dran, da ist der @phip unter anderem Admin und das bringt mich wieder zu dem Punkt, dass wir dringend einen eigenen Server brauchen, was hauptsächlich wie immer am Faktor Zeit scheitert.

Ich habe gerade leider keinen Zugriff auf Internet worüber ich testen kann, ich habe eine Internetverbindung über Handy und zahle für 10GB „nur“ 50 USD. Der Preis ist nicht das Problem, aber hier geht SSH so grade, besser mosh und ich arbeite nur in screen, weil hin und wieder bricht die Verbindung einfach weg. Naja Dritte Welt…

Also hat der @phip eine Ahnung, ob es ein Problem mit dem Routing gibt?

@FreifunkSDF kannst du mal den alten Beitrag raussuchen als du das letzte mal ein Problem hattest und nochmal auf der Konsole auf dem Router schauen ob der Router verbunden ist und mit welchem Server?
[1]: Wupper – Freifunk Rheinland e.V.

5

ich guck gleich mal…

1 „Gefällt mir“
6

Tut mir leid das ich nicht reagiert habe, aber ich hab nicht mal meine E-Mails gelesen seit vorgestern, dafür habe ich Freitag und Samstag insgesamt 27h gearbeitet. Waren Abschlusstests beim Kunden, da bin ich dann quasi voll ausgelastet.

7

Es gibt hier im Kreis KBU und FFREK, wäre toll, damals ™ fanden alle die Idee toll, wenn wir uns hier von KBU ablösen und selber was machen, aber irgendwie läuft es schleppend, wir können jede Unterstützung brauchen, siehe auch hier.

8

So, lass uns mal gucken, folgendes habe ich gemacht + Ergebnisse:
Vom Windows-Notebook (nur mit Freifunk verbunden):

ping 8.8.8.8
Ping wird ausgeführt für 8.8.8.8 mit 32 Bytes Daten:
Antwort von 10.219.38.70: Zielhost nicht erreichbar.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Antwort von 10.219.38.70: Zielhost nicht erreichbar.

Ping-Statistik für 8.8.8.8:
Pakete: Gesendet = 4, Empfangen = 2, Verloren = 2
(50% Verlust),

Vom Freifunk-Router mit Internet-Uplink:

root@Sinnersdorf-4025:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=49 time=29.602 ms
64 bytes from 8.8.8.8: seq=1 ttl=49 time=29.053 ms
64 bytes from 8.8.8.8: seq=2 ttl=49 time=29.170 ms
64 bytes from 8.8.8.8: seq=3 ttl=49 time=28.278 ms
64 bytes from 8.8.8.8: seq=4 ttl=49 time=28.775 ms
64 bytes from 8.8.8.8: seq=5 ttl=49 time=29.125 ms
64 bytes from 8.8.8.8: seq=6 ttl=49 time=28.385 ms
64 bytes from 8.8.8.8: seq=7 ttl=49 time=28.460 ms
64 bytes from 8.8.8.8: seq=8 ttl=49 time=28.652 ms
64 bytes from 8.8.8.8: seq=9 ttl=49 time=29.019 ms
64 bytes from 8.8.8.8: seq=10 ttl=49 time=28.010 ms
^C
— 8.8.8.8 ping statistics —
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 28.010/28.775/29.602 ms
root@Sinnersdorf-4025:~# ping google.com
ping: bad address ‚google.com‘

Was braucht ihr noch, um helfen zu können???

9

Noch ein paar Infos:

vom Windows-Notebook:

tracert 8.8.8.8

Routenverfolgung zu 8.8.8.8 über maximal 30 Hops

1 * * * Zeitüberschreitung der Anforderung.
2 * * * Zeitüberschreitung der Anforderung.
3 * * * Zeitüberschreitung der Anforderung.
4 * * * Zeitüberschreitung der Anforderung.
5 * * * Zeitüberschreitung der Anforderung.
6 * * * Zeitüberschreitung der Anforderung.
7 Mein-Notebook [10.219.38.70] meldet: Zielhost nicht erreichbar.

Ablaufverfolgung beendet.

Vom Freifunk-Router mit Uplink:

root@Sinnersdorf-4025:~# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 192.168.179.1 (192.168.179.1) 0.719 ms 0.362 ms 0.433 ms
2 195.14.226.125 (195.14.226.125) 13.358 ms 13.404 ms 12.898 ms
3 89.1.16.157 (89.1.16.157) 11.094 ms 89.1.16.169 (89.1.16.169) 10.976 ms 89.1.16.157 (89.1.16.157) 11.058 ms
4 78.35.33.54 (78.35.33.54) 15.691 ms 81.173.192.62 (81.173.192.62) 16.519 ms 78.35.18.83 (78.35.18.83) 15.315 ms
5 78.35.18.6 (78.35.18.6) 15.035 ms 15.398 ms 15.467 ms
6 108.170.241.194 (108.170.241.194) 15.616 ms 15.507 ms 16.570 ms
7 209.85.241.127 (209.85.241.127) 16.176 ms 216.239.43.120 (216.239.43.120) 16.068 ms 216.239.47.100 (216.239.47.100) 16.356 ms
8 209.85.246.43 (209.85.246.43) 29.293 ms 108.170.234.123 (108.170.234.123) 29.172 ms 29.515 ms
9 209.85.246.119 (209.85.246.119) 28.956 ms 108.170.234.143 (108.170.234.143) 29.099 ms 29.632 ms
10 * * *
11 8.8.8.8 (8.8.8.8) 29.426 ms 28.875 ms 29.385 ms
root@Sinnersdorf-4025:~#

demeg:

root@Sinnersdorf-4025:~# dmesg
[ 0.000000] Linux version 3.18.23 (gluon@benser) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r46287) ) #1 Mon Jan 11 22:40:33 CET 2016
[ 0.000000] MyLoader: sysp=b6b877a7, boardp=f225bfa2, parts=37b4aff6
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 00019750 (MIPS 74Kc)
[ 0.000000] SoC: Qualcomm Atheros QCA9558 ver 1 rev 0
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 04000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x03ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x03ffffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x03ffffff]
[ 0.000000] On node 0 totalpages: 16384
[ 0.000000] free_area_init_node: node 0, pgdat 803802b0, node_mem_map 81000000
[ 0.000000] Normal zone: 128 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 16384 pages, LIFO batch:3
[ 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: 16256
[ 0.000000] Kernel command line: board=TL-WR1043ND-v2 console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 60812K/65536K available (2615K kernel code, 132K rwdata, 548K rodata, 216K init, 194K bss, 4724K reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.000000] Clocks: CPU:720.000MHz, DDR:600.000MHz, AHB:200.000MHz, Ref:40.000MHz
[ 0.000000] Calibrating delay loop… 358.80 BogoMIPS (lpj=1794048)
[ 0.060000] pid_max: default: 32768 minimum: 301
[ 0.060000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.070000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.070000] NET: Registered protocol family 16
[ 0.080000] MIPS: machine is TP-LINK TL-WR1043ND v2
[ 0.520000] Switched to clocksource MIPS
[ 0.530000] NET: Registered protocol family 2
[ 0.530000] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.530000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.540000] TCP: Hash tables configured (established 1024 bind 1024)
[ 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.560000] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.580000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.580000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.590000] msgmni has been set to 118
[ 0.600000] io scheduler noop registered
[ 0.600000] io scheduler deadline registered (default)
[ 0.600000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.610000] console [ttyS0] disabled
[ 0.640000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A
[ 0.640000] console [ttyS0] enabled
[ 0.650000] bootconsole [early0] disabled
[ 0.660000] m25p80 spi0.0: found s25fl064k, expected m25p80
[ 0.670000] m25p80 spi0.0: s25fl064k (8192 Kbytes)
[ 0.670000] 5 tp-link partitions found on MTD device spi0.0
[ 0.680000] Creating 5 MTD partitions on „spi0.0“:
[ 0.680000] 0x000000000000-0x000000020000 : „u-boot“
[ 0.690000] 0x000000020000-0x000000142f28 : „kernel“
[ 0.690000] 0x000000142f28-0x0000007f0000 : „rootfs“
[ 0.700000] mtd: device 2 (rootfs) set to be root filesystem
[ 0.710000] 1 squashfs-split partitions found on MTD device rootfs
[ 0.710000] 0x000000380000-0x0000007f0000 : „rootfs_data“
[ 0.720000] 0x0000007f0000-0x000000800000 : „art“
[ 0.720000] 0x000000020000-0x0000007f0000 : „firmware“
[ 0.750000] switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0
[ 0.840000] libphy: ag71xx_mdio: probed
[ 1.440000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
[ 1.450000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
[ 2.040000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:SGMII
[ 2.040000] TCP: cubic registered
[ 2.050000] NET: Registered protocol family 17
[ 2.050000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 2.060000] Bridge firewalling registered
[ 2.070000] 8021q: 802.1Q VLAN Support v1.8
[ 2.080000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[ 2.090000] Freeing unused kernel memory: 216K (8039a000 - 803d0000)
[ 3.380000] init: Console is alive
[ 3.380000] init: - watchdog -
[ 5.390000] init: - preinit -
[ 5.940000] eth1: link up (1000Mbps/Full duplex)
[ 5.960000] random: procd urandom read with 9 bits of entropy available
[ 9.270000] jffs2: notice: (384) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 9.280000] mount_root: switching to jffs2 overlay
[ 9.390000] eth1: link down
[ 9.400000] procd: - early -
[ 9.400000] procd: - watchdog -
[ 10.020000] procd: - ubus -
[ 11.030000] procd: - init -
[ 11.810000] NET: Registered protocol family 10
[ 11.820000] tun: Universal TUN/TAP device driver, 1.6
[ 11.830000] tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.com
[ 11.840000] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 11.860000] batman_adv: B.A.T.M.A.N. advanced 2015.1 (compatibility version 15) loaded
[ 11.870000] u32 classifier
[ 11.880000] input device check on
[ 11.880000] Actions configured
[ 11.880000] Mirror/redirect action on
[ 11.900000] netem: version 1.3
[ 11.910000] Loading modules backported from Linux version master-2015-07-21-0-g47cd203
[ 11.920000] Backport generated by backports.git backports-20150626-0-gc1a4168
[ 11.950000] Ebtables v2.0 registered
[ 11.960000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 11.980000] nf_conntrack version 0.5.0 (953 buckets, 3812 max)
[ 12.060000] xt_time: kernel timezone is -0000
[ 12.110000] cfg80211: World regulatory domain updated:
[ 12.120000] cfg80211: DFS Master region: unset
[ 12.120000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 12.130000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.140000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.150000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.150000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 12.160000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 12.170000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 12.180000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.190000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 12.310000] ath: EEPROM regdomain: 0x0
[ 12.310000] ath: EEPROM indicates default country code should be used
[ 12.310000] ath: doing EEPROM country->regdmn map search
[ 12.310000] ath: country maps to regdmn code: 0x3a
[ 12.310000] ath: Country alpha2 being used: US
[ 12.310000] ath: Regpair used: 0x3a
[ 12.330000] ieee80211 phy0: Selected rate control algorithm ‚minstrel_ht‘
[ 12.330000] ieee80211 phy0: Atheros AR9550 Rev:0 mem=0xb8100000, irq=47
[ 12.350000] cfg80211: Regulatory domain changed to country: US
[ 12.350000] cfg80211: DFS Master region: FCC
[ 12.360000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 12.370000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[ 12.370000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
[ 12.380000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
[ 12.390000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
[ 12.400000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[ 12.410000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 22.460000] device eth0 entered promiscuous mode
[ 22.490000] br-wan: port 1(eth0) entered forwarding state
[ 22.490000] br-wan: port 1(eth0) entered forwarding state
[ 22.550000] eth1: link up (1000Mbps/Full duplex)
[ 22.610000] IPv6: ADDRCONF(NETDEV_UP): br-client: link is not ready
[ 22.620000] device br-client entered promiscuous mode
[ 22.630000] IPv6: ADDRCONF(NETDEV_UP): local-node: link is not ready
[ 23.040000] batman_adv: bat0: Adding interface: eth1
[ 23.050000] batman_adv: bat0: The MTU of interface eth1 is too small (1500) 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 1532 would solve the problem.
[ 23.070000] batman_adv: bat0: Interface activated: eth1
[ 23.080000] 8021q: adding VLAN 0 to HW filter on device bat0
[ 23.080000] device bat0 entered promiscuous mode
[ 23.090000] br-client: port 1(bat0) entered forwarding state
[ 23.090000] br-client: port 1(bat0) entered forwarding state
[ 23.110000] IPv6: ADDRCONF(NETDEV_CHANGE): br-client: link becomes ready
[ 23.110000] IPv6: ADDRCONF(NETDEV_CHANGE): local-node: link becomes ready
[ 23.880000] br-wan: port 1(eth0) entered disabled state
[ 23.890000] eth0: link up (1000Mbps/Full duplex)
[ 23.890000] br-wan: port 1(eth0) entered forwarding state
[ 23.900000] br-wan: port 1(eth0) entered forwarding state
[ 24.160000] cfg80211: Regulatory domain changed to country: DE
[ 24.170000] cfg80211: DFS Master region: ETSI
[ 24.170000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 24.180000] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 24.190000] cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 24.200000] cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 24.210000] cfg80211: (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
[ 24.220000] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 24.810000] batman_adv: bat0: Changing gw mode from: off to: client
[ 24.870000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15
[ 24.940000] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled
[ 24.940000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000
[ 25.090000] br-client: port 1(bat0) entered forwarding state
[ 25.110000] batman_adv: bat0: Adding interface: mesh-vpn
[ 25.110000] 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 1532 would solve the problem.
[ 25.140000] batman_adv: bat0: Interface activated: mesh-vpn
[ 25.140000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled
[ 25.890000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 5 is up
[ 25.900000] br-wan: port 1(eth0) entered forwarding state
[ 26.600000] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
[ 26.700000] device client0 entered promiscuous mode
[ 26.700000] br-client: port 2(client0) entered forwarding state
[ 26.710000] br-client: port 2(client0) entered forwarding state
[ 26.890000] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
[ 27.070000] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
[ 27.090000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
[ 27.270000] batman_adv: bat0: Adding interface: mesh0
[ 27.280000] batman_adv: bat0: Interface activated: mesh0
[ 28.710000] br-client: port 2(client0) entered forwarding state
[ 45.190000] random: nonblocking pool is initialized
root@Sinnersdorf-4025:~#

10

logread

root@Sinnersdorf-4025:~# logread
Sun Jan 17 23:49:39 2016 daemon.notice netifd: Interface ‚wan6‘ is now down
Sun Jan 17 23:49:39 2016 daemon.notice netifd: Interface ‚wan6‘ is setting up now
Sun Jan 17 23:49:39 2016 daemon.notice netifd: wan (1345): Received SIGTERM
Sun Jan 17 23:49:39 2016 daemon.notice netifd: Interface ‚wan‘ is now down
Sun Jan 17 23:49:39 2016 daemon.notice netifd: Interface ‚wan‘ is setting up now
Sun Jan 17 23:49:40 2016 daemon.notice netifd: wan (1487): udhcpc (v1.23.2) started
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 24.810000] batman_adv: bat0: Changing gw mode from: off to: client
Sun Jan 17 23:49:40 2016 daemon.notice fastd[1494]: fastd v17 starting
Sun Jan 17 23:49:40 2016 daemon.notice fastd[1494]: changed to UID 0, GID 800
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 24.870000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15
Sun Jan 17 23:49:40 2016 daemon.notice netifd: Interface ‚mesh_vpn‘ is enabled
Sun Jan 17 23:49:40 2016 daemon.notice netifd: Network device ‚mesh-vpn‘ link is up
Sun Jan 17 23:49:40 2016 daemon.notice netifd: Interface ‚mesh_vpn‘ has link connectivity
Sun Jan 17 23:49:40 2016 daemon.notice netifd: Interface ‚mesh_vpn‘ is setting up now
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer6>
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 24.940000] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 24.940000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000
Sun Jan 17 23:49:40 2016 daemon.notice netifd: wan (1487): Sending discover…
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer5>
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_fastd4>
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 25.090000] br-client: port 1(bat0) entered forwarding state
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 25.110000] batman_adv: bat0: Adding interface: mesh-vpn
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 25.110000] 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 1532 would solve the problem.
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 25.140000] batman_adv: bat0: Interface activated: mesh-vpn
Sun Jan 17 23:49:40 2016 kern.info kernel: [ 25.140000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer1>
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer3>
Sun Jan 17 23:49:40 2016 user.emerg syslog: setting up led USB
Sun Jan 17 23:49:40 2016 user.emerg syslog: Skipping trigger ‚usbdev‘ for led ‚USB‘ due to missing kernel module
Sun Jan 17 23:49:40 2016 daemon.notice netifd: Interface ‚mesh_vpn‘ is now up
Sun Jan 17 23:49:40 2016 user.emerg syslog: setting up led WLAN
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer9>
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer7>
Sun Jan 17 23:49:40 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer8>
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer0>
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: adding peer <mesh_vpn_backbone_peer_peer2>
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd02.ffrek.de' for peer <mesh_vpn_backbone_peer_peer2>... Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd00.ffrek.de’ for peer <mesh_vpn_backbone_peer_peer0>…
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd08.ffrek.de' for peer <mesh_vpn_backbone_peer_peer8>... Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd07.ffrek.de’ for peer <mesh_vpn_backbone_peer_peer7>…
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd09.ffrek.de' for peer <mesh_vpn_backbone_peer_peer9>... Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd03.ffrek.de’ for peer <mesh_vpn_backbone_peer_peer3>…
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd01.ffrek.de' for peer <mesh_vpn_backbone_peer_peer1>... Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd04.ffrek.de’ for peer <mesh_vpn_backbone_peer_fastd4>…
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd05.ffrek.de' for peer <mesh_vpn_backbone_peer_peer5>... Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd06.ffrek.de’ for peer <mesh_vpn_backbone_peer_peer6>…
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd07.ffrek.de' failed: Name or service not known Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd09.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd03.ffrek.de' failed: Name or service not known Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd05.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd06.ffrek.de' failed: Name or service not known Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd02.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd08.ffrek.de' failed: Name or service not known Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd04.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd01.ffrek.de' failed: Name or service not known Sun Jan 17 23:49:41 2016 daemon.info fastd[1494]: resolving host fastd00.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:49:41 2016 kern.info kernel: [ 25.890000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 5 is up
Sun Jan 17 23:49:41 2016 kern.info kernel: [ 25.900000] br-wan: port 1(eth0) entered forwarding state
Sun Jan 17 23:49:41 2016 daemon.notice netifd: wan (1487): Sending select for 192.168.179.40…
Sun Jan 17 23:49:41 2016 daemon.notice netifd: wan (1487): Lease of 192.168.179.40 obtained, lease time 864000
Sun Jan 17 23:49:41 2016 daemon.notice netifd: Interface ‚wan‘ is now up
Sun Jan 17 23:49:41 2016 daemon.notice netifd: radio0 (1279): Configuration file: /var/run/hostapd-phy0.conf
Sun Jan 17 23:49:41 2016 kern.info kernel: [ 26.600000] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 26.700000] device client0 entered promiscuous mode
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 26.700000] br-client: port 2(client0) entered forwarding state
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 26.710000] br-client: port 2(client0) entered forwarding state
Sun Jan 17 23:49:42 2016 daemon.notice netifd: radio0 (1279): client0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Jan 17 23:49:42 2016 daemon.notice netifd: radio0 (1279): Using interface client0 with hwaddr c2:4c:01:39:4d:58 and ssid „Freifunk“
Sun Jan 17 23:49:42 2016 daemon.notice netifd: radio0 (1279): client0: interface state COUNTRY_UPDATE->ENABLED
Sun Jan 17 23:49:42 2016 daemon.notice netifd: radio0 (1279): client0: AP-ENABLED
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 26.890000] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
Sun Jan 17 23:49:42 2016 daemon.info procd: - init complete -
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 27.070000] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 27.090000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Sun Jan 17 23:49:42 2016 daemon.notice netifd: Network device ‚client0‘ link is up
Sun Jan 17 23:49:42 2016 daemon.notice netifd: Network device ‚mesh0‘ link is up
Sun Jan 17 23:49:42 2016 daemon.notice netifd: Interface ‚mesh_radio0‘ is enabled
Sun Jan 17 23:49:42 2016 daemon.notice netifd: Interface ‚mesh_radio0‘ has link connectivity
Sun Jan 17 23:49:42 2016 daemon.notice netifd: Interface ‚mesh_radio0‘ is setting up now
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 27.270000] batman_adv: bat0: Adding interface: mesh0
Sun Jan 17 23:49:42 2016 kern.info kernel: [ 27.280000] batman_adv: bat0: Interface activated: mesh0
Sun Jan 17 23:49:42 2016 daemon.notice netifd: Interface ‚mesh_radio0‘ is now up
Sun Jan 17 23:49:42 2016 daemon.info dnsmasq[1699]: started, version 2.73 cachesize 150
Sun Jan 17 23:49:42 2016 daemon.info dnsmasq[1699]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Sun Jan 17 23:49:42 2016 daemon.info dnsmasq[1699]: DNS service limited to local subnets
Sun Jan 17 23:49:42 2016 daemon.info dnsmasq[1699]: using local addresses only for domain lan
Sun Jan 17 23:49:42 2016 daemon.warn dnsmasq[1699]: no servers found in /tmp/resolv.conf.auto, will retry
Sun Jan 17 23:49:42 2016 daemon.info dnsmasq[1699]: read /etc/hosts - 1 addresses
Sun Jan 17 23:49:43 2016 user.notice firewall: Reloading firewall due to ifup of local_node (local-node)
Sun Jan 17 23:49:44 2016 kern.info kernel: [ 28.710000] br-client: port 2(client0) entered forwarding state
Sun Jan 17 23:49:46 2016 user.notice firewall: Reloading firewall due to ifup of wan (br-wan)
Sun Jan 17 23:49:47 2016 daemon.info dnsmasq[1118]: reading /var/gluon/wan-dnsmasq/resolv.conf
Sun Jan 17 23:49:47 2016 daemon.info dnsmasq[1118]: using nameserver 192.168.179.1#53
Sun Jan 17 23:49:50 2016 daemon.notice netifd: Interface ‚client‘ is now up
Sun Jan 17 23:49:50 2016 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Sun Jan 17 23:49:59 2016 daemon.info fastd[1494]: resolving host fastd01.ffrek.de' for peer <mesh_vpn_backbone_peer_peer1>... Sun Jan 17 23:49:59 2016 daemon.info fastd[1494]: resolved host fastd01.ffrek.de’ successfully
Sun Jan 17 23:49:59 2016 daemon.info fastd[1494]: resolving host fastd06.ffrek.de' for peer <mesh_vpn_backbone_peer_peer6>... Sun Jan 17 23:49:59 2016 daemon.info fastd[1494]: resolved host fastd06.ffrek.de’ successfully
Sun Jan 17 23:50:00 2016 kern.notice kernel: [ 45.190000] random: nonblocking pool is initialized
Sun Jan 17 23:50:01 2016 daemon.info fastd[1494]: resolving host fastd00.ffrek.de' for peer <mesh_vpn_backbone_peer_peer0>... Sun Jan 17 23:50:01 2016 daemon.info fastd[1494]: resolved host fastd00.ffrek.de’ successfully
Sun Jan 17 23:50:01 2016 daemon.info fastd[1494]: resolving host fastd03.ffrek.de' for peer <mesh_vpn_backbone_peer_peer3>... Sun Jan 17 23:50:01 2016 daemon.info fastd[1494]: resolving host fastd03.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:50:02 2016 daemon.info fastd[1494]: resolving host fastd02.ffrek.de' for peer <mesh_vpn_backbone_peer_peer2>... Sun Jan 17 23:50:02 2016 daemon.info fastd[1494]: resolved host fastd02.ffrek.de’ successfully
Sun Jan 17 23:50:03 2016 daemon.info fastd[1494]: resolving host fastd04.ffrek.de' for peer <mesh_vpn_backbone_peer_fastd4>... Sun Jan 17 23:50:03 2016 daemon.info fastd[1494]: resolved host fastd04.ffrek.de’ successfully
Sun Jan 17 23:50:03 2016 daemon.info fastd[1494]: resolving host fastd09.ffrek.de' for peer <mesh_vpn_backbone_peer_peer9>... Sun Jan 17 23:50:03 2016 daemon.info fastd[1494]: resolving host fastd07.ffrek.de’ for peer <mesh_vpn_backbone_peer_peer7>…
Sun Jan 17 23:50:03 2016 daemon.info fastd[1494]: resolved host fastd07.ffrek.de' successfully Sun Jan 17 23:50:03 2016 daemon.info fastd[1494]: resolving host fastd09.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:50:05 2016 daemon.info fastd[1494]: resolving host fastd08.ffrek.de' for peer <mesh_vpn_backbone_peer_peer8>... Sun Jan 17 23:50:05 2016 daemon.info fastd[1494]: resolved host fastd08.ffrek.de’ successfully
Sun Jan 17 23:50:05 2016 daemon.info fastd[1494]: resolving host fastd05.ffrek.de' for peer <mesh_vpn_backbone_peer_peer5>... Sun Jan 17 23:50:05 2016 daemon.info fastd[1494]: resolving host fastd05.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:50:19 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer1>[[2001:41d0:c:95c::188]:50169]…
Sun Jan 17 23:50:19 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer6>[[2a00:13c8:1000:2::b]:50169]…
Sun Jan 17 23:50:20 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer2>[[2a01:4f8:140:64d8::2]:50169]…
Sun Jan 17 23:50:21 2016 daemon.info fastd[1494]: resolving host fastd03.ffrek.de' for peer <mesh_vpn_backbone_peer_peer3>... Sun Jan 17 23:50:21 2016 daemon.info fastd[1494]: resolving host fastd03.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:50:21 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer0>[[2001:41d0:c:95c::176]:50169]…
Sun Jan 17 23:50:21 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer7>[37.120.168.152:50169]…
Sun Jan 17 23:50:21 2016 daemon.info fastd[1494]: resolving host fastd07.ffrek.de' for peer <mesh_vpn_backbone_peer_peer7>... Sun Jan 17 23:50:21 2016 daemon.info fastd[1494]: resolved host fastd07.ffrek.de’ successfully
Sun Jan 17 23:50:23 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_fastd4>[[2a00:13c8:1000:2::a]:50169]…
Sun Jan 17 23:50:24 2016 daemon.info fastd[1494]: resolving host fastd05.ffrek.de' for peer <mesh_vpn_backbone_peer_peer5>... Sun Jan 17 23:50:24 2016 daemon.info fastd[1494]: resolving host fastd05.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:50:25 2016 daemon.info fastd[1494]: resolving host fastd09.ffrek.de' for peer <mesh_vpn_backbone_peer_peer9>... Sun Jan 17 23:50:25 2016 daemon.info fastd[1494]: resolving host fastd09.ffrek.de’ failed: Name or service not known
Sun Jan 17 23:50:25 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer8>[46.38.236.87:50169]…
Sun Jan 17 23:50:25 2016 daemon.info fastd[1494]: resolving host fastd08.ffrek.de' for peer <mesh_vpn_backbone_peer_peer8>... Sun Jan 17 23:50:25 2016 daemon.info fastd[1494]: resolved host fastd08.ffrek.de’ successfully
Sun Jan 17 23:50:40 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169]…
Sun Jan 17 23:50:40 2016 daemon.info fastd[1494]: resolving host fastd06.ffrek.de' for peer <mesh_vpn_backbone_peer_peer6>... Sun Jan 17 23:50:40 2016 daemon.info fastd[1494]: resolved host fastd06.ffrek.de’ successfully
Sun Jan 17 23:50:40 2016 daemon.info fastd[1494]: received handshake response from <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169] using fastd v17
Sun Jan 17 23:50:40 2016 daemon.info fastd[1494]: 185.46.137.139:50169 authorized as <mesh_vpn_backbone_peer_peer6>
Sun Jan 17 23:50:40 2016 daemon.notice fastd[1494]: connection with <mesh_vpn_backbone_peer_peer6> established.
Sun Jan 17 23:50:40 2016 daemon.info fastd[1494]: new session with <mesh_vpn_backbone_peer_peer6> established using method salsa2012+umac'. Mon Jan 18 00:27:54 2016 daemon.info hostapd: client0: STA d8:d1:cb:7e:f3:7a IEEE 802.11: authenticated Mon Jan 18 00:27:54 2016 daemon.info hostapd: client0: STA d8:d1:cb:7e:f3:7a IEEE 802.11: associated (aid 1) Mon Jan 18 00:33:35 2016 daemon.info hostapd: client0: STA d8:d1:cb:7e:f3:7a IEEE 802.11: disassociated due to inactivity Mon Jan 18 00:33:36 2016 daemon.info hostapd: client0: STA d8:d1:cb:7e:f3:7a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Mon Jan 18 00:45:19 2016 daemon.info fastd[1494]: refreshing session with <mesh_vpn_backbone_peer_peer6> Mon Jan 18 00:45:20 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169]... Mon Jan 18 00:45:20 2016 daemon.info fastd[1494]: received handshake response from <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169] using fastd v17 Mon Jan 18 00:45:20 2016 daemon.info fastd[1494]: 185.46.137.139:50169 authorized as <mesh_vpn_backbone_peer_peer6> Mon Jan 18 00:45:20 2016 daemon.info fastd[1494]: new session with <mesh_vpn_backbone_peer_peer6> established using method salsa2012+umac’.
Mon Jan 18 01:39:03 2016 daemon.info fastd[1494]: refreshing session with <mesh_vpn_backbone_peer_peer6>
Mon Jan 18 01:39:03 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169]…
Mon Jan 18 01:39:03 2016 daemon.info fastd[1494]: received handshake response from <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169] using fastd v17
Mon Jan 18 01:39:03 2016 daemon.info fastd[1494]: 185.46.137.139:50169 authorized as <mesh_vpn_backbone_peer_peer6>
Mon Jan 18 01:39:03 2016 daemon.info fastd[1494]: new session with <mesh_vpn_backbone_peer_peer6> established using method salsa2012+umac'. Mon Jan 18 02:12:32 2016 daemon.info hostapd: client0: STA 08:ec:a9:91:3e:c8 IEEE 802.11: authenticated Mon Jan 18 02:12:32 2016 daemon.info hostapd: client0: STA 08:ec:a9:91:3e:c8 IEEE 802.11: associated (aid 1) Mon Jan 18 02:31:54 2016 daemon.info fastd[1494]: refreshing session with <mesh_vpn_backbone_peer_peer6> Mon Jan 18 02:31:54 2016 daemon.info fastd[1494]: sending handshake to <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169]... Mon Jan 18 02:31:54 2016 daemon.info fastd[1494]: received handshake response from <mesh_vpn_backbone_peer_peer6>[185.46.137.139:50169] using fastd v17 Mon Jan 18 02:31:55 2016 daemon.info fastd[1494]: 185.46.137.139:50169 authorized as <mesh_vpn_backbone_peer_peer6> Mon Jan 18 02:31:55 2016 daemon.info fastd[1494]: new session with <mesh_vpn_backbone_peer_peer6> established using method salsa2012+umac’.
Mon Jan 18 02:47:25 2016 authpriv.info dropbear[2581]: Child connection from fda0:747e:ab29:5016:6f:26c9:3bf3:9943:63301
Mon Jan 18 02:47:30 2016 authpriv.notice dropbear[2581]: Pubkey auth succeeded for ‚root‘ with key md5 f9:46:04:95:a9:50:14:87:43:8d:fc:c1:9c:ec:ac:31 from fda0:747e:ab29:5016:6f:26c9:3bf3:9943:63301
root@Sinnersdorf-4025:~#

Nun mach ich erstmal Schluss - bis morgen :smile:

1 „Gefällt mir“
11

Hi Leute,
was können wir nochmal ausprobieren/testen?
Liest @phip mit?

Vg

12

Das klingt nach „IPv4-Gateway nicht erreichbar“ aka „DHCP vergibt nicht funktionionsfähiges Default-Gateway“.

13

So, habe nun ein paar Test gemacht, vielleicht kommen wir damit weiter…

ipconfig

Ethernet-Adapter Ethernet:
Verbindungsspezifisches DNS-Suffix:
IPv6-Adresse. . . . . . . . . . . : fda0:747e:ab29:5016:c842:d150:66f:8e8d
Temporäre IPv6-Adresse. . . . . . : fda0:747e:ab29:5016:c1d1:4d25:3e10:221e
Verbindungslokale IPv6-Adresse . : fe80::c842:d150:66f:8e8d%3
IPv4-Adresse . . . . . . . . . . : 10.219.45.33
Subnetzmaske . . . . . . . . . . : 255.192.0.0
Standardgateway . . . . . . . . . : 10.186.0.244

ping 8.8.8.8

Ping wird ausgeführt für 8.8.8.8 mit 32 Bytes Daten:
Antwort von 10.219.45.33: Zielhost nicht erreichbar.
Antwort von 10.219.45.33: Zielhost nicht erreichbar.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Ping-Statistik für 8.8.8.8:
Pakete: Gesendet = 4, Empfangen = 2, Verloren = 2
(50% Verlust),

ping 127.0.0.1

Ping wird ausgeführt für 127.0.0.1 mit 32 Bytes Daten:
Antwort von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128
Antwort von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128
Antwort von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128
Antwort von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128
Ping-Statistik für 127.0.0.1:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

ping 10.219.45.33

Ping wird ausgeführt für 10.219.45.33 mit 32 Bytes Daten:
Antwort von 10.219.45.33: Bytes=32 Zeit<1ms TTL=128
Antwort von 10.219.45.33: Bytes=32 Zeit<1ms TTL=128
Antwort von 10.219.45.33: Bytes=32 Zeit<1ms TTL=128
Antwort von 10.219.45.33: Bytes=32 Zeit<1ms TTL=128
Ping-Statistik für 10.219.45.33:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

ping 10.186.0.244

Ping wird ausgeführt für 10.186.0.244 mit 32 Bytes Daten:
Antwort von 10.219.45.33: Zielhost nicht erreichbar.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Ping-Statistik für 10.186.0.244:
Pakete: Gesendet = 4, Empfangen = 1, Verloren = 3
(75% Verlust),

ping fda0:747e:ab29:5016:c24a:ff:fe39:4d58 (Uplink-Knoten)

Ping wird ausgeführt für fda0:747e:ab29:5016:c24a:ff:fe39:4d58 mit 32 Bytes Daten:
Antwort von fda0:747e:ab29:5016:c24a:ff:fe39:4d58: Zeit=828ms
Antwort von fda0:747e:ab29:5016:c24a:ff:fe39:4d58: Zeit=6ms
Antwort von fda0:747e:ab29:5016:c24a:ff:fe39:4d58: Zeit=4ms
Antwort von fda0:747e:ab29:5016:c24a:ff:fe39:4d58: Zeit=2ms
Ping-Statistik für fda0:747e:ab29:5016:c24a:ff:fe39:4d58:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 2ms, Maximum = 828ms, Mittelwert = 210ms

Somit kann ich das Standardgateway (10.186.0.244) nicht erreichen :frowning:

14

Würde meine obige Vermutung bestätigen.
Oder aber Gateway auf einem anderen Supernode, Quertraffic mit hohem Packetloss.
Setze mal manuell eines der anderen möglichen gateways von Hand.

15

Leider weiß ich nicht, welche anderen Gateways zum Testen in Frage kommen.
Werde nun erstmal auf die Rückkehr von @utzer warten.
Danke für die Hilfe @adorfer

16

Du kannst einfach mal .240 bis .248 durchprobieren.

1 „Gefällt mir“
17

@FreifunkSDF kannst du mal an deinem PC ein anderes Gateway setzen, ich denke das ist es was der @adorfer meint und dann noch mal probieren? Probier mal durch.

Hat vielleicht noch jemand eine Idee wie man den @phip erreichen kann, ich denke da muss nur ein Dienst oder so neugestartet werden, ggf. ist auch einer der Sever irgendwie anders gestört. Hat da noch jemand Zugriff auf die Server in der Domäne Wupper?

18

Hey @utzer,
welcome home :smile:

Hab mal weiter getestet. Vom Notebook kann ich die anderen GWs (.240-.248) auch nciht erreichen.
Wie stell ich das Standard-GW beim Uplink-Knoten um?

Welchen DHCP-Server nutzen wir? Muss da evtl. der Server/Dienst neu gestartet werden???

19

Gute Frage, ich bin nicht sicher, ich dachte @adorfer meinte den Gateway am Client, also in Windows.

Das ist sehr gut möglich, aber darauf haben wir mangels eigenem Server keinen Zugriff.

20

Wir sollten wohl eine komplett eigene Domäne aufbauen… Seufz. Wahrscheinlich kann man da auch mit anderen kooperieren, eben gegenseitig Aufgaben übernehmen, aber eben alles komplett selber betreiben ist sicherlich unumgänglich. :-/

1 „Gefällt mir“