[6bone] IPv6 via NAT - problems

[Jeremy Worrells]

Thanks Jeroen! That did the trick. Looks like I'm up!

frink# ping6 www.jp.freebsd.org
PING6(56=40+8+8 bytes) 3ffe:b80:2:f1a6::2 -->
3ffe:505:2008:1:2e0:18ff:fea8:4533
16 bytes from 3ffe:505:2008:1:2e0:18ff:fea8:4533, icmp_seq=0 hlim=56
time=445.559 ms

Fantastic!

Jeremy
----- Original Message -----
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Jeremy Worrells'" <jeremy@worrells.org>
Cc: "'6bone'" <6bone@isi.edu>
Sent: Monday, October 21, 2002 3:16 PM
Subject: RE: [6bone] IPv6 via NAT - problems


Jeremy Worrells [mailto:jeremy@worrells.org] wrote:

> Unfortunately, 172.16.0.4 is on a non-routeable subnet that I
> am using. I tried using 172.16.0.4 as my address, but freenet6 throws
> away any request using 10/8, 172.16/12, or 192.168/16 addresses, as
it's not
> routable. I thought that using my DSL router's address would let the
> packets be NATted and work just fine.

You should request the tunnel with your external (public) interfaces IP
address.
Then you should reconfigure your gif0 endpoint to 172.16.0.4.
Check the ifconfig line I gave below, it will work ;)

Greets,
 Jeroen

> > Jeremy Worrells wrote:
> >
> > <SNIP>
> > > 11:33:50.929054 worrells.dsl.xmission.com > www.freenet6.net:
> > > jworrells.tsps1.freenet6.net >
> > > 3ffe:505:2008:1:2e0:18ff:fea8:4533: icmp6:
> > > echo request (encap)
> > > 11:33:51.358566 www.freenet6.net > 172.16.0.4:
> > > 3ffe:505:2008:1:2e0:18ff:fea8:4533 >
> > > jworrells.tsps1.freenet6.net: icmp6:
> > > echo reply (encap)
> >
> > Tunnel endpoint is 172.16.0.4 but:
> >
> > <SNIP>
> >
> > > gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
> > >         tunnel inet 166.70.27.6 --> 206.123.31.114
> > >         inet6 fe80::203:47ff:fe98:96f5%gif0 prefixlen 64
> > scopeid 0x7
> > >         inet6 3ffe:b80:2:f1a6::2 --> 3ffe:b80:2:f1a6::1
> > prefixlen 128
> >
> > It's configured as 166.70.27.6.
> >
> > Change that and it will work:
> > ifconfig gif0 tunnel 172.16.0.4 206.123.31.114
> >
> > The kernel throws away your packets as the local endpoint
> > doesn't match.