[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Please help... odd problems with one machine, the other works fine.

Hello,
I just installed freenet6 on two machines - continuity, which is a server that I have at a colocation facility, and indigo, my machine at home.
The server at the colocation facility (accessible at 3ffe:b80:2:d79e::2) seems to be working fine. That is, I can ping6 hosts on the 6bone, etc.
However, my machine at home is acting very oddly. In theory, it should be accessible on the 6bone at 3ffe:b80:2:d78d::2. In fact, I can ping6 my machine from my server: 
kevin@continuity:~$ ping6 3ffe:b80:2:d78d::2
PING 3ffe:b80:2:d78d::2(3ffe:b80:2:d78d::2) from 3ffe:b80:2:d79e::2 : 56 data bytes 
64 bytes from 3ffe:b80:2:d78d::2: icmp_seq=1 ttl=63 time=118 ms

However, I can't ping6 in the opposite direction:
kevin@indigo:~$ ping6 3ffe:b80:2:d79e::2
PING 3ffe:b80:2:d79e::2(3ffe:b80:2:d79e::2) from 3ffe:b80:2:d78d::2 : 56 data bytes 
ping: recvmsg: No route to host

However, I *can* tracepath6 from my machine at home to my server:
kevin@indigo:~$ /usr/sbin/tracepath6 3ffe:b80:2:d79e::2
 1?: [LOCALHOST]                      pmtu 1280
 1:  3ffe:b80:2:d79e::1                        96.602ms
 2:  suffusionsmain.tsps1.freenet6.net        133.490ms reached
     Resume: pmtu 1280 hops 2 back 2

and I can also do so from my server to my machine at home:
kevin@continuity:~$ /usr/sbin/tracepath6 3ffe:b80:2:d78d::2
 1?: [LOCALHOST]                      pmtu 1280
 1:  3ffe:b80:2:d78d::1                        58.038ms
 2:  suffusionshome.tsps1.freenet6.net        133.297ms reached
     Resume: pmtu 1280 hops 2 back 2
So... why can my machine at home successfully determine the path to my server, but I can't connect to anything? Why does it always say "No route to host"?
To elaborate even further, I have another machine at home running MacOS X 10.2, which has IPv6 support. I can ping6 my linux machine from the mac: 
[xavier:~] kevin% ping6 -I en0 fe80::200:c5ff:fe53:42a7
PING6(56=40+8+8 bytes) fe80::230:65ff:fe7c:e792%en0 --> fe80::200:c5ff:fe53:42a7 16 bytes from fe80::200:c5ff:fe53:42a7%en0, icmp_seq=0 hlim=64 time=0.626 ms 16 bytes from fe80::200:c5ff:fe53:42a7%en0, icmp_seq=1 hlim=64 time=0.424 ms 

but I can't ping6 the mac from the linux machine:
kevin@indigo:~$ ping6 -I eth0 fe80::230:65ff:fe7c:e792
PING fe80::230:65ff:fe7c:e792(fe80::230:65ff:fe7c:e792) from fe80::200:c5ff:fe53:42a7 eth0: 56 data bytes 
ping: recvmsg: No route to host
This time, an interesting thing occurs when I try to tracepath6 from the linux machine to the mac: 
indigo:~# traceroute6 -i eth0 fe80::230:65ff:fe7c:e792
traceroute to fe80::230:65ff:fe7c:e792 (fe80::230:65ff:fe7c:e792) from fe80::200:c5ff:fe53:42a7, 30 hops max, 16 byte packets 1 78fd:ffbf:aeeb:1140:e0a0:408:70a2:408 (78fd:ffbf:aeeb:1140:e0a0:408:70a2:408) 0.362 ms 0.517 ms 0.273 ms 

Where'd that address come from?! What's it mean?!
Any help would be greatly appreciated. I've looked through the list archives, etc., but can't seem to find anything relating to a situation like this. 

Thanks,
Kevin Pfohl
Reply to: