Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  


Welcome to Hurricane Electric's forums!

Pages: [1] 2 3 ... 10
 on: July 09, 2020, 04:04:28 AM 
Started by anirbansengupta - Last post by anirbansengupta
I have setup the txt file to my website but it says "Failed to connect to port 80: Connection timed out" repeatedly while trying out the test. Any help will be highly appreciated.

 on: July 06, 2020, 04:47:13 AM 
Started by iosoft - Last post by cholzhauer
There is already a thread that handles this

 on: July 04, 2020, 08:30:10 PM 
Started by iosoft - Last post by iosoft
D-Link DIR-615 Wireless N 300 Router
(saw this in a YouTube video -

 on: July 04, 2020, 08:25:05 PM 
Started by iosoft - Last post by iosoft
Dear Friends,

Can you pls list some Home routers that have build-in support for IPv6 Tunnel Broker service settings?
(without Open-WRT or DD-WRT because not all routers are supported and it breaks warranty)

Actually, if we go to shop and ask if 'this' router supports Tunnel Broker service, they can not answer.
It will be a great help for buyers like us.

 on: June 30, 2020, 04:53:52 PM 
Started by Rewillis - Last post by Rewillis
tjeske, the terminology in my Netgear D6400 router "6to4 Tunnel" settings is "6to4."  Also, I do not know what you mean by my router terminating the tunnel - please be more specific.  Finally, you will need to inform me regarding protocol 41 ( I know that it is not referring to port 41, though ).  Thank you.  :)

 on: June 30, 2020, 03:51:42 PM 
Started by Rewillis - Last post by tjeske
What do you mean "6to4"? HE uses "6in4", not "6to4".

And what do you mean you have configured it in Netgear D6400 router? Is this router capable of terminating the tunnel? If yes, then you don't need to paste anything in the Windows command prompt window. If no, then you need to forward protocol 41 (_not_ port 41!) to your PC where you enter the commands.

 on: June 30, 2020, 03:26:07 PM 
Started by altadenamd - Last post by altadenamd
My connections through tserv13.ash1 go silent for minutes at a time, long enough to stop ssh with 400s timeouts.  During this nothing on v6 (outside my local network) pings (even, the tunnel's v4 address does ping pretty much at all times through these outages.  This appears to happen fairly regularly, different times around hourly or a bit more often.  Possibly could be my router, though I have another tacked-up vpn (vti, though) that keeps up through these and doesn't seem to go bad.  I could switch to New York (adds 15ms or so) but don't want to change addresses if possible.
Is the server maybe running out of RAM or maybe a bad interface on a LAG?  I presume this doesn't hit everyone or I would have seen notes here already.

Actually wish VZ would get with the program and offer native V6 for business fios...  (some residential accounts have it already).  About once a month for several years now I listen for RADV packets and never see any :-(, and once in a while try configure dhcp-pd to no avail either. And of course when I call tech support they say "what's that" about ipv6.

-- Pete

 on: June 26, 2020, 05:54:55 AM 
Started by Rewillis - Last post by Rewillis
Update: I am able to ping my 6to4 tunnel IP address ( i.e., "2001:470:4:6a3::2" ) from the Microsoft Windows 10 ( Home ) Edition command prompt, as shown in the attachment, below.  Any suggestions?  :)

 on: June 25, 2020, 05:21:15 PM 
Started by Rewillis - Last post by Rewillis
Running Microsoft Windows 10 ( Home ) Edition, Build 1903.  I followed the steps to cut and paste 6to4 tunnel commands in the command window, initially using the IPv4 address provided to the broker.  The response was okay.  6to4 tunnel is configured in Netgear D6400 router.  When I ping my tunnel IPv6 address ( i.e., "2001:470:4:6a3::2" ), using the "Looking Glass" link, the command times out.  Why is this happening?  :)

 on: June 25, 2020, 10:57:52 AM 
Started by woosingwoo - Last post by lynxmax
Thank you again. I'll check it out.

Pages: [1] 2 3 ... 10