Hyper Backup Backup über VPN (fehlerhafter MTU?)

Flipper92 · 19. Sep 2020

Hallo zusammen,
ich versuche seit mehreren Tagen ein externes Backup auf eine entfernte NAS zu sichern.

Zuerst zum Aufbau:
Am Standort 1 (Hauptnetzwerk):
- DS1618+ mit OpenVPN Server (=NAS-A)
- 1000/50 Mbit/s Unitymedia Internet

Am Standort 2 (Eltern)
- DS216j (=NAS-B)
- 250/25 Mbit/s Unitymedia Internet

Aufgabe:
1. Beide Netzwerke sollen nicht komplett miteinander Verbunden werden. (Stichwort: SmartHome und Unerfahrene Internet-Nutzer)
2. Die Daten auf der NAS-A sollen auf die NAS-B gesichert werden.
3. Keine Sicherung der Daten von NAS-B auf NAS-A

Aktueller Stand:
Auf NAS-A ist Hyper Backup eingerichtet und auf NAS-B ist Hyper Backup Vault installiert. Ich hab die NAS-B auch zuerst in meinem Netzwerk (Standort 1) eingerichtet und die erste Sicherung laufen lassen. Das hat soweit auch gut Funktioniert.
Nun steht die NAS-B bei meinen Eltern und ich hab eine VPN Verbindung zwischen NAS-A und NAS-B hinbekommen. (Laut VPN Server und der Auflistung dort)
Ein Ping von NAS-A auf die "VPN dynamische IP" der NAS-B funktioniert.
In Hyper Backup auf NAS-A wird auch die NAS-B als "Online" und auch die Größe wird angezeigt.

Was hab ich noch gemacht:
Den Datenfluss hab ich auf beiden NAS reduziert auf 200-1000Mbit/s. -> Wie hier beschrieben.
Durch Pings hab ich einen MTU von 1300 ermittelt und dies auf der NAS-B eingestellt (sogar reduziert).

Fehlermeldung:
So und nun kommen wir zum Fehler. Wenn das Backup ausgeführt werden soll, dann kommt die Meldung "Übertragung fehlgeschlagen wegen unangemessener MTU."
Im Protokoll steht dann:

Code:

Error    2020/09/19 17:19:45    SYSTEM    [Network][Synology NAS 1] Failed to run backup task.
Error    2020/09/19 17:19:00    SYSTEM    [Network][Synology NAS 1] Failed to backup data.
Error    2020/09/19 17:18:58    SYSTEM    [Network][Synology NAS 1] Exception occurred while backing up data. (Failed to transfer data to the target. Maybe MTU size is not appropriate for the network.)
Error    2020/09/19 17:18:58    SYSTEM    [Network][Synology NAS 1] Failed to access the backup destination. (Failed to transfer data to the target. Maybe MTU size is not appropriate for the network.)

Ausschnitte aus den Konsolen:
Ich hab hier nun ein paar Auszüge aus den Konsolen:

NAS-A

Code:

USER@NAS-A:~$ ifconfig
bond0     Link encap:Ethernet  HWaddr 00:11:32:8D:46:C7
          inet addr:192.168.178.60  Bcast:192.168.178.255  Mask:255.255.255.0
          inet6 addr: fe80::211:32ff:fe8d:46c7/64 Scope:Link
          inet6 addr: 2a02:8070:aac:2000:211:32ff:fe8d:46c7/64 Scope:Global
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:650127 errors:0 dropped:0 overruns:0 frame:0
          TX packets:915930 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:504599599 (481.2 MiB)  TX bytes:1148296108 (1.0 GiB)

docker0   Link encap:Ethernet  HWaddr 02:42:5E:10:31:9C
          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
          inet6 addr: fe80::42:5eff:fe10:319c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10789 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11840 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11274991 (10.7 MiB)  TX bytes:30102580 (28.7 MiB)

eth0      Link encap:Ethernet  HWaddr 00:11:32:8D:46:C7
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:328148 errors:0 dropped:0 overruns:0 frame:0
          TX packets:457863 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:55158282 (52.6 MiB)  TX bytes:582646606 (555.6 MiB)

eth1      Link encap:Ethernet  HWaddr 00:11:32:8D:46:C8
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:321979 errors:0 dropped:0 overruns:0 frame:0
          TX packets:458067 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:449441317 (428.6 MiB)  TX bytes:565649502 (539.4 MiB)

