Just recently I managed to get a virtualized IPFire (Linux) to use my IPv6 tunnel, even though IPv6 is not officially supported. Turned out that the IPv6-related modules were present, just not loaded and had to edit a couple of configuration files because IPv6 was set disabled.
Unfortunately there's no (easy) way to get radvd and/or DHCPv6 installed and working. That will involve cross compiling and might not even work. There's no radvd or DHCPv6 addon available, there is also no C-compiler for IPFire, which makes ./configure and make useless. So if I want to try that, I'll have to try IPFire's build-environment or use a different operating system to compile everything and pray it might work.
So I figured I'd try a static-config first, but can't get that to work and that is why I made this topic. I cannot get the host of the virtual machine (Windows 7 Ultimate x64) to connect to websites or IPFire using IPv6. Pings to the IPv6 address of IPFire's green0(=LAN) interface fail with timeout errors, the other way round as well. Although from IPFire's end, I'm using
My Traceroute since ping6 wasn't compiled into the kernel

Now the strange part: if I ping -6 IPFire using the fe80 address of the green0/LAN-interface then pings are successful. Although the 1st one always fails, after the one fail it works. The other way round it only works if I use the fe80 address of "VMware Network Adapter VMnet1" on the host, can't reach the fe80 address of the physical LAN-interface of the host.
I'm guessing that being able to ping the fe80 addresses rules out firewall issues, although I disabled it on the host to be sure. I also checked if forwarding is enabled:
[root@ipfire-test ~]# cat /proc/sys/net/ipv6/conf/all/forwarding
1
The only other cause I can think of is that VMware Workstation 9.0.0 is being a pain in the butt. The reason I virtualized this is because I want to test it first and make sure nothing gets broken in the process of getting IPFire to support IPv6 even though it, officially, is not supported.
I've set the virtualized LAN-interface of IPFire to "host-only", the WAN-interface to bridged. IPFire demands the WAN (red0) and LAN interface to be in different subnets/ranges, so I cannot set them both to bridged. Maybe the host-only setting is preventing IPv6 access? But then I shouldn't have been able to ping the fe80 addresses(?).
But first let's make sure all the settings check out. This is what I got:
Server IPv4 Address:216.66.84.46
Server IPv6 Address:2001:****:**14:***8::1/64
Client IPv4 Address:IP-address of IPFires virtualized WAN-interface
Client IPv6 Address:2001:****:**14:***8::2/64
Routed IPv6 Prefixes
Routed /64:2001:****:**15:***9::/64
Routed /48:Assign /48
Available DNS Resolvers
Anycasted IPv6 Caching Nameserver:2001:470:20::2
Anycasted IPv4 Caching Nameserver:74.82.42.42
IPFire: (Someone was kind enough to put a pre-compiled ifconfig with IPv6 support online

)
[root@ipfire-test ~]# ifconfig
green0 Link encap:Ethernet HWaddr 00:50:56:26:A9:A5
inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fe26:a9a5/64 Scope:Link
inet6 addr: 2001:****:**15:***9::1/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6371 (6.2 Kb) TX bytes:10961 (10.7 Kb)
Interrupt:16 Base address:0x2080
he-ipv6 Link encap:UNSPEC HWaddr C0-A8-01-29-FF-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::c0a8:129/128 Scope:Link
inet6 addr: 2001:****:**14:***8::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3474 (3.3 Kb) TX bytes:3474 (3.3 Kb)
red0 Link encap:Ethernet HWaddr 00:50:56:27:7F:B1
inet addr:192.168.1.41 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fe27:7fb1/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:101 errors:0 dropped:2 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16244 (15.8 Kb) TX bytes:8793 (8.5 Kb)
Interrupt:19 Base address:0x2000
[root@ipfire-test ~]# ip -6 route
2001:****:**14:***8::/64 via :: dev he-ipv6 proto kernel metric 256
2001:****:**15:***9::/64 dev green0 proto kernel metric 256
fe80::/64 dev green0 proto kernel metric 256
fe80::/64 dev red0 proto kernel metric 256
fe80::/64 via :: dev he-ipv6 proto kernel metric 256
default dev he-ipv6 metric 1024
The host, with these two being relevant:
LAN-verbinding = physical LAN-interface
VMware Network Adapter VMnet1 = IPFire's host-only LAN-interface
Windows IP-configuratie
Draadloos LAN-adapter voor Draadloze netwerkverbinding:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel: localdomain
Ethernet-adapter voor LAN-verbinding:
Verbindingsspec. DNS-achtervoegsel:
IPv6-adres. . . . . . . . . . . . : 2001:****:**15:***9::2
Link-local IPv6-adres . . . . . . : fe80::ac25:6ddb:20b6:ad66%11
IPv4-adres. . . . . . . . . . . . : 192.168.1.11
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . : 2001:****:**15:***9::1
192.168.1.1
Ethernet-adapter voor VMware Network Adapter VMnet1:
Verbindingsspec. DNS-achtervoegsel:
Link-local IPv6-adres . . . . . . : fe80::bc3c:537f:4e2d:e2f1%19
IPv4-adres. . . . . . . . . . . . : 10.0.0.1
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . :
Ethernet-adapter voor VMware Network Adapter VMnet8:
Verbindingsspec. DNS-achtervoegsel:
Link-local IPv6-adres . . . . . . : fe80::dce7:db34:44c9:112a%20
IPv4-adres. . . . . . . . . . . . : 192.168.85.1
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . :
Tunnel-adapter voor isatap.localdomain:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Tunnel-adapter voor isatap.{5CFD9F22-6CEA-43BB-B6C6-D3CAFBDD5CC3}:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Tunnel-adapter voor LAN-verbinding* 9:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Tunnel-adapter voor isatap.{56D84449-E100-440D-9BB2-AA495539F069}:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Tunnel-adapter voor isatap.{8555E581-1A7E-4875-8FBC-3EC34E065FFB}:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Unless I overlooked something, everything checks out. Can anyone confirm that?