Setting the MTU on our interface changes the MTU on OUR side. You still need to manually adjust the MTU on YOUR side.
Quote from: broquea on July 26, 2017, 12:39:33 PM
Setting the MTU on our interface changes the MTU on OUR side. You still need to manually adjust the MTU on YOUR side.
Thanks! MTU has changed!
But the problem remained.
I will not create a new branch, but I'll ask the question here the traffic goes to - Server IPv6 Address: 2001: 470: 27: 805 :: 1/64
he-XXXXXX Link encap:IPv6-in-IPv4
inet6 addr: 2001:470:27:805::2/64 Scope:Общий
inet6 addr: fe80::XXXX:XXXX/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1460 Metric:1
RX packets:73 errors:0 dropped:0 overruns:0 frame:0
TX packets:194 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:5736 (5.7 KB) TX bytes:58627 (58.6 KB)
$ traceroute6 he.net
traceroute to he.net (2001:470:0:76::2) from 2001:470:27:805::2, 30 hops max, 24 byte packets
1 cashipvsix-2.tunnel.tserv24.sto1.ipv6.he.net (2001:470:27:805::1) 62.205 ms
* *
$ wget -6 -O / dev / null http://he.net
-2017-07-27 01: 37: 49-- http://he.net/
Recognized as he.net (he.net) ... 2001: 470: 0: 76 :: 2
Connection to he.net (he.net) | 2001: 470: 0: 76 :: 2 |: 80 ... the connection is established.
HTTP request sent. Waiting for an answer ... ^ C
I do not even know what to do ...
Could you suggest more options where there can be a mistake?