eth2      Link encap:Ethernet  HWaddr 00:11:32:8D:46:C9
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth3      Link encap:Ethernet  HWaddr 00:11:32:8D:46:CA
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:7126 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7126 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:951869 (929.5 KiB)  TX bytes:951869 (929.5 KiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.179.1  P-t-P:192.168.179.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:193 errors:0 dropped:0 overruns:0 frame:0
          TX packets:386 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:15064 (14.7 KiB)  TX bytes:420644 (410.7 KiB)

NAS-B

Code:

USER@NAS-B:/$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:32:51:83:0C 
          inet addr:192.168.0.219  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1250  Metric:1
          RX packets:5492 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9260 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1024
          RX bytes:2088198 (1.9 MiB)  TX bytes:6705344 (6.3 MiB)
          Interrupt:73

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2473 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2473 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:330082 (322.3 KiB)  TX bytes:330082 (322.3 KiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          inet addr:192.168.179.6  P-t-P:192.168.179.5  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:68 errors:0 dropped:0 overruns:0 frame:0
          TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:26533 (25.9 KiB)  TX bytes:11546 (11.2 KiB)

Ich weiß nicht mehr wo ich weitersuchen soll.

Anzeige · 19. Sep 2020

Hallo Flipper92,

Bücher und Hardware zum Thema gibt es bei Amazon: Backup über VPN (fehlerhafter MTU?)

Fusion · 20. Sep 2020

Stell mal die MTU einfach auf standard zurück und probiers nochmal

Flipper92 · 20. Sep 2020

Code:

USER@NAS-B:/$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:32:51:83:0C
          inet addr:192.168.0.219  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: 2a02:8071:81a9:800::b30a/64 Scope:Global
          inet6 addr: 2a02:8071:81a9:800:211:32ff:fe51:830c/64 Scope:Global
          inet6 addr: fe80::211:32ff:fe51:830c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4143 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4977 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1024
          RX bytes:1109856 (1.0 MiB)  TX bytes:3321011 (3.1 MiB)
          Interrupt:73

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1248 (1.2 KiB)  TX bytes:1248 (1.2 KiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.179.6  P-t-P:192.168.179.5  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:1751 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:439389 (429.0 KiB)  TX bytes:2239342 (2.1 MiB)

Hab es wieder zurückgestellt.
Aber da der Fehler ja bereits vor dem Umstellen aufgetreten ist, bringt es nichts. Hab es auch gerade (nach einem Neustart von NAS-B) nochmal getestet.
Mit der selben Fehlermeldung fehlgeschlagen.

Interessanterweise ist die Integritätsprüfung (mit NAS-B MTU 1250) heute nacht durchgelaufen.

Zudem hab ich wie folgt auch eine "bessere" MTU von ~1300 ermittelt.
Per SSH auf NAS-A zur NAS-B (192.168.178.6):

Code:

USER@NAS-A:~$ sudo ping -s 1500 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1500(1528) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 8999ms

USER@NAS-A:~$ sudo ping -s 1300 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1300(1328) bytes of data.                              1308 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=30.7 ms                             1308 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=26.1 ms                             1308 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=27.1 ms                             1308 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=26.2 ms                             1308 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=27.5 ms                             
--- 192.168.179.6 ping statistics ---                                                     5 packets transmitted, 5 received, 0% packet loss, time 4004ms                            rtt min/avg/max/mdev = 26.179/27.584/30.728/1.663 ms                                      USER@NAS-A:~$ sudo ping -s 1350 -c 5 -M do 192.168.179.6                        PING 192.168.179.6 (192.168.179.6) 1350(1378) bytes of data.                             
--- 192.168.179.6 ping statistics ---                                                     5 packets transmitted, 0 received, 100% packet loss, time 4004ms                         
USER@NAS-A:~$ sudo ping -s 1322 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1322(1350) bytes of data.

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

USER@NAS-A:~$ sudo ping -s 1300 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1300(1328) bytes of data.
1308 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=34.5 ms
1308 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=25.6 ms
1308 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=26.2 ms
1308 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=27.0 ms
1308 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=25.1 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 25.133/27.712/34.518/3.461 ms
USER@NAS-A:~$ sudo ping -s 1305 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1305(1333) bytes of data.
1313 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=78.0 ms
1313 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=86.9 ms
1313 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=61.7 ms
1313 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=60.9 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4002ms
rtt min/avg/max/mdev = 60.931/71.908/86.912/11.031 ms
USER@NAS-A:~$ sudo ping -s 1310 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1310(1338) bytes of data.
1318 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=64.6 ms
1318 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=61.5 ms
1318 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=26.3 ms
1318 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=26.6 ms
1318 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=47.2 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 26.390/45.271/64.605/16.411 ms
USER@NAS-A:~$ sudo ping -s 1315 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1315(1343) bytes of data.
1323 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=30.5 ms
1323 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=32.9 ms
1323 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=36.1 ms
1323 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=33.1 ms
1323 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=24.1 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 24.173/31.384/36.113/4.025 ms
USER@NAS-A:~$ sudo ping -s 1320 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1320(1348) bytes of data.
1328 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=269 ms
1328 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=245 ms
1328 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=265 ms
1328 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=236 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 3999ms
rtt min/avg/max/mdev = 236.837/254.311/269.599/13.593 ms
USER@NAS-A:~$ sudo ping -s 1325 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1325(1353) bytes of data.

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

USER@NAS-A:~$ sudo ping -s 1321 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1321(1349) bytes of data.

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms

USER@NAS-A:~$ sudo ping -s 1300 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1300(1328) bytes of data.
1308 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=218 ms
1308 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=275 ms
1308 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=247 ms
1308 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=315 ms
1308 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=314 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 218.636/274.393/315.774/37.729 ms
USER@NAS-A:~$ sudo ping -s 1315 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1315(1343) bytes of data.

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms

USER@NAS-A:~$ sudo ping -s 1305 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1305(1333) bytes of data.
1313 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=28.3 ms
1313 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=24.9 ms
1313 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=29.3 ms
1313 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=27.5 ms
1313 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=34.5 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 24.932/28.957/34.585/3.170 ms
USER@NAS-A:~$ sudo ping -s 1304 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1304(1332) bytes of data.
1312 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=129 ms
1312 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=93.0 ms
1312 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=115 ms
1312 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=132 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4002ms
rtt min/avg/max/mdev = 93.042/117.527/132.699/15.623 ms
USER@NAS-A:~$ sudo ping -s 1303 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1303(1331) bytes of data.
1311 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=36.8 ms
1311 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=24.2 ms
1311 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=26.1 ms
1311 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=49.8 ms
1311 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=26.1 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 24.255/32.664/49.867/9.673 ms
USER@NAS-A:~$ sudo ping -s 1302 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1302(1330) bytes of data.
1310 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=28.1 ms
1310 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=28.9 ms
1310 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=25.7 ms
1310 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=25.7 ms
1310 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=25.8 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 25.767/26.920/28.992/1.384 ms
USER@NAS-A:~$ sudo ping -s 1301 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1301(1329) bytes of data.
1309 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=32.3 ms
1309 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=28.6 ms
1309 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=26.7 ms
1309 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=29.0 ms
1309 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=30.8 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 26.742/29.536/32.391/1.936 ms
USER@NAS-A:~$ sudo ping -s 1300 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1300(1328) bytes of data.
1308 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=110 ms
1308 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=64.5 ms
1308 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=100 ms
1308 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=85.4 ms
1308 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=111 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 64.593/94.369/111.371/17.541 ms
USER@NAS-A:~$ sudo ping -s 1299 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1299(1327) bytes of data.
1307 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=303 ms
1307 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=305 ms
1307 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=272 ms
1307 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=303 ms
1307 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=281 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 272.446/293.003/305.098/13.570 ms
USER@NAS-A:~$ sudo ping -s 1298 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1298(1326) bytes of data.
1306 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=33.6 ms
1306 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=25.2 ms
1306 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=25.8 ms
1306 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=26.3 ms
1306 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=28.4 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 25.277/27.916/33.679/3.074 ms
USER@NAS-A:~$ sudo ping -s 1297 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1297(1325) bytes of data.
1305 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=248 ms
1305 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=46.2 ms
1305 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=33.1 ms
1305 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=403 ms
1305 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=208 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 33.124/187.948/403.979/137.685 ms
USER@NAS-A:~$ sudo ping -s 1296 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1296(1324) bytes of data.
1304 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=425 ms
1304 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=421 ms
1304 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=415 ms
1304 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=412 ms
1304 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=414 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 412.041/417.776/425.836/5.087 ms
USER@NAS-A:~$ sudo ping -s 1295 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1295(1323) bytes of data.
1303 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=28.1 ms
1303 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=37.1 ms
1303 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=24.5 ms
1303 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=27.9 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4003ms
rtt min/avg/max/mdev = 24.581/29.455/37.150/4.667 ms
USER@NAS-A:~$ sudo ping -s 1295 -c 5 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1295(1323) bytes of data.
1303 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=57.0 ms
1303 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=64.3 ms
1303 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=37.3 ms
1303 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=27.0 ms
1303 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=52.9 ms

--- 192.168.179.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 27.075/47.758/64.384/13.604 ms
USER@NAS-A:~$

Flipper92 · 22. Sep 2020

Ich hab nun versucht über ein anderes VPN Protokoll eine Verbindung herzustellen. Doch diese brechen immer mit dem Hinweis im Bild ab.
Dabei ist es sogar egal, ob der VPN Server auf der NAS-A läuft oder auf der Fritzbox (im Netzwerk A).

Ich bin ratlos. Gibt es noch ein paar Ansätze?

the other · 23. Sep 2020

Moinsen,
da ich hier bekannt bin für doofes Nachfragen, will ich meinem Ruf erneut gerecht werden:
1. im ersten Post hat NAS A die IP 192.168.178.60 und NAS B (remote) die 192.168.0.219...hast du das NAS im letzten Post von deinen Eltern abgeholt und bei dir ins Netzwerk gestellt oder woher die abweichende IP (192.178.169.6 im Codeblock, im Text 192.168.178.6)...könntest du nochmal sagen, welche IPs die NAS jetzt aktuell haben...?

2. dann den MTU PING Versuch bitte nochmal mit den (korrekten?) IPs zeigen. Ich habe MTU noch nie verändert, egal welcher Server (NAS, Firewall) als openVPN Server genutzt wurde, immer 1500er....

3. Hast du den VPN Versuch mit IPsec mal ganz ohne aktive Firewall auf den NASen versucht?

4. In der fritz ist der korrekte Port weitergeleitet?

5. Auch wenn es nervt: versuch nochmal mit den korrekten fixen IPs auf einem NAS den openVPN einzurichten und versuch dann auch den Client nochmal zu konfigurieren...wie ist dann eine eventuelle Fehlermeldung?

Syno-OS · 23. Sep 2020

Zuerst zum Aufbau

Zum Vergrößern anklicken....

:
Am Standort 1 (Hauptnetzwerk):
- DS1618+ mit OpenVPN Server (=NAS-A)
- 1000/50 Mbit/s Unitymedia Internet

Am Standort 2 (Eltern)
- DS216j (=NAS-B)
- 250/25 Mbit/s Unitymedia Internet

Tausche VPN Server - Client Rolle, dann klappt es meistens. Backup Ziel muss VPN Server sein.

Flipper92 · 23. Sep 2020

the other schrieb:
Moinsen,
da ich hier bekannt bin für doofes Nachfragen, will ich meinem Ruf erneut gerecht werden:

Doofe Fragen bringen doch immer die Lösung

Zu 1)
NAS-A:
192.168.178.60

NAS-B:
Lokal: 192.168.0.219 (Zugriff per Teamviewer auf Raspberry im Netz B)
VPN: 192.168.179.6 ~~192.178.169.6~~ (erreichbar damit per VPN und mit NAS-A)

Die " 192.168.178.6" gibt es nicht.

zu 2)

Code:

USER@192.168.178.60:~$ sudo ping -s 1500 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1500(1528) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 9000ms

USER@192.168.178.60:~$ sudo ping -s 1400 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1400(1428) bytes of data.
1408 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=30.8 ms
1408 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=25.3 ms
1408 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=25.0 ms
1408 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=27.1 ms
1408 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=25.8 ms
1408 bytes from 192.168.179.6: icmp_seq=6 ttl=64 time=30.9 ms
1408 bytes from 192.168.179.6: icmp_seq=7 ttl=64 time=26.4 ms
1408 bytes from 192.168.179.6: icmp_seq=8 ttl=64 time=27.4 ms
1408 bytes from 192.168.179.6: icmp_seq=9 ttl=64 time=24.0 ms
1408 bytes from 192.168.179.6: icmp_seq=10 ttl=64 time=25.2 ms

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 24.023/26.831/30.925/2.241 ms
USER@192.168.178.60:~$ sudo ping -s 1490 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1490(1518) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 9000ms

USER@192.168.178.60:~$ sudo ping -s 1480 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1480(1508) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 9002ms

USER@192.168.178.60:~$ sudo ping -s 1470 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1470(1498) bytes of data.
1478 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=29.7 ms
1478 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=24.0 ms
1478 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=30.2 ms
1478 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=26.5 ms
1478 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=27.5 ms
1478 bytes from 192.168.179.6: icmp_seq=6 ttl=64 time=24.1 ms
1478 bytes from 192.168.179.6: icmp_seq=7 ttl=64 time=25.5 ms
1478 bytes from 192.168.179.6: icmp_seq=8 ttl=64 time=39.2 ms
1478 bytes from 192.168.179.6: icmp_seq=9 ttl=64 time=32.2 ms
1478 bytes from 192.168.179.6: icmp_seq=10 ttl=64 time=37.7 ms

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 24.007/29.700/39.243/5.074 ms
USER@192.168.178.60:~$ sudo ping -s 1472 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1472(1500) bytes of data.
1480 bytes from 192.168.179.6: icmp_seq=1 ttl=64 time=26.4 ms
1480 bytes from 192.168.179.6: icmp_seq=2 ttl=64 time=26.6 ms
1480 bytes from 192.168.179.6: icmp_seq=3 ttl=64 time=29.0 ms
1480 bytes from 192.168.179.6: icmp_seq=4 ttl=64 time=25.3 ms
1480 bytes from 192.168.179.6: icmp_seq=5 ttl=64 time=25.0 ms
1480 bytes from 192.168.179.6: icmp_seq=6 ttl=64 time=26.4 ms
1480 bytes from 192.168.179.6: icmp_seq=7 ttl=64 time=30.9 ms
1480 bytes from 192.168.179.6: icmp_seq=8 ttl=64 time=35.1 ms
1480 bytes from 192.168.179.6: icmp_seq=9 ttl=64 time=36.9 ms
1480 bytes from 192.168.179.6: icmp_seq=10 ttl=64 time=27.2 ms

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 25.091/28.922/36.932/3.941 ms
USER@192.168.178.60:~$ sudo ping -s 1473 -c 10 -M do 192.168.179.6
PING 192.168.179.6 (192.168.179.6) 1473(1501) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 192.168.179.6 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 8999ms

Ich hab diesen Test gefunden: http://www.letmecheck.it/mtu-test.php
Das Ergebnis davon:
The maximum MTU size for [PUBLIC-IP Network-A] is: 1496
The maximum MTU size for [PUBLIC-IP Network-B] is: 1500

zu 3)
Ich hab gerade alle Firewalls (Fritzbox, NAS-A, NAS-B und Unitymediabox) ausgeschalten. Keine Änderung.

