search

zerotier / ZeroTierOne

A Smart Ethernet Switch for Earth
https://zerotier.com
Other
14.62k stars 1.71k forks source link

Unable to ping clients with packet data of 1355 bytes and higher (MTU issue?) #2228

Closed KweezyCode closed 8 months ago

KweezyCode commented 9 months ago

I am also unable to ssh over zerotier. My hosting provider is Aeza (aeza.net)

kweezy@spiky-stove:~$ ifconfig
ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1448
        inet 5.42.95.95  netmask 255.255.255.255  broadcast 5.42.95.95
        inet6 fe80::5054:ff:fe17:fcda  prefixlen 64  scopeid 0x20<link>
        inet6 2a12:5940:bae1::2  prefixlen 48  scopeid 0x0<global>
        ether 52:54:00:17:fc:da  txqueuelen 1000  (Ethernet)
        RX packets 4503  bytes 721136 (721.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5727  bytes 784315 (784.3 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 180  bytes 14240 (14.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 180  bytes 14240 (14.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

zt7nnbwwj7: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2800
        inet 10.8.0.1  netmask 255.255.255.0  broadcast 10.8.0.255
        inet6 fe80::a448:2dff:fe0a:b5da  prefixlen 64  scopeid 0x20<link>
        ether a6:48:2d:0a:b5:da  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 13  bytes 1006 (1.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ztwdjpiagx: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2800
        inet 10.0.0.3  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 fe80::740f:a7ff:fe99:3930  prefixlen 64  scopeid 0x20<link>
        ether e2:ba:ab:a6:1e:b3  txqueuelen 1000  (Ethernet)
        RX packets 108  bytes 99279 (99.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 143  bytes 100617 (100.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
ping -s 1355 10.0.0.3
PING 10.0.0.3 (10.0.0.3) 1355(1383) bytes of data.
^C
--- 10.0.0.3 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1017ms
ping -s 1354 10.0.0.3
PING 10.0.0.3 (10.0.0.3) 1354(1382) bytes of data.
1362 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=39.7 ms
1362 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=34.4 ms
1362 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=32.3 ms
^C
--- 10.0.0.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 32.289/35.471/39.739/3.136 ms
jmp242 commented 9 months ago

We have also seen this issue for kerberos / ssh and the like from a wifi network that does a second layer of encapsulation as documented here: https://discuss.zerotier.com/c/community-support/8

laduke commented 9 months ago

which thread?

Do you have direct connections to the thing you're pinging? zerotier-cli peers

jmp242 commented 9 months ago

Sorry, I copied the wrong URL, here's the specific one. https://discuss.zerotier.com/t/roaming-wifi-with-spectrum-fails-to-work-because-of-mtu-issues/18741 For us, we are pinging things that are routed on a remote zerotier device via a reverse NAT (to that network).

KweezyCode commented 8 months ago

looks like provider issue, sorry, closing