New user getting very discouraged with IPv6 problems, cannot get tunnel working completely :(

aksis aksis at idea-anvil.net
Sat Sep 24 04:33:26 PDT 2005


On Friday 23 September 2005 01:08, resonant evil wrote:
>
> Here are the full tunnel details I was approved for
> Server IPV4 Address: 64.71.128.83 <http://64.71.128.83>
> Server IPV6 Address: 2001:470:1F01:FFFF::DD2/127
> Client IPV4 Address: 70.28.MY.IP
> Client IPV6 Address: 2001:470:1F01:FFFF::DD3/127
>
> in my /etc/rc.conf, I have
>
> ipv6_enable="YES"
> ipv6_gateway_enable="YES"

Im using Hurricane Electric as well,
When you login to HE they have a link for an example config generation, this 
is what I used. I had some problems with the handbook as well.

My rc.conf:
... snip ...
gif_interfaces="gif0 gif1"      # IPv6 tunnel
gifconfig_gif0="63.226.12.96 64.71.128.82" # IPv4 tunnel for IPv6 tunnel

ipv6_enable="YES"              	 # Set to YES to set up for IPv6.
ipv6_network_interfaces="rl0 gif0"      # List of network interfaces.
ipv6_defaultrouter="2001:470:1F00:FFFF::22E" # Set to IPv6 default gateway
ipv6_ifconfig_rl0="2001:470:1F00:379::1" # assigned from my /64to a nic
ipv6_ifconfig_gif0="2001:470:1F00:FFFF::22F 2001:470:1F00:FFFF::22E prefixlen 
128" <--- wrapped, should be on the above line.
... snip ...

My Assigned Prefix: 2001:470:1F00:379::/64

# ifconfig gif0 
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
        tunnel inet 63.226.12.96 --> 64.71.128.82
        inet6 fe80::2c0:f0ff:fe2a:aa7c%gif0 prefixlen 64 scopeid 0x8
      inet6 2001:470:1f00:ffff::22f --> 2001:470:1f00:ffff::22e prefixlen 128 


Is your firewall blocking ipv6?
# /etc/rc.firewall6 open

Don't leave this open after you get the tunnel working.

> That goes off without any errors or anything, and then that guide tells me
> to 'ping6 ff02::1%gif0' and it works perfectly, and I get ping replies, so
> I get REALLY excited. Then, the guide tells me to finish by

ping their ipv6 end point of the tunnel:

# ping6 2001:470:1F01:FFFF::DD2 (you sure its /127 and not /128?)

If you don't get replies then there is a problem with the tunnel.

> irc'ing an ipv6 server just resolves the IPV6 address but doesn't actually
> get past the CONNECTING stage

Last I knew, freenode has all HE ipv6 blocked because of abuse. This might 
have been lifted, I don't use ipv6 for irc.


More information about the freebsd-questions mailing list