zu 4)
siehe zu 3. Alle Ports sind nun offen und dennoch keine Änderung.

zu 5)
mach ich jetzt mal. Ich starte auch mal die NAS A und B nach der Installaton. Das kann etwas dauern

Syno-OS schrieb:
Tausche VPN Server - Client Rolle, dann klappt es meistens. Backup Ziel muss VPN Server sein.

Nicht möglich, da die Unitymedia Box (Roter im Netzwerk B) keine Portweiterleitung erlaubt.

synfor · 23. Sep 2020

Zu 1) Ich würde für das VPN ja private Adressen verwenden. 192.178.169.6 ist keine.

Flipper92 · 23. Sep 2020

synfor schrieb:
Zu 1) Ich würde für das VPN ja private Adressen verwenden. 192.178.169.6 ist keine.

Danke, das war ein Fehler. Die VPN war nicht 192.178.169.6 sondern 192.168.179.6

Da ich nun bei "zu 5)" alles neu gemacht hab, hat diese sich nun auch nochmal geändert.
Was hab ich gerade gemacht:
- VPN-Server gelöscht
- VPN Verbindung gelöscht
- Hyperbackupauftrag gelöscht
- NAS-A und NAS-B neu gestartet
- VPN-Server auf NAS-A installiert
- VPN Verbindung auf NAS-B erstellt
- Hyperbackupauftrag neu verknüpft

