Problem solved.
As expected, it was evidently a network problem on the Contabo side.

Recently I'm experiencing IPv6 connectivity issues through tunnelbroker to various sites, preventing webpages from loading:

Specific example:

Through tunnelbroker: ping6 substackcdn.com
PING6(56=40+8+8 bytes) 2001:470:.... --> 2600:9000:24eb:ee00:4:b4b9:d3c0:93a1
^C
--- substackcdn.com ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

From a cloud server with direct IPv6 service:

ping6 substackcdn.com
PING substackcdn.com(2600:9000:...) 56 data bytes
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=0 ttl=56 time=1.17 ms
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=1 ttl=56 time=1.21 ms
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=2 ttl=56 time=1.18 ms
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=3 ttl=56 time=1.25 ms
^C
--- substackcdn.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.173/1.207/1.252/0.052 ms, pipe 2

See if this works:

ifconfig sit1 inet6 add 2001:470:1f1a:21e::2/64 tunnel ::216.66.87.14 up
route -6 add default dev sit1

If you have “ip” available, using it to bring up the tunnel is cleaner.

Sit0 does not need to be brought up.

Could someone give me a hand Linux-net tools configuration auto generated doesn't work !

Code: [Select]

ifconfig sit0 up
ifconfig sit0 inet6 tunnel ::216.66.87.14
ifconfig sit1 up
ifconfig sit1 inet6 add 2001:470:1f1a:21e::2/64
route -A inet6 add ::/0 dev sit1

Hi,
same problem here (I have a VPS in Düsseldorf Contabo datacenter).
The cause seems to belong to Contabo.
I contacted Contabo support but so far I have not received any confirmation regarding the cause (nor regarding the existence of the problem...).
In any case (and I think it's not accidental) two days ago Conbabo communicated (see "Scheduled Maintenances" here:https://contabo-status.com/) that it had scheduled (for next Monday) a network maintenance intervention.

Hello,
First sorry for my bad english.

With your Setup was my ipv6 tunnel not work.

I take anythink and only 30 seconds was the gateway up and after this 30 seconds down.

I have a Sophos XG with v19

Can you add a step by step tutorial to add a ipv6 Tunnel in Sophos XG v19

Example: at 6to4 i can only add the local ipv4 address not remote
And then come a popup where i can only add the destination IP/Prefix.
If you can post an example ipv6 infos from HE.NET and the Sophos XG v19 pictures step by step??
Please add the Rules(ipv4, ipv6 and nat) pictures too.
Thank you

Hi,

i have mailed dnsadmin about this issue and they replied to me:

Code: [Select]

Hello,

The recent DNS resolution issues should be resolved at this point.

Please test again and let us know if you still see any issues.

Regards,

Roman
HE Support
AS6939

---- Original message ----

 Dear DNS-Admins,
 
 i would like to inform you about a recent issue:
 
 host -vt ns synology.thefirewall.de ns5.he.net
 Trying "synology.thefirewall.de"
 Using domain server:
 Name: ns5.he.net
 Address: 216.66.80.18#53
 Aliases:
 
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18019
 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
 
 ;; QUESTION SECTION:
 ;synology.thefirewall.de. IN NS
 
 ;; AUTHORITY SECTION:
 thefirewall.de. 172800 IN SOA ns1.he.net. hostmaster.he.net. 2022111700
 86400 7200 3600000 172800
 
 Received 98 bytes from 216.66.80.18#53 in 1340 ms
 
 
 You DNS replies are really slow, sometimes they even timeout... Also
 this issue hits he.net own domains as well and not just the user ones.
 
 For  Example:
 
 host -vt ns bgp.he.net ns5.he.net
 Trying "bgp.he.net"
 Using domain server:
 Name: ns5.he.net
 Address: 216.66.80.18#53
 Aliases:
 
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59397
 ;; flags: qr aa rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
 
 ;; QUESTION SECTION:
 ;bgp.he.net. IN NS
 
 ;; ANSWER SECTION:
 bgp.he.net. 86400 IN NS ns2.he.net.
 bgp.he.net. 86400 IN NS ns1.he.net.
 bgp.he.net. 86400 IN NS ns5.he.net.
 bgp.he.net. 86400 IN NS ns3.he.net.
 bgp.he.net. 86400 IN NS ns4.he.net.
 
 Received 118 bytes from 216.66.80.18#53 in 1428 ms



Seeing significant problems now reaching tserv1.lon2.he.net from a Sky/NOW! connection on v4:

Code: [Select]

4. 10gigabitethernet5-1.core1.lon1.he.net                                                            69.6%    24    6.0   6.1   5.9   7.3   0.5
 5. 40ge1-3.core1.lon2.he.net                                                                        82.6%    24    6.9  23.0   6.9  31.8  11.6
 6. port-channel8.core2.lon2.he.net                                                                   0.0%    24    7.8   7.6   7.3   8.9   0.3
 7. tserv1.lon2.he.net                                                                                0.0%    24  245.0 273.7 186.3 410.9  55.1
Can anyone at he.net comment - is there anyway to raise this with anyone?

S.

Hello all,

I have setup an IPv6 Tunnel with HE. When I created the tunnel I picked Tokyo as the location as that is the closest to me, however it seems that all my traffic is being routed to the USA which well, has slowed down downloads being made through ipv6.

Is this normal? I thought if I picked Japan as the server the traffic would there but not?

If I run a trace route this is what it shows:

Code: [Select]

# /usr/sbin/traceroute6 -w 2 -I  -n  -m '18'  '2001:dc2::1'
traceroute6 to 2001:dc2::1 (2001:dc2::1) from 2001:470:23:2fc::2, 18 hops max, 20 byte packets
 1  MyIPv6 Tunnel Prefix  29.147 ms  31.087 ms  31.091 ms
 2  * * *
 3  2001:de8:8::2516:1  132.449 ms  137.078 ms  135.844 ms
 4  * * *
 5  2001:268:fa00:267::2  130.746 ms  131.285 ms  133.248 ms
 6  2001:268:f702:4::2  29.710 ms  28.161 ms  28.234 ms
 7  2001:260:30b:1::1:25  30.038 ms * *
 8  * * *
 9  2001:dc2:0:2::1  31.065 ms  39.765 ms  30.094 ms
10  2001:dc2::1  28.255 ms  29.471 ms  28.584 ms

Hi.
As of yesterday, one of our servers using IPv6 via HE cannot reach a VPS we have at Contabo. Traceroute stops somewhere around twelve99.net, two hops after as1299.gige-g2-9.core1.fra1.he.net.
We have no issues from other IPv6 nodes, while a second TB connection (my home) cannot reach the host as well!

Is there something on HE side?

Thanks