Hi Cory,
yep. I have all that. Got that far all together. Started with tspc, but then
moved to setting up 6to4 without it.
However - everything works on my 'router' machine. etc etc, except
connecting to my client machine via a planned IP.
If you look at your tcpdump....
>
> >From the client machine using tcpdump
>
> tcpdump: listening on xe0
> 19:45:38.805354 fe80::210:a4ff:feb2:75ca > ff02::2: icmp6: router
solicitation
> 19:45:39.225390 fe80::2a0:ccff:fe77:2b27 > ff02::1: icmp6: router
advertisement
^^^^^^^^^^^^^^^^^^^^^^^^^^
This is the internal interface address. This can't be used - as I understand
it - for advertising over the networks.
ok - let me rephrase this.
11:21:30.276036 2002:cb01:6006::1.telnet > fe80::210:b5ff:fee4:4386.4313:
11:21:30.277592 fe80::210:b5ff:fee4:4386.4313 > 2002:cb01:6006::1.telnet:
This is from the machine 1, where I have the gateway and so on set up.
You can see that it's address is 2002:cb01:6006::1
Machine 2 has an advertised address of fe80::210:b5ff:fee4:4386.4313
Which is useless for DNS purposes. Its the mac address/interface.
What I need to know is how to put a 2002 address onto machine 2, in place
of. or as well as that link address.
Machine 1: You can see the 2002 address configured onto the stf0 interface.
ruby# ifconfig
ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 203.1.96.6 netmask 0xffffff00 broadcast 203.1.96.255
inet6 fe80::240:5ff:fe4e:a982%ed0 prefixlen 64 scopeid 0x1
ether 00:40:05:4e:a9:82
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000000
stf0: flags=1<UP> mtu 1280
inet6 2002:cb01:6006::1 prefixlen 16
Machine 2: The client has no interface configured to the 2002 addressing.
And that's the part I'm trying to solve. :-) Even when I ran tspc on both
machines - it was the same, just different prefixes.
$ ifconfig
rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet 203.1.96.5 netmask 0xffffff00 broadcast 203.1.96.255
inet6 fe80::210:b5ff:fee4:4386%rl0 prefixlen 64 scopeid 0x1
inet 203.1.96.155 netmask 0xffffffff broadcast 203.1.96.155
inet 203.1.96.200 netmask 0xffffffff broadcast 203.1.96.200
ether 00:10:b5:e4:43:86
media: Ethernet 10baseT/UTP
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000000
faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500
stf0: flags=0<> mtu 1280
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet6 fe80::210:b5ff:fee4:4386%tun0 prefixlen 64 scopeid 0x5
inet 203.1.96.5 --> 139.130.78.1 netmask 0xffffff00
Opened by PID 53
2002:cb01:6006::1 ???????
[machine 1].............. ehternet..............[machine 2].........
ppp....... internet
this machine 2 should be 2002:cb01:6006::2
I know I'm missing something fundamental, but am getting so bamboozeled now
I can't see it.
Robert
>
> Anyway I hope this helps. I found that tspc -vv helped in my debugging.
>
> -Cory
>
>
>
>
> >
> >
> > Cory,
> > tried that. The problem seems to be that on the client - there is no
2002
> > interface that is set up with anything?
> >
> > robert
> >
> >
> >
> > > Robert,
> > >
> > > On the client side you need to run rtsold(8). Consider rtsold
something
> > along
> > > the lines of dhclient except for ipv6 rather than ipv4.
> > >
> > > /sbin/sysctl -w net.inet6.ip6.accept_rtadv=1
> > > /usr/sbin/rtsold xe0
> > >
> > > -Cory
> > >
> > >
> > > >
> > > >
> > > > Maybe I'm just plain stupid, but following the instructions for
6to4,
> > the
> > > > second host on the network simply will not 'autocinfigure' as
stated.
> > > >
> > > > I'm using FreeBSD on two machines on our IPv4 network, and have one
set
> > up
> > > > as the gateway, with all the apporpriate bits in place in the
rc.conf
> > file.
> > > > It all appears to work fine.
> > > > Machine 1:
> > > > ### IPv6 options: ###
> > > > ipv6_enable="YES" # Set to YES to set up for IPv6.
> > > > ipv6_network_interfaces="auto" # List of network interfaces (or
> > "auto").
> > > > ipv6_gateway_enable="YES" # Set to YES if this host will be a
> > gateway.
> > > > ipv6_static_routes="default"
> > > > ipv6_route_default="default 2002:c058:6301::"
> > > > stf_interface_ipv4addr="203.1.96.6"
> > > > rtadvd_enable="YES"
> > > > rtadvd_interfaces=""
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > According to the documentation, to put a second machine on the same
6to4
> > > > network, all I need do is put in the lines...
> > > > Machine 2:
> > > > ### IPv6 options: ###
> > > > ipv6_enable="YES" # Set to YES to set up for IPv6.
> > > > ipv6_network_interfaces="auto" # List of network interfaces (or
> > "auto").
> > > >
> > > > Well - I'm here to tell you it doesn't work.
> > > >
> > > > There is no connectivity between machine 2 and machine 1, because
there
> > is
> > > > no 2002: IP auto-configured on machine 2.
> > > > The only connectivity is between the link-local addresses (fe80) and
> > that's
> > > > no good for advertising and general connectivity.
> > > > Of course, the IPv4 network works fine between them - but not the
IPv6
> > > >
> > > > and, I now have a collection of 'solutions' that could fill a good
book,
> > and
> > > > none of which work. oh well. Interesting experiment anyway.
> > > >
> > > > cheers
> > > > Robert
> > > >
> > > >
> > > > ---
> > > > Quantum Radio: World Music with a difference.
> > > > http://quantum-radio.net/
> > > > Now Playing: Ethnic Music - Los Indios De Cuzco - Rin Del
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Cory B Zito, Contract Unix and VMS Systems Administrator,
[EMAIL PROTECTED]
> > > Copyright 2002 by Cory Zito, All Rights Reserved.
> > >
> >
> >
>
>
> --
> Cory B Zito, Contract Unix and VMS Systems Administrator, [EMAIL PROTECTED]
> Copyright 2002 by Cory Zito, All Rights Reserved.
>
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