Zu 1 und 5)
Die neue IP lautet nun 10.8.0.6

zu 2 nach neustart)
Während dem Backupversuch:

Code:

USER@192.168.178.60:~$ sudo ping -s 1400 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1400(1428) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

USER@192.168.178.60:~$ sudo ping -s 1400 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1400(1428) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

USER@192.168.178.60:~$ sudo ping -s 1000 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1000(1028) bytes of data.
1008 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=36.5 ms
1008 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=26.2 ms
1008 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=327 ms
1008 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=120 ms
1008 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=310 ms
1008 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=600 ms
1008 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=385 ms
1008 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=111 ms
1008 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=28.2 ms
1008 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=29.5 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 26.292/197.732/600.467/187.905 ms
USER@192.168.178.60:~$ sudo ping -s 1300 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1300(1328) bytes of data.
1308 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=39.8 ms
1308 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=27.1 ms
1308 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=28.8 ms
1308 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=28.5 ms
1308 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=26.8 ms
1308 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=26.3 ms
1308 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=25.2 ms
1308 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=27.2 ms
1308 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=31.3 ms
1308 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=26.8 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 25.256/28.815/39.836/4.000 ms
USER@192.168.178.60:~$ sudo ping -s 1350 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1350(1378) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

USER@192.168.178.60:~$ sudo ping -s 1340 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1340(1368) bytes of data.
1348 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=33.9 ms
1348 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=38.3 ms
1348 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=30.4 ms
1348 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=38.8 ms
1348 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=33.0 ms
1348 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=37.5 ms
1348 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=33.2 ms
1348 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=37.2 ms
1348 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=35.0 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9007ms
rtt min/avg/max/mdev = 30.447/35.298/38.805/2.695 ms
USER@192.168.178.60:~$ sudo ping -s 1345 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1345(1373) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9000ms

