RESOLVED - IPv6 tunnel offline - sendto error: 13 in logs

reisender

I am attempting to setup a Hurricane Electric (HE) IPv6 tunnel, but have not been successful. I'll admit I don't have a true need for the tunnel right now, but I want to learn more about configuring IPv6 and thought this sounded like a good place to start. I don't have all of the pieces of the puzzle, but I'm hoping someone can point me in the right direction.

I am using pfSense 2.4.2. I set up the (HE) tunnel on their website. The HE website confirmed that it is able to ping my public IP address, so I believe that is setup correctly. I followed the guide found here: https://doc.pfsense.org/index.php/Using_IPv6_with_a_Tunnel_Broker

It fails when I get to the step that says the gateway should be listed as online. The gateway logs shows the following entry twice per second:

Dec 10 21:06:48 dpinger HE_v6 2001:4860:4860::8888: sendto error: 13
Dec 10 21:06:48 dpinger HE_v6 2001:4860:4860::8888: sendto error: 13
Dec 10 21:06:47 dpinger HE_v6 2001:4860:4860::8888: sendto error: 13
Dec 10 21:06:47 dpinger HE_v6 2001:4860:4860::8888: sendto error: 13
Dec 10 21:06:46 dpinger HE_v6 2001:4860:4860::8888: sendto error: 13
Dec 10 21:06:46 dpinger HE_v6 2001:4860:4860::8888: sendto error: 13

I attached screenshots of my configuration.

I searched for the meaning of sendto error: 13, but didn't find anything.

Any suggestions on where I messed up?

gateway.jpg_thumb

interface.jpg_thumb

gif_config.jpg_thumb

johnpoz

I see you didn't set the HE gateway as default.. Which is listed in the steps to do.. I just setup HE again this morning on my shiny new sg4860 and no issues came right up..

Why are you changing the monitor IP? If the gateway is not set as default it would not know where to send to get to get to the IPv6 address you have set as monitor.

reisender

Good catch on the default gateway. I have now checked that box, but the tunnel still isn't coming up.

I had set the monitor IP to Google's DNS while trying to troubleshoot. I've removed that again, still no success.

The logs still show the same error, just with a different IP.

Dec 11 19:12:00 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13
Dec 11 19:11:59 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13
Dec 11 19:11:58 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13
Dec 11 19:11:58 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13
Dec 11 19:11:57 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13
Dec 11 19:11:57 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13
Dec 11 19:11:56 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13
Dec 11 19:11:56 dpinger HE_v6 2001:470:x:xxxx::1: sendto error: 13

reisender

The good news, the tunnel is now working. I decided to do a clean install and import the backup config. Once I did that, the tunnel came up right away. I don't know what, but something must have been messed up in my system - which has been upgraded several times.

a4ehusker

I know this is an old post but in case anybody else finds it and need a possible solution:

For me it was because I had Snort running, and it blocked the Tunnel IPv4 endpoint. I had to add it to the alias list that I use to whitelist IPs for Snort (and restart Snort!)