he.net IPv6 tunnel

[David Benfell]

Hi all,

It turns out my new ISP, the only one available here, doesn't do IPv6
(yet). So I've been trying to get a tunnel from he.net up.

Here is the relevant snippet from rc.conf:

ipv6_activate_all_interfaces="YES"
# IPv6-over-IPv4 tunnel supplied by he.net; ID 258129
ipv6_network_interfaces="em0"
ifconfig_em0_ipv6="inet6 accept_rtadv"
rtsold_enable="NO"
ipv6addrctl_policy="ipv6_prefer"
cloned_interfaces="gif0"
gifconfig_gif0="50.250.218.161 64.62.134.130"
ifconfig_gif0_ipv6="inet6 2001:470:66:119::2 2001:470:66:119::1
prefixlen 128"
ipv6_defaultrouter="2001:470:66:119::1"

Here is ifconfig -a:

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 44:39:c4:3a:d7:ea
        inet 50.250.218.161 netmask 0xfffffff0 broadcast
50.250.218.175 
        inet6 fe80::4639:c4ff:fe3a:d7ea%em0 prefixlen 64 scopeid 0x1 
        inet 50.250.218.162 netmask 0xffffffff broadcast
50.250.218.162 
        inet 50.250.218.163 netmask 0xffffffff broadcast
50.250.218.163 
        inet 50.250.218.164 netmask 0xffffffff broadcast
50.250.218.164 
        inet 50.250.218.165 netmask 0xffffffff broadcast
50.250.218.165 
        inet 50.250.218.166 netmask 0xffffffff broadcast
50.250.218.166 
        inet 50.250.218.167 netmask 0xffffffff broadcast
50.250.218.167 
        inet 50.250.218.168 netmask 0xffffffff broadcast
50.250.218.168 
        inet 50.250.218.169 netmask 0xffffffff broadcast
50.250.218.169 
        inet 50.250.218.170 netmask 0xffffffff broadcast
50.250.218.170 
        inet 50.250.218.171 netmask 0xffffffff broadcast
50.250.218.171 
        inet 50.250.218.172 netmask 0xffffffff broadcast
50.250.218.172 
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
gif0: flags=8011<UP,POINTOPOINT,MULTICAST> metric 0 mtu 1280
        inet6 2001:470:66:119::2 --> 2001:470:66:119::1 prefixlen 128 
        inet6 fe80::4639:c4ff:fe3a:d7ea%gif0 prefixlen 64 scopeid 0x3 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Here is ping6 ipv6.google.com:

PING6(56=40+8+8 bytes) 2001:470:66:119::2 --> 2607:f8b0:4010:801::1003
ping6: sendmsg: Network is down
ping6: wrote ipv6.l.google.com 16 chars, ret=-1
ping6: sendmsg: Network is down
ping6: wrote ipv6.l.google.com 16 chars, ret=-1
ping6: sendmsg: Network is down
ping6: wrote ipv6.l.google.com 16 chars, ret=-1

When I used the example script that he.net supplies, it brought up
enough IPv6 that I could ping out, and I could ping the two tunnel
endpoints from inside or out. Now, after rebooting, I don't even have
that.

But I also need the routable addresses (I think I got a /64 block)
associated with an interface so they can actually be used. And I don't
see anything on how this is supposed to be done.

Help?

Thanks!


-- 
David Benfell <benfell at parts-unknown.org>
See https://parts-unknown.org/node/2 if you don't understand the
attachment.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20140803/bdddc2a9/attachment.sig>