USER@192.168.178.60:~$ sudo ping -s 1344 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1344(1372) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

USER@192.168.178.60:~$ sudo ping -s 1343 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1343(1371) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

USER@192.168.178.60:~$ sudo ping -s 1342 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1342(1370) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9001ms

USER@192.168.178.60:~$ sudo ping -s 1341 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1341(1369) bytes of data.
1349 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=35.7 ms
1349 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=32.4 ms
1349 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=32.5 ms
1349 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=31.2 ms
1349 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=33.1 ms
1349 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=35.4 ms
1349 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=34.9 ms
1349 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=30.6 ms
1349 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=36.8 ms
1349 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=36.6 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 30.682/33.975/36.876/2.141 ms
USER@192.168.178.60:~$ sudo ping -s 1342 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1342(1370) bytes of data.
1350 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=38.3 ms
1350 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=35.0 ms
1350 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=34.2 ms
1350 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=35.4 ms
1350 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=34.6 ms
1350 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=34.2 ms
1350 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=38.7 ms
1350 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=33.4 ms
1350 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=32.1 ms
1350 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=32.0 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9001ms
rtt min/avg/max/mdev = 32.036/34.856/38.757/2.152 ms
USER@192.168.178.60:~$ sudo ping -s 1343 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1343(1371) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9001ms

