Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Aug 2014 03:50:20 -0700
From:      David Benfell <benfell@parts-unknown.org>
To:        questions@freebsd.org
Subject:   he.net IPv6 tunnel
Message-ID:  <20140804105020.GD94656@home.parts-unknown.org>

next in thread | raw e-mail | index | archive | help

--k4f25fnPtRuIRUb3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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

Here is ifconfig -a:

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

Here is ping6 ipv6.google.com:

PING6(56=3D40+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=3D-1
ping6: sendmsg: Network is down
ping6: wrote ipv6.l.google.com 16 chars, ret=3D-1
ping6: sendmsg: Network is down
ping6: wrote ipv6.l.google.com 16 chars, ret=3D-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!


--=20
David Benfell <benfell@parts-unknown.org>
See https://parts-unknown.org/node/2 if you don't understand the
attachment.

--k4f25fnPtRuIRUb3
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJT32VrAAoJEBV64x4SNmArB90P/0+b7R5nzQJdKd0t2997PVLR
xC46b6vYaRZIifXf91aB0gcraVtNcGUj4GXg09d4yi3arcNrV1L0ZfVOk+HjcW/Y
WbPR5R5+aToWfM9zabqn3IxSzpveFVP52BDeeXDHrKhLnBxeRpCteAbZmhzDbbiB
v8HUR6A+mdg5wVxxk7sY++b22ImNekfEmHyRaMI2SzQIxUm9s1x9ZFm9Pr6XyQu7
7vAmgb+devKLI9bZyAbBUKSlDSZHTcjfIDYy5sfqi4P8jqL6Q21x6knAfSKpT1bc
/1ANyPJnuTbinHMmvgysUnFVQKSzT0xo7wn5xmhEZo7dUPLXyLAEbwu4E1MR4JBc
5QtfRGDVKJyXTLvAlzA17isYC2Ht4+T95NOqxLjwbeLpWthTJSk230Ta8fA41rCw
pNx/LbafC4t2AjLl5FIdPvc0MTDNimRjtGmsa7tvRZgDMUwCe82D1FPH81bS0ZyN
BIxpdsrlwhOrEdGXLEblNigp8ZObKGyOr8FbSumIfzzxytp3yuqRxR6NXWFs+MBB
P6CSBJISH+2snTx2O3tiwAv5408sKim4/5N9e8ss2/xuUDxYdoJGcI4qDG/8Qtrl
eplk1o4cDTzGErH36lEe0myeE0ry7vfV+vCsKjSDwIwr3O2lUkdvdqWxhUC3akS5
JsqJFkwMrz59kJWLydPB
=jJBr
-----END PGP SIGNATURE-----

--k4f25fnPtRuIRUb3--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140804105020.GD94656>