I'm looking for a good and stable IPv6 tunnel broker, to be used from Germany. For example Sixxs and Hurricane seem to be popular choices. What qualities should one look for when selecting a tunnel broker, and are there big differences between the service quality between different providers?

If I got your question right, then what you need is called a 4in6 tunnel broker. This is a service that tunnels IPv4 traffic over an IPv6 network. The way it works is this: A router on your side accepts IPv4 packets that are to be routed outside and encapsulates them inside an IPv6 packet, which is then sent to the tunnel broker service.

2023年2月20日 · When creating an IPv6 tunnel with tunnelbroker.net, the Tunnel Broker service assigns you a client IPv6 address to be used on the router and a routed IPv6 network to be used by the systems in the network. However, I don't have a network: I have a single system with IPv4 connectivity, to whom I'd like to also give IPv6 connectivity.

In my experience of comparing traceroute6 vs. traceroute, IPv6 is faster, even through a tunnel broker. This is probably because IPv6 generally requires fewer hops to get from point A to B. Here's a third-party source backing up my observation:

When created a tunnel from TunnelBroker.net on Windows 7 there were only 3 important pieces of information: Tunnel Entry-Point Node: 192.168.1.98; Tunnel Exit-Point Node: 209.51.181.2; Client IPv6 Address: 2001:470:1f11:1178::2/64; and then then tunnel needs a default gateway IPv6 address: Server IPv6 Address: 2001:470:1f11:1178::1/64

Unfortunately, there's a lot of IPv6 tunnel brokers, and their documentation often clutters the search results for how to setup your own IPv6 tunnel. I have a Linux server with IPv6 connectivity. I want to make my own tunnel (very securely, via SSH SOCKS or similar, if possible) for my Windows 7 x64 computer to utilize for all IPv6 purposes ...

2017年3月16日 · If your have an IPv6 tunnel broker then your IPv6 packets will be put inside IPv4 packets. Those packets are then sent to the IPv4 address of the tunnel broker, where the IPv4 header is removed and the inner IPv6 packet is forwarded to the IPv6 internet as usual. No NAT is involved. IPv4 is completely independent of IPv6.

Sixxs's AYIYA tunnel looks like it could be a work-around, but they refused my application for a tunnel without giving a reason (which is fair enough, for a free service). So, from behind a large-scale NAT network (that I have no control over and can't open ports for), is there any other tunnel technology, and tunnel provider, that is usable?

2015年3月1日 · The broker endpoint was 2001:470:1f0e while subnet for my LAN was 2001:470:1f0f. I had simply used the wrong one like you said. I had simply used the wrong one like you said. However, is there a way to refresh the interface?

2019年3月1日 · (As mentioned above, either configure the tunnel on a router, or turn the tunnel endpoint into a router if it's capable of it.) The tunnel configuration is the same as before: the device still has its own address (the "Client IPv6 address" from tunnel info), it just additionally receives traffic meant for the extra "routed /48" network.