USER@192.168.178.60:~$ sudo ping -s 1342 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1342(1370) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

USER@192.168.178.60:~$ sudo ping -s 1341 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1341(1369) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

USER@192.168.178.60:~$ sudo ping -s 1340 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1340(1368) bytes of data.
1348 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=35.7 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 1 received, 90% packet loss, time 8999ms
rtt min/avg/max/mdev = 35.700/35.700/35.700/0.000 ms
USER@192.168.178.60:~$ sudo ping -s 1340 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1340(1368) bytes of data.
1348 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=40.2 ms
1348 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=37.0 ms
1348 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=31.3 ms
1348 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=32.9 ms
1348 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=41.6 ms
1348 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=37.4 ms
1348 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=36.6 ms
1348 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=43.5 ms
1348 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=53.3 ms
1348 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=48.7 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8999ms
rtt min/avg/max/mdev = 31.381/40.294/53.348/6.489 ms
USER@192.168.178.60:~$ sudo ping -s 1342 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1342(1370) bytes of data.
1350 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=33.7 ms
1350 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=33.3 ms
1350 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=34.9 ms
1350 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=34.8 ms
1350 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=38.1 ms
1350 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=35.3 ms
1350 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=31.7 ms
1350 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=29.2 ms
1350 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=565 ms
1350 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=83.6 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9009ms
rtt min/avg/max/mdev = 29.246/91.998/565.115/158.416 ms
USER@192.168.178.60:~$ sudo ping -s 1345 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1345(1373) bytes of data.
1353 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=27.3 ms
1353 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=29.4 ms
1353 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=30.1 ms
1353 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=29.8 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 4 received, 60% packet loss, time 9002ms
rtt min/avg/max/mdev = 27.324/29.175/30.128/1.106 ms
USER@192.168.178.60:~$ sudo ping -s 1350 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1350(1378) bytes of data.

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

Nach dem Backupversuch:

Code:

USER@192.168.178.60:~$ sudo ping -s 1350 -c 10 -M do 10.8.0.6
Password:
PING 10.8.0.6 (10.8.0.6) 1350(1378) bytes of data.
1358 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=27.0 ms
1358 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=24.6 ms
1358 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=26.6 ms
1358 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=31.6 ms
1358 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=28.0 ms
1358 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=32.4 ms
1358 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=29.1 ms
1358 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=31.6 ms
1358 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=30.0 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9013ms
rtt min/avg/max/mdev = 24.681/29.032/32.484/2.505 ms
USER@192.168.178.60:~$ sudo ping -s 1360 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1360(1388) bytes of data.
1368 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=29.0 ms
1368 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=25.6 ms
1368 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=27.1 ms
1368 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=30.2 ms
1368 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=27.1 ms
1368 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=24.6 ms
1368 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=26.3 ms
1368 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=25.4 ms
1368 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=25.8 ms
1368 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=35.4 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 24.630/27.707/35.499/3.062 ms
USER@192.168.178.60:~$ sudo ping -s 1380 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1380(1408) bytes of data.
1388 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=29.1 ms
1388 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=24.4 ms
1388 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=26.7 ms
1388 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=25.6 ms
1388 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=27.2 ms
1388 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=29.1 ms
1388 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=26.7 ms
1388 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=27.4 ms
1388 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=23.9 ms
1388 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=28.0 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 23.934/26.865/29.197/1.694 ms
USER@192.168.178.60:~$ sudo ping -s 1400 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1400(1428) bytes of data.
1408 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=31.2 ms
1408 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=31.9 ms
1408 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=26.7 ms
1408 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=27.1 ms
1408 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=26.7 ms
1408 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=25.3 ms
1408 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=24.4 ms
1408 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=25.0 ms
1408 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=25.3 ms
1408 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=29.3 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 24.484/27.356/31.969/2.514 ms
USER@192.168.178.60:~$ sudo ping -s 1500 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1500(1528) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 9000ms

