Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 ... 7 8 [9] 10
 81 
 on: January 10, 2019, 01:24:22 PM 
Started by ljonget - Last post by ljonget
Yes, I said "it might" as when a ping with default packet size (=56) and it works, it still works if increase the packet size to 100, then 500 then 1000 it works, and a few seconds after it doesn't anymore, even with default value.

if I let run the ping command, I have a huge loss of packet :
Code: [Select]
PING 2001:200:dff:fff1:216:3eff:feb1:44d7(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes
64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=12 ttl=50 time=319 ms
64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=13 ttl=50 time=320 ms
64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=14 ttl=50 time=321 ms
64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=15 ttl=50 time=318 ms
^C
--- 2001:200:dff:fff1:216:3eff:feb1:44d7 ping statistics ---
73 packets transmitted, 4 received, 94% packet loss, time 72006ms
rtt min/avg/max/mdev = 318.390/320.028/321.046/1.240 ms

I tried to set MTU to 1480 (default value in tunnel broker account) and to minimum (1280).

 82 
 on: January 07, 2019, 10:21:53 AM 
Started by Napsterbater - Last post by Daniel15
Just noticed the same thing when I tried to configure an IPv6 tunnel for a site that uses Cloudflare (unfortunately, I have some servers in data centers that still don't offer native IPv6!). It would be good to document this more clearly on the tunnelbroker site.

 83 
 on: January 07, 2019, 04:36:03 AM 
Started by ljonget - Last post by cholzhauer
You said it seems to depend on packet size...can you just set the MTU to a value that works and leave it?

 84 
 on: January 06, 2019, 02:01:17 PM 
Started by ljonget - Last post by ljonget
Hi all,

I'm using HE tunnelbroker since 2016 without issue, and since 1 month or so, it stopped working.
Since then, the linux box (a Synology NAS) has been updated, the ISP router might have been updated as well (don't know and can't know...) so it's difficult to know why.

here is more info :
- the setup is : a synology NAS with a private IPV4 address and the ISP router with a static public IPV4 address
- all commands (scripted, so they didn't changed) to bring the interface up with ips,... are successful
- ping to server IPV4 address is OK
- ping to client IPV6 address is OK
- ping to server IPV4 address is OK
- when running a IPv6 Portscan from tunnelbroker.net website, the results are OK and ports that should be opened are opened
- ping to a IPV6 website (like www.kame.net, ...) is sometime ok sometime not ok and might depend on packets size
- curl to a IPV6 fails anytime.

what I've tried :
- setup the IPV6 on another Linux box (a VM on my laptop) : same behavior
- delete tunnel and create a new one : same
- tcpdump the IPV6 traffic while pinging and curling : seeing a lot of output packet but only a few for echo request, and none for http(s) calls and so a lot of retransmission

it seems tunnel is OK, and that router is forwarding IP protocol 41 as the portscan is ok, but can't understand why outgoing traffic (except ping) is failing...

Any ideas ?
what else can I do to narrow down culprit ?

thanks a lot

 85 
 on: January 06, 2019, 12:23:14 PM 
Started by hechz - Last post by hechz
Ah sorry for the confusion, I merely mentioned IPSEC on the IPv4 addresses as an indication that other services are working with both external addresses, just not 6to4 tunneling

 86 
 on: January 03, 2019, 03:08:35 PM 
Started by hechz - Last post by snarked
I assume that your multi-wan device has different IPv4 addresses on the wan interfaces.  However, your use of IPSEC may interfere.  That's not what the HE tunnels use, and if your IPSEC configuration requires authentication or encapsulation, that could reject the tunnelled packets using protocol 4 (IPv4 in IPv4).

 87 
 on: January 03, 2019, 12:36:44 PM 
Started by hechz - Last post by hechz
I have a question regarding having multiple tunnels with different source IPs on the same device. My router supports, and I am using multi-wan for my IPv4 connections, IPSEC-GRE, etc but I cannot get two HE tunnels to work at the same time on the device. Is this supported, known to work, or am I barking up the wrong tree?

 88 
 on: January 03, 2019, 09:01:23 AM 
Started by fastbyte - Last post by integrabh
I have changed the home router couple of days ago and I have a domain on he.net so I'm trying to get dynamic DNS to work.

But after over 10-20 retry's i have seen that tunnelbroker gives a abuse status (abuse @ 2016-08-03 02:05:12).

How can I fix this?



DynDNS_FritzBox_To Tunnel Broker:

Update-URL: https://ipv4.tunnelbroker.net/nic/update?hostname=451585  ,......,Tunnel ID
Domain: he.net
Username: ibh     ,......,Username Tunnelbroker Login
Password: RWoghAb7kIaY3n3D  ,......,Key Dynamic DNS Record

 89 
 on: December 21, 2018, 05:29:23 AM 
Started by Walter H. - Last post by d3x0r
No ping response, it respolves to an IPv6 though.

But then today I find I can't connect through my tunnel to anywhere that is IPV6.

ping -6 www.he.net (timeout)
ping -6 www.google.com (timeout)
ping -6 [my upstream ipv6] 12-13ms.

don't know any further points to connect to.

I'm connecting via 66.220.18.42

edit:
my address is 'd3x0r.org' which resolves to 2001:470:d:579::4  I can ping it from my windows box (intenral network) but cannot from the world side... (found an online ping utility, that can ping www.google.com (fails for me) and can't ping d3x0r.org (which works for me).   it has been working until today.

 90 
 on: December 20, 2018, 04:16:50 PM 
Started by mcavic - Last post by snarked
I think you really need to take a look at the structure of the "ip6.arpa" zone.

Pages: 1 ... 7 8 [9] 10