> You can run "aiccu test" and it might show you where the problem is.
Not when you know as little about IPv6 as I do, you can't :-)
> ip -6 addr
[root@OldEmpire ~]# ip -6 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::204:23ff:fe65:9818/64 scope link
valid_lft forever preferred_lft forever
13: sixxs: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280
inet6 2a01:348:6:417::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5b54:306b/128 scope link
valid_lft forever preferred_lft forever
> ip -6 ro
[root@OldEmpire ~]# ip -6 ro
2a01:348:6:417::/64 via :: dev sixxs proto kernel metric 256 mtu 1280
advmss 1220 hoplimit 0
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220
hoplimit 0
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
default via 2a01:348:6:417::1 dev sixxs metric 1024 mtu 1280 advmss 1220
hoplimit 0
> Can you ping it?
I can't ping the PoP - but the unreachable message when I ping Google
seems to come from the PoP. At this point, I have to recognise the limit
of my knowledge in this area...
> cl-1048.lon-02.gb.sixxs.net is your end of the tunnel; its IP ends
> in ::2.
Ah, OK. I didn't realise that. Given the FWDN in question, I thought that
was the far end. OK, looks like it's my cock-up...
> The sixxs POP's end will be gw-1048.lon-02.gb.sixxs.net and
> its IP will end in ::1.
Gotcha. Thanks for that.
Back to reading...
Vic.