USER@192.168.178.60:~$ sudo ping -s 1420 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1420(1448) bytes of data.
1428 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=28.8 ms
1428 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=25.3 ms
1428 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=24.2 ms
1428 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=24.0 ms
1428 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=24.2 ms
1428 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=25.2 ms
1428 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=24.6 ms
1428 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=26.5 ms
1428 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=28.8 ms
1428 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=29.1 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 24.098/26.131/29.149/1.985 ms
USER@192.168.178.60:~$ sudo ping -s 1427 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1427(1455) bytes of data.
1435 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=30.7 ms
1435 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=27.6 ms
1435 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=29.5 ms
1435 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=29.9 ms
1435 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=24.3 ms
1435 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=25.6 ms
1435 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=28.5 ms
1435 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=31.0 ms
1435 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=29.7 ms
1435 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=26.3 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 24.363/28.366/31.079/2.157 ms
USER@192.168.178.60:~$ sudo ping -s 1432 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1432(1460) bytes of data.
1440 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=32.5 ms
1440 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=24.7 ms
1440 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=34.1 ms
1440 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=32.9 ms
1440 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=26.3 ms
1440 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=24.7 ms
1440 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=27.0 ms
1440 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=33.4 ms
1440 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=34.7 ms
1440 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=26.1 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9009ms
rtt min/avg/max/mdev = 24.703/29.677/34.700/3.977 ms
USER@192.168.178.60:~$ sudo ping -s 1442 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1442(1470) bytes of data.
1450 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=27.2 ms
1450 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=25.2 ms
1450 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=26.0 ms
1450 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=24.4 ms
1450 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=24.7 ms
1450 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=27.5 ms
1450 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=26.2 ms
1450 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=24.8 ms
1450 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=28.1 ms
1450 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=23.9 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 23.980/25.862/28.165/1.357 ms
USER@192.168.178.60:~$ sudo ping -s 1452 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1452(1480) bytes of data.
1460 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=27.1 ms
1460 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=26.8 ms
1460 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=24.4 ms
1460 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=26.0 ms
1460 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=29.3 ms
1460 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=26.7 ms
1460 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=25.2 ms
1460 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=28.7 ms
1460 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=24.7 ms
1460 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=29.6 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9007ms
rtt min/avg/max/mdev = 24.410/26.901/29.641/1.786 ms
USER@192.168.178.60:~$ sudo ping -s 1462 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1462(1490) bytes of data.
1470 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=37.8 ms
1470 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=29.9 ms
1470 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=24.4 ms
1470 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=24.8 ms
1470 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=24.2 ms
1470 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=25.4 ms
1470 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=24.4 ms
1470 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=24.0 ms
1470 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=25.0 ms
1470 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=24.7 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9009ms
rtt min/avg/max/mdev = 24.028/26.519/37.850/4.115 ms
USER@192.168.178.60:~$ sudo ping -s 1472 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1472(1500) bytes of data.
1480 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=26.3 ms
1480 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=24.0 ms
1480 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=25.8 ms
1480 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=26.6 ms
1480 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=28.7 ms
1480 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=26.4 ms
1480 bytes from 10.8.0.6: icmp_seq=7 ttl=64 time=24.9 ms
1480 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=25.7 ms
1480 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=27.8 ms
1480 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=30.4 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 24.016/26.698/30.402/1.787 ms
USER@192.168.178.60:~$ sudo ping -s 1473 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1473(1501) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 9000ms

USER@192.168.178.60:~$ sudo ping -s 1472 -c 10 -M do 10.8.0.6
PING 10.8.0.6 (10.8.0.6) 1472(1500) bytes of data.
1480 bytes from 10.8.0.6: icmp_seq=1 ttl=64 time=33.2 ms
1480 bytes from 10.8.0.6: icmp_seq=2 ttl=64 time=26.5 ms
1480 bytes from 10.8.0.6: icmp_seq=3 ttl=64 time=25.7 ms
1480 bytes from 10.8.0.6: icmp_seq=4 ttl=64 time=24.2 ms
1480 bytes from 10.8.0.6: icmp_seq=5 ttl=64 time=35.1 ms
1480 bytes from 10.8.0.6: icmp_seq=6 ttl=64 time=26.3 ms
1480 bytes from 10.8.0.6: icmp_seq=8 ttl=64 time=139 ms
1480 bytes from 10.8.0.6: icmp_seq=9 ttl=64 time=343 ms
1480 bytes from 10.8.0.6: icmp_seq=10 ttl=64 time=263 ms

--- 10.8.0.6 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9010ms
rtt min/avg/max/mdev = 24.238/102.003/343.690/114.623 ms

Was mir auffällt:
Unter last bricht der Ping ab ~1341 ab und wird nicht mehr weitergegeben..
Eventuell ist hier der Fehler zu suchen?

