Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 ... 6 7 [8] 9 10
 71 
 on: June 28, 2019, 10:21:56 AM 
Started by bunxbun - Last post by snarked
Your public address.

 72 
 on: June 28, 2019, 10:16:29 AM 
Started by bunxbun - Last post by bunxbun
I am at my wits end on this. I tried all day yesterday to get this to work.

I have the tunnel setup on a Centos VM and I can ping out from it, great.

I enabled this https://docs.netgate.com/pfsense/en/latest/book/config/advanced-networking.html#ipv6-over-ipv4-tunneling but no where does it say what IP goes in the "IPv4 address of Tunnel Peer" field. Is it HE's endpoint? or the local behind NAT IP? either way, I tried both and it doesn't seem to matter. Also it says firewall rules need to be made but no where does it indicate what those rules look like.

So I checked that, and made firewall rules where protocol is IPv4 IPV6, source is HE endpoint, destination is my local VM ip and any port. Which pfsense does seem to match a state to the traffic of this rule. But if I stop traffic for 15 minutes or so I can't access the VM from the other side of the tunnel until I start pinging from my side of it.

I even tried making a NAT rule on IPV6 protocol source HE endpoint destination my WAN redirect to my internal VM and any port. nothing.

I deleted all that and unchecked the ipv6 over ipv4 stuff and it still works if I ping from my side first. So what was any of the above doing? Seems nothing.

Anyone have any idea how this is supposed to be configured? My google fu finds people who say they couldn't do this with a consumer router but got it working with pfsense but don't say how...

 73 
 on: June 28, 2019, 03:34:02 AM 
Started by KNBu5ZMdbR - Last post by KNBu5ZMdbR
Thank you.

FYI, here's an analysis of the routing issue: https://blog.cloudflare.com/the-deep-dive-into-how-verizon-and-a-bgp-optimizer-knocked-large-parts-of-the-internet-offline-monday/

 74 
 on: June 26, 2019, 07:32:24 AM 
Started by isaackwan - Last post by splud
Need My  Sage tshirt please

 75 
 on: June 25, 2019, 07:30:21 PM 
Started by hakami - Last post by hakami
Hello,
Does anyone know How to configure HE ipv6 for kubernets?

 76 
 on: June 24, 2019, 09:01:27 PM 
Started by KNBu5ZMdbR - Last post by broquea
Your issue was the result of a larger issue created by Verizon who accidentally accepted routes learned from their customer, that re-advertised around 2400 other network's IP space.

Tunnels are point-to-point, so on our side it sources from a fixed IP. There is no alternative IP that your tunnel would be configured for on our local side.

 77 
 on: June 24, 2019, 06:31:49 AM 
Started by KNBu5ZMdbR - Last post by KNBu5ZMdbR
Now I can ping again and the tunnel comes up fine.

I'd still be interested to know if there's a backup IPv4 to use.

 78 
 on: June 24, 2019, 05:05:56 AM 
Started by KNBu5ZMdbR - Last post by KNBu5ZMdbR
Hi.  My IPv6 went out.  it was last working eight hours ago.  I noticed that I can't ping 209.51.161.14, my IP6 Tunnel Endpoint, Server IPv4 Address.  I tried it from my router.  It can ping other sites (yahoo.com) but not 209.51.161.14.

Is there an alternate IPv4 address that I can use to get my tunnel working again?

 79 
 on: June 18, 2019, 07:20:13 AM 
Started by TobiasFuchs - Last post by TobiasFuchs
Thank you.
The failure was on my side. After knowing that the tunnel is OK it was easy to find the configuratrion mistake on my system.
Problem is solved.

 80 
 on: June 17, 2019, 07:48:49 AM 
Started by TobiasFuchs - Last post by broquea
Generally under a minute. Looking at your tunnels, the SMTP filter was removed and is not in place.

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