Hi guys,
I have three internet connection with two different providers.
Larger ping requests get not fragmented with one of the providers (UPC, two internernet connections are from this one), so the limit there is 1472 byte for some reason.
Larger ping do not get through, even if I lower down the MTU on my router.
Internet Connection 1 (IC1):
Same thing with this connection, which is a symetric UPC / Inode DSL line:
eth1.301 Link encap:Ethernet HWaddr 58:EF:68:B7:6D:A4
inet addr:83.65.96.212 Bcast:83.65.96.223 Mask:255.255.255.240
inet6 addr: fe80::5aef:68ff:feb7:6da4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:117466237 errors:0 dropped:0 overruns:0 frame:0
TX packets:89747404 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44893152409 (41.8 GiB) TX bytes:49781448291 (46.3 GiB)
Internet Connection 2 (IC2):
On my third connection, which is a A1 LTE modem line, larger pings are working.
eth2 Link encap:Ethernet HWaddr 00:A0:C6:00:00:00
inet addr:90.152.149.110 Bcast:255.255.255.255 Mask:255.255.255.255
inet6 addr: fe80::2a0:c6ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:203376486 errors:0 dropped:0 overruns:0 frame:0
TX packets:132904330 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1604613911 (1.4 GiB) TX bytes:3256878506 (3.0 GiB)
ping 88.198.132.225 -l 2500
Ping wird ausgeführt für 88.198.132.225 mit 2500 Bytes Daten:
Antwort von 88.198.132.225: Bytes=2500 Zeit=80ms TTL=53
Antwort von 88.198.132.225: Bytes=2500 Zeit=57ms TTL=53
Antwort von 88.198.132.225: Bytes=2500 Zeit=48ms TTL=53
Antwort von 88.198.132.225: Bytes=2500 Zeit=59ms TTL=53
Ping-Statistik für 88.198.132.225:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 48ms, Maximum = 80ms, Mittelwert = 61ms
ping 88.198.132.225 -l 1472 -f
Ping wird ausgeführt für 88.198.132.225 mit 1472 Bytes Daten:
Antwort von 88.198.132.225: Bytes=1472 Zeit=56ms TTL=53
Antwort von 88.198.132.225: Bytes=1472 Zeit=92ms TTL=53
Antwort von 88.198.132.225: Bytes=1472 Zeit=79ms TTL=53
Antwort von 88.198.132.225: Bytes=1472 Zeit=82ms TTL=53
Ping-Statistik für 88.198.132.225:
Pakete: Sent = 4, Received = 4, Lost = 0
(0% Loss),
Ca. Zeitangaben in Millisek.:
Minimum = 56ms, Maximum = 92ms, Mittelwert = 77ms
ping 88.198.132.225 -l 1473 -f
Ping wird ausgeführt für 88.198.132.225 mit 1473 Bytes Daten:
Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Ping-Statistik für 88.198.132.225:
Pakete: Sent = 4, Received = 0, Lost = 4
(100% Loss),
(Sorry for the German there in the command, I have only a German Windows PC on this location and I have not seen a DF option with the OpenWRT ping command)
Internet Connection 3 (IC3):
This is a UPC / Chello Internet connection via a cable TV line.
eth1.2 Link encap:Ethernet HWaddr 58:EF:68:B7:62:F4
inet addr:84.115.50.36 Bcast:84.115.50.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
RX packets:5241 errors:0 dropped:0 overruns:0 frame:0
TX packets:3697 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1087994 (1.0 MiB) TX bytes:699318 (682.9 KiB)
root@uFW1:~# ping 88.198.132.225 -s 1473
PING 88.198.132.225: 1473 data bytes
^C
--- 88.198.132.225 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss
root@uFW1:~# ping 88.198.132.225 -s 1472
PING www.nahtec.at (88.198.132.225): 1472 data bytes
1480 bytes from 88.198.132.225: seq=0 ttl=54 time=33.075 ms
1480 bytes from 88.198.132.225: seq=1 ttl=54 time=32.231 ms
So 1072 bytes are the limit, even when the DF bit is not set.
Since I already lowered down the packages with the low MTU size on my side, I guess the problem is the return package.
Has this provider a problem with black wholes?
If yes, how can I get around this?