• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Recent posts

#71
Questions & Answers / Re: IPv6 tunnel on Paris serve...
Last post by rgarcia - October 21, 2023, 03:12:08 PM
New test that confirms that outbound IPv6 trafic is correctly sent to target but answer does never come back : inbound paquets are lost somewhere as it seems there is a routing issue to go back to the 6to4 tunnel.
Is there anyone from HE reading this forum ?
#72
Questions & Answers / IPv6 tunnel on Paris server st...
Last post by rgarcia - October 20, 2023, 04:07:20 PM
Hi,

I am using a 6to4 tunnel since 2015 attached to Paris server. Last week it stopped working, I don't receive anymore any paquet from the tserv1.par2.he.net (216.66.84.42) server. My configuration has not changed. Is there any known issue with this endpoint?

traceroute trying to reach the server ipv6 address from the client (failure)

traceroute to 2001:470:1f12:4c2::1 (2001:470:1f12:4c2::1), 30 hops max, 80 byte packets
 1  * * *
 2  * * *
 3  * * *^C

traceroute trying to reach the server ipv6 address from the outside (success)
traceroute to 2001:470:1f12:4c2::1 (2001:470:1f12:4c2::1), 30 hops max, 80 byte packets
 1  2001:bc8:47b0:2203::  0.960 ms  0.852 ms  0.812 ms
 2  2001:bc8:407:304::1  1.371 ms  1.396 ms  1.363 ms
 3  2001:bc8:400:1::75  1.555 ms 2001:bc8:400:1::7d  1.465 ms 2001:bc8:400:1::75  1.567 ms
 4  2001:bc8:400:1::1b4  1.147 ms 2001:bc8:400:1::1b2  1.060 ms 2001:bc8:400:1::1a6  1.159 ms
 5  2001:bc8:400:100::c7  1.059 ms * *
 6  * * *
 7  2001:470:1f12:4c2::1  0.653 ms  0.833 ms  0.744 ms

Traceroute trying to reach the client ipv6 address from the outside (failure)
traceroute to 2001:470:1f12:4c2::2 (2001:470:1f12:4c2::2), 30 hops max, 80 byte packets
 1  2001:bc8:47b0:2203::  1.397 ms  1.312 ms  1.284 ms
 2  2001:bc8:407:304::1  1.354 ms  1.357 ms  1.313 ms
 3  2001:bc8:400:1::75  1.729 ms 2001:bc8:400:1::7d  1.673 ms 2001:bc8:400:1::75  1.730 ms
 4  2001:bc8:400:1::7c  1.916 ms 2001:bc8:400:1::1b6  1.906 ms 2001:bc8:400:1::1b8  1.407 ms
 5  2001:bc8:400:100::c7  1.419 ms 2001:bc8:400:100::c1  1.474 ms 2001:bc8:400:100::c7  1.751 ms
 6  * * *
 7  2001:470:0:7b::2  5.810 ms  5.434 ms  5.400 ms
 8  * * *
 9  * * *
10  * * *^C

Regards,
René

#73
Questions & Answers / Re: Are there other BGP tunnel...
Last post by kamil445 - October 16, 2023, 08:41:42 AM
Quote from: cjy666 on September 30, 2023, 02:47:33 AMHello,Are there other free BGP tunnel providers after he.net  do not provide free BGP tunnel?

here you can find list of active Tunnelbrokers

https://tunnelbroker.services/
#74
Questions & Answers / Re: Google forcing ReCAPTCHA o...
Last post by supergvozd - October 09, 2023, 10:41:48 PM
I changed routed prefix to /48. Still works
#75
General Questions & Suggestions / Re: DNS: vague error message "...
Last post by kcochran - October 07, 2023, 07:31:59 PM
This would be the DNS server you're querying, and if you didn't enter one in the tool, it would be the default DNS server for your phone, which should then be displayed as placeholder text in the DNS server field.

If you're trying to query an authoritative DNS server for a domain it does not handle, this is the response you will receive.  A few other rare cases it's a non-recoverable error on the remote server, or it has no answer to give you, and doesn't want to return NXDOMAIN instead for some reason.
#76
General Questions & Suggestions / DNS: vague error message "Serv...
Last post by minfrin - October 07, 2023, 05:04:08 AM
While the he.net app is normally very good, I've found a bug in the DNS troubleshooting section.

When encountering an error, it reports "Server rejected query", without telling us which server rejected the query, or what the nature was of the rejection.

Without knowing the server's IP address, this is impossible to troubleshoot.
#77
Questions & Answers / Are there other BGP tunnel pro...
Last post by cjy666 - September 30, 2023, 02:47:33 AM
Hello,Are there other free BGP tunnel providers after he.net  do not provide free BGP tunnel?
#78
Questions & Answers / Timeout and poor ping time to ...
Last post by jlde - September 11, 2023, 08:31:14 AM
Hello,
I use the tunnel broker service for a 6in4 tunnel. It's a great service which works very well. But now I get al lot of timeouts during my work over IPv6. The IPv4 connection to the tunnel server shows altough timeouts and poor ping times to the location in Frankfurt. Are there any known issues regarding the location? Any others having trouble with the Frankfurt node?

Here is a ping output:

Ping statistics for 216.66.80.30:
    Packets: Sent = 100, Received = 89, Lost = 11 (11% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 226ms, Average = 27ms

And here a traceroute output:
Tracing route to tserv1.fra1.he.net [216.66.80.30]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.101.1
  2     2 ms     2 ms     2 ms  192.168.2.1
  3     *        *        *     Request timed out.
  4     7 ms     6 ms     6 ms  88.79.8.22
  5     7 ms     7 ms     7 ms  188.111.161.8
  6     *        *        *     Request timed out.
  7     8 ms     8 ms    38 ms  port-channel16.core2.fra1.he.net [184.104.231.45]
  8    80 ms     *        8 ms  port-channel16.core2.fra1.he.net [184.104.231.45]
  9     7 ms     7 ms     7 ms  tserv1.fra1.he.net [216.66.80.30]


Best regards Jörg
#79
Questions & Answers / Re: Packet loss e0-30.core2.lo...
Last post by lewislfoster - September 08, 2023, 01:35:36 PM
For the past few months ive been seeing consistent 5-10% packet loss to e0-19.core2.lon2.he.net both through tunnel broker and native IPv6 from linode. Before i tried to ping from linode i thought it might have been something to do with virgin media but it appears to not be
#80
Questions & Answers / Re: Google forcing ReCAPTCHA o...
Last post by Jenick - September 08, 2023, 12:10:58 PM
If it helps, HE.net support told me to change my LAN side networks to my /48 routed, not the /64 default they hand you when you first created your tunnel.  However, if you're running pfSense and pfBlockerNG you can give this a try... https://github.com/pahtzo/hurricane-tunnel-dohdot The main issue I believe is chromium based browsers have their own built-in DNS client which automatically goes for DOH-DOT by default and maybe not even against your system based DNS servers.  I've disabled my pfBlockerNG no-AAAA for google.com and www.google.com but retained my Windows 10 registry settings to disable the built-in DOH-DOT in Brave, Chrome, and Edge.  Still working just fine.