I've got a strange problem here with ping6 from Sid. I set up an IPv6-in-IPv4 tunnel between two hosts, and, except for pinging through it, it's working. Host B has a tunnel from freenet6, and it's forwarding host A's packets over that. However, if from host A I try to ping anything, I get this: cna:~# ping6 -c1 3ffe:b80:d8d:42::1 PING 3ffe:b80:d8d:42::1(3ffe:b80:d8d:42::1) from 3ffe:b80:d8d:42::2 : 56 data bytes ping: recvmsg: No route to host and it just hangs. In the mean time, on the same box: cna:~# tcpdump -i sit1 tcpdump: WARNING: sit1: no IPv4 address assigned tcpdump: listening on sit1 12:09:04.275550 3ffe:b80:d8d:42::2 > 3ffe:b80:d8d:42::1: icmp6: echo request 12:09:04.321065 3ffe:b80:d8d:42::1 > 3ffe:b80:d8d:42::2: icmp6: echo reply Host A has 3ffe:b80:d8d:42::2 as its IP, host B has 3ffe:b80:d8d:42::1. Host A is running 2.4.19 patched with FreeS/Wan, host B is running the USAGI version of 2.4.18. (Might this be an incompatibility between the two?) The routing tables should be fine, IMO, the packets do get back just fine, and everything else works just fine. Any ideas on what I might be doing wrong? -- PGP public key: http://www.wolfheart.ro/pubkey.asc
Attachment:
signature.asc
Description: This is a digitally signed message part