Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 08 Dec 2006 12:22:10 -0500
From:      Joe Marcus Clarke <marcus@FreeBSD.org>
To:        gnn@FreeBSD.org
Cc:        current@FreeBSD.org
Subject:   Re: Problem with gif and IPv6 in -CURRENT
Message-ID:  <1165598530.55760.7.camel@shumai.marcuscom.com>
In-Reply-To: <m24ps6bfpq.wl%gnn@neville-neil.com>
References:  <4578995B.4090305@FreeBSD.org> <m24ps6bfpq.wl%gnn@neville-neil.com>

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

--=-5d3pORTv/WytuBUBzOgi
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2006-12-08 at 22:54 +0800, gnn@freebsd.org wrote:
> At Thu, 07 Dec 2006 17:44:43 -0500,
> Joe Marcus Clarke wrote:
> >=20
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >=20
> > I am running:
> >=20
> > FreeBSD jclarke-pc 7.0-CURRENT FreeBSD 7.0-CURRENT #81: Thu Dec  7
> > 16:06:32 EST 2006     marcus@jclarke-pc:/usr/obj/usr/src/sys/JCLARKE-PC
> >  i386
> >=20
> > And I am trying to get a gif IPv6 tunnel up to a Cisco router.  I can
> > get this to work on a 6.2-PRERELEASE server, but the -CURRENT machine
> > always claims there is no route to the far end of the point-to-point
> > link.  Here is my config:
> >=20
> > # ifconfig gif0 create
> > # ifconfig gif0 tunnel 172.18.173.17 10.29.100.75
> > # ifconfig gif0 inet6 3ffe:604::2 3ffe:604::1 prefixlen 128
> > # ifconfig gi0
> > gif0: flags=3D8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
> >         tunnel inet 172.18.173.17 --> 10.29.100.75
> >         inet6 fe80::211:11ff:fe10:461e%gif0 prefixlen 64 scopeid 0x4
> >         inet6 3ffe:604::2 --> 3ffe:604::1 prefixlen 128
> >=20
> > This looks good, and I can ping my local 3ffe:604::2 address.  However,
> > when I ping 3ffe:604::1, I get:
> >=20
> > ping6: UDP connect: No route to host
> >=20
> > It's not lying.  I don't have a route to 3ffe:604::1:
> >=20
> > # netstat -nr
> > ...
> > ::/96                             ::1                           UGRS
> >     lo0
> > ::1                               ::1                           UHL
> >     lo0
> > ::ffff:0.0.0.0/96                 ::1                           UGRS
> >     lo0
> > 2003:a02::/64                     link#1                        UC
> >     em0
> > 2003:a02::1                       00:11:11:10:46:1e             UHL
> >     lo0
> > 3ffe:604::2                       link#4                        UHL
> >     lo0
> > fe80::/10                         ::1                           UGRS
> >     lo0
> > fe80::%em0/64                     link#1                        UC
> >     em0
> > fe80::211:11ff:fe10:461e%em0      00:11:11:10:46:1e             UHL
> >     lo0
> > fe80::%lo0/64                     fe80::1%lo0                   U
> >     lo0
> > fe80::1%lo0                       link#3                        UHL
> >     lo0
> > fe80::%gif0/64                    link#4                        UC
> >    gif0
> > fe80::211:11ff:fe10:461e%gif0     link#4                        UHL
> >     lo0
> > ff01:1::/32                       link#1                        UC
> >     em0
> > ff01:3::/32                       ::1                           UC
> >     lo0
> > ff01:4::/32                       link#4                        UC
> >    gif0
> > ff02::/16                         ::1                           UGRS
> >     lo0
> > ff02::%em0/32                     link#1                        UC
> >     em0
> > ff02::%lo0/32                     ::1                           UC
> >     lo0
> > ff02::%gif0/32                    link#4                        UC
> >    gif0
> >=20
> > The IPv4 address on the other end of the tunnel is reachable, and the
> > Cisco router has no problems finding a route to the FreeBSD machine.
> > Here is the config from the Cisco side:
> >=20
> > interface Tunnel1
> >  no ip address
> >  load-interval 30
> >  ipv6 address 3FFE:604::1/126
> >  ipv6 enable
> >  tunnel source 10.29.100.75
> >  tunnel destination 172.18.173.17
> >  tunnel mode ipv6ip
> >=20
> > Why isn't the other end of the point-to-point tunnel being instantiated
> > in the routing table?  If I take this exact config to a 6.2 box, this
> > works just fine, and the far end of the PTP link is instantiated in the
> > routing table.  Thanks for any clues you can provide.
>=20
> I'm not sure for the reason for that but I find that with this in my
> rc.conf my PTP comes up just fine:
>=20
> #IPv6 Config
> gif_interfaces=3D"gif0"
> gifconfig_gif0=3D"124.39.153.88 211.14.6.238"
>=20
> ipv6_enable=3D"YES"
> ipv6_network_interfaces=3D"bge0"
> ipv6_ifconfig_bge0=3D"2001:2f0:104:8081::1 prefixlen 64"
> ipv6_defaultrouter=3D"::1 -ifp gif0"
> ipv6_gateway_enable=3D"YES"
>=20
> It might be the "ipv6_defaultrouter" line above that makes this all
> work.

This did it.  Thanks!  In 6.X I could use a default route of 3ffe:604::1
(in this example), and I did not need a route at all just to get to the
other end of the PTP link.  All the examples I found online assumed
4.4-RELEASE up to 6.X.

Joe

--=20
Joe Marcus Clarke
FreeBSD GNOME Team      ::      gnome@FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome

--=-5d3pORTv/WytuBUBzOgi
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQBFeZ9Cb2iPiv4Uz4cRAoCOAJ9k4kf1BX4Naqvcv8MyhM3JU72rqgCgneQb
zPFoCoI1gufUF3aHBkyW0lA=
=6QCq
-----END PGP SIGNATURE-----

--=-5d3pORTv/WytuBUBzOgi--




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