Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  


Welcome to Hurricane Electric's forums!

Pages: 1 2 [3] 4 5 ... 10
 on: August 14, 2017, 05:53:53 AM 
Started by rnolen - Last post by cholzhauer
You should create your own thread.

 on: August 14, 2017, 05:16:09 AM 
Started by rnolen - Last post by liuxyon
Sure.  Using ssh -w would work just fine.  You set up the SSH connection(s), then put IPv6 addresses on the associated TUN interfaces, and point routes though 'em.  Or run a dynamic routing proto.

You might also want to look into vtun, openvpn, and other stuff like that which supports IPv6.

how i do it? i am using windows ssh.

 on: August 11, 2017, 07:01:31 AM 
Started by ShinobiCrew - Last post by cholzhauer
So you've actually created a tunnel?  Where is it hosted?  Post the commands you used to create it as well as ipconfig/ifconfig from your computer

 on: August 10, 2017, 10:11:30 PM 
Started by ShinobiCrew - Last post by ShinobiCrew

I have spent 2 days reading about IPV6, as before doing so I knew exactly zero about this subject.  I have researched compatibility with my modem, provided by the isp, and direct connect to my computer to verify ipv6 connectivity.  there is... and then plugging the ethernet into my computer from the router...thats when i get nothing.  Through some forums, I saw that some were saying rollback the firmware.  I did that and not only did it not work, I cant update the router to the newest hardware.  I have used the cmd to get the required information such as:
IPV6 address
border relay
prefix and length
The Router is a EA4500 Linksys Dual band N-router.
...what else what else....
Right, so i found out about tunneling via testipv6, and established the config...still nothing..

If you need a Screenshot of anything specific please let me know, and please someone help. Ive been spending hours and hours trying to learn and configure all of literally going crazy

EDIT 1: Now I notice I can't use certain websites that I could before like and etc

 on: August 10, 2017, 06:50:16 AM 
Started by swschulz - Last post by swschulz
I am in the process of migrating DNS hosting to HE, and the first few have gone off without a hitch, but the last one has been failing the delegation test, and I'm not sure if there is something else I can do.

The domain is registered with namecheap, and I updated the nameservers for the domain there about 18 hours ago.  This morning, HE still shows that delegation is not complete.

I've checked `whois` and `dig NS` and both show the five HE nameservers, so I'm not sure if HE is caching some old results, or I'm missing something.


 on: August 08, 2017, 10:15:17 AM 
Started by afalk42 - Last post by broquea
As I mentioned in your trouble ticket, don't forget to install a pull-up route for your /48 either with a null route of the range, or configuring an IP out of it in an interface or loopback device.

 on: August 08, 2017, 06:58:50 AM 
Started by afalk42 - Last post by afalk42
I am trying to configure an IPv6 tunnel to tunnelbroker using BGP, since I have an assigned IPv6 address space. I have BGP configured on the SonicWall NSA 3600 using the command-line interface (CLI) and have created the following configuration (this is largely based on the SonicWall knowledgebase instructions here: plus information from their CLI manual regarding IPv6 and BGP here:

Code: [Select]
router bgp 54729
 neighbor 2001:470:1f0c:1f::1 remote-as 6939

 address-family ipv6
 network 2620:fc:8000::/48
 redistribute connected
 neighbor 2001:470:1f0c:1f::1 activate

BGP seems to be running correctly, and my router is communicating with the HE router via the IPv6 tunnel. However, HE tech support tells me that no advertised routes were received from my router:

Code: [Select]
No routes are received from  Neighbor 2001:470:1f0c:1f::2
ipv6 prefix-list as54729-tunnel-filter: 1 entries
     seq 3932 permit 2620:fc:8000::/48

I have searched via the SonicWall knowledge-base, these forums, and Google, but was unable to find any reference to what is amiss in my configuration. There is tons of more complicated examples using multi-homed configurations, but mine is single-homed, single-ISP (tunnel), but for a simple configuration like mine, the above config should be theoretically sufficient.

So, as far as I can tell, the configuration statement
Code: [Select]
network 2620:fc:8000::/48 in my configuration should advertise the network to the neighbor.

Anybody have any idea what is missing? I'm sorry, but while I'm quite knowledgable about IPv6, I'm not as familiar with BGP....

 on: August 06, 2017, 07:49:47 AM 
Started by primordial - Last post by bjo
I'm using the unbound-solution now, so no need for nullrouting prefixes in the Fritzbox, so I can not provide any screenshots.

 on: August 06, 2017, 07:47:52 AM 
Started by primordial - Last post by fir3drag0n
any help here?

 on: August 05, 2017, 10:16:31 AM 
Started by jmpoure - Last post by jmpoure
Fixed, thanks.

There was a small problem with my configuration:

option 'mtu' '1424'   
made the trick.

Many thanks.

Pages: 1 2 [3] 4 5 ... 10