Was kann ich hierfür noch als Infos bieten?

the other · 24. Sep 2020

Moinsen,
sorry, ich passe, habe aktuell keine Idee dazu...mal sehen was die Profis hier dazu meinen.

blurrrr · 24. Sep 2020

@the other : Meinste bei so einem Blödsinn hat noch jemand groß Lust? ?

@Flipper92 : Tu uns (und auch Dir) doch einfach erstmal den Gefallen und setz die MTU "überall" wieder auf 1500. Die Fragmentierung/Reassemblierung überlässt Du dann mal schön den Routern (Waaaaas?! Zack, wieder was gelernt!) und im übrigen müssten dann auch alle anderen Geräte entsprechend im Heimnetz von der MTU her angepasst werden (die auf das NAS zugreifen) und sowas ist natürlich völliger Unsinn... Jut, also MTU wieder rauf auf "Standard" (soll heissen: 1500).

Da ich selbst die Syno nicht für VPN missbrauche, kann ich Dir leider nicht im Detail sagen wo wie was, aber halt allgemeines...Für den virtuellen VPN-Adapter auf der Syno kannst Du dann Deine gewünschte MTU "für den VPN-Tunnel" konfigurieren (das geschieht dann aber in der VPN-Config via "mssfix" (näheres dazu hier)) und nicht am Ethernet-Adapter(!).

Das würde ich jetzt soweit erstmal machen... Was jetzt noch mit "Last" und Co. ist, dass lassen wir erstmal aussen vor und biegen das erstmal hin.

Flipper92 · 24. Sep 2020

blurrrr schrieb:
Tu uns (und auch Dir) doch einfach erstmal den Gefallen und setz die MTU "überall" wieder auf 1500.

Das hab ich schon seit der ersten Nachricht von @Fusion gemacht. Also seit Sonntag 20.09. um 10:40.

Also werde ich nun Mal schauen, das ich irgendwie beim OpenVPN einstellen kann. (Hab ich das nun richtig verstanden?) Geht nicht direkt in der Synology VPN Station. Alle anderen VPN Protokolle nimmt die NAS-B nicht an (egal ob der Server NAS-A oder die Fritzbox an Ort-A ist).

blurrrr · 24. Sep 2020

Genau, schau vielleicht noch hier mal drüber https://blog.doenselmann.com/openvpn-durchsatz-optimieren/

Flipper92 · 25. Sep 2020

Danke, jetzt funktioniert es.
Die Übertragungsrate liegt zwar nur bei ~2MB/s, aber das ist okay für meinen Zweck.

Eventuell bastele ich noch an den Werten, aber fürs erste ist es lauffähig.
tun-mtu 1500 und 1400 sind fehlgeschlagen..

###########
Hier die Lösung für die "Nachwelt":

ich hab zuerst (gestern) die server.conf (auf NAS-A) geändert.
sudo vi /volume1/@appstore/VPNCenter/etc/openvpn/server.conf

Code:

sndbuf 393216
rcvbuf 393216
tun-mtu 1300
mssfix 1200

Ich hatte da auch die push Zeilen eingearbeitet. Das hat aber nichts gebracht und es gab die bekannte Fehlermeldung.
Heute hab ich nun die Push Zeilen in die client.config (auf NAS-B) direkt eingearbeitet:

Code:

sndbuf 393216
rcvbuf 393216
tun-mtu 1300

Die Zeile fragmentation 1300 hat zu einem "Falschen Parameter" Fehler geführt.

User388 · Dienstag um 21:32

Bei mir hat folgender Fix funktioniert:

1, Öffnen von cmd.exe und Eingabe des folgenden Befehls ping -f -l 1000 10.1.1.10
-> 10.1.1.10 ersetzen durch eure Ziel IP
-> erhöhen des 1000 Wertes um 28 und erneute Eingabe (Iteration)

Sobald die Verbindung instabil wird, habt ihr den maximalen MTU-Wert ermittelt. Bei mir war es 1200. Im Anschluss habe ich den MTU-Wert auf dem Ziel-NAS, auf dem Source-NAS und auf dem VPN-Server auf 1200 gestellt und es hat geklappt.

Suche

Hyper Backup Backup über VPN (fehlerhafter MTU?)

Flipper92

Benutzer

Anzeige

Fusion

Benutzer

Flipper92

Benutzer

Flipper92

Benutzer

Anhänge

the other

Benutzer

Syno-OS

Benutzer

Flipper92

Benutzer

synfor

Benutzer

Flipper92

Benutzer

the other

Benutzer

blurrrr

Benutzer

Flipper92

Benutzer

blurrrr

Benutzer

Flipper92

Benutzer

User388

Benutzer

Kaffeautomat