> You asked how to setup a tunnel, not anything else, and that didn't > change much from what is on the above page.
Apparently it's changed just enough for it to be relevant. See below. > Remove the first two defaults. > > "route -6 delete -inet6 default", twice, should work. > The reason why you have it twice though, might only be when it is on two > interfaces, looks weird and is wrong either way. First off, it's "route delete -inet6 default". Second, I can only run this command once, and then my routing table looks like this: Routing tables Internet6: Destination Gateway Flags default ::1 UG default ::1 UG ::1 ::1 UH ::127.0.0.0 ::1 UG ::224.0.0.0 ::1 UG ::255.0.0.0 ::1 UG ::ffff:0.0.0.0 ::1 UG 2001:5c0:8fff:fffe::28f4 2001:5c0:8fff:fffe::28f5 UH 2001:5c0:8fff:fffe::28f5 link#7 UH 2002:: ::1 UG 2002:7f00:: ::1 UG 2002:e000:: ::1 UG 2002:ff00:: ::1 UG fe80:: ::1 UG fe80::%xl0 link#1 U fe80::210:4bff:fecc:1f2e%xl0 0:10:4b:cc:1f:2e UH fe80::%fxp0 link#2 U fe80::207:e9ff:fe82:984c%fxp0 0:7:e9:82:98:4c UH fe80::%lo0 fe80::1%lo0 U fe80::1%lo0 link#5 UH fe80::%gif0 link#7 U fe80::210:4bff:fecc:1f2e%gif0 link#7 UH fec0:: ::1 UG ff01:: ::1 U ff02::%xl0 link#1 U ff02::%fxp0 link#2 U ff02::%lo0 ::1 U ff02::%gif0 link#7 U Further attempts at route deletion result in: schnarff.com:~$ sudo route delete -inet6 default writing to routing socket: No such process delete net default: not in table This looks thoroughly broken, but as I'm not the IPv6 expert here, I don't know how to fix it. > Try pinging 2001:5c0:8fff:fffe::28f5, 2001:5c0:8fff:fffe::28f4 etc and > then try something remote, or just try something remote and see if that > works. If you can't ping the ::28f4 then your tunnel is broken, use > tcpdump on the IPv4 interface (fxp0 in your case) to see if you get any > packets, like proto-41 unreach back from the remote side or from > intermediate routers. Or if you get packets back but the kernel filters > them out -> firewall issue. I can't ping the ::28f4 address. When I run tcpdump (which I have to do on gif0, not fxp0, if I want IPv6 traffic), I get: schnarff.com:~$ sudo tcpdump -n -i gif0 tcpdump: WARNING: gif0: no IPv4 address assigned tcpdump: listening on gif0 10:12:37.890333 2001:5c0:8fff:fffe::28f5 > 2001:5c0:8fff:fffe::28f4: icmp6: echo request 10:12:38.890316 2001:5c0:8fff:fffe::28f5 > 2001:5c0:8fff:fffe::28f4: icmp6: echo request 10:12:39.890308 2001:5c0:8fff:fffe::28f5 > 2001:5c0:8fff:fffe::28f4: icmp6: echo request 10:12:40.890305 2001:5c0:8fff:fffe::28f5 > 2001:5c0:8fff:fffe::28f4: icmp6: echo request Looks like the other side isn't paying any attention to me. Of course, seeing this, I noted that ::28f5 appeared to be where I was coming from, so I tried setting that as my default route. At that point, I could ping myself (at ::28f5), but I couldn't hit, say, 2001:200:0:8002:203:47ff:fea5:3085: schnarff.com:~$ ping6 www.kame.net PING6(56=40+8+8 bytes) 2001:5c0:8fff:fffe::28f5 --> 2001:200:0:8002:203:47ff:fea5:3085 ping6: sendmsg: No route to host ping6: wrote www.kame.net 16 chars, ret=-1 ping6: sendmsg: No route to host ping6: wrote www.kame.net 16 chars, ret=-1 > Good thing about IPv6, you can destroy it and IPv4 keeps working. > Alternatively when you have IPv4 and IPv6 native, like me, either of the > two can die, get firewalled and it will still work ;) I'm well aware of this...I just didn't want to start touching "default" routes, since a simple syntax error on my part could result in the whacking of my IPv4 default route. Given this, does the need to have some modern documentation on the subject seem a bit more clear? ;-) Alex Kirk --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
