Hi all, my name is Bob and I am going to try and share my experiences so far. I am currently disabled which gives me more time to tinker but less funds to invest in hardware. I have been working with computers since the mid 70's so I have seen more than most when it comes to all things electronics and digital. I have Windows 7 X64 on an AMD Athlon X64 6400+(3.2Ghz) with 8Gb of DDR2, 2 Ea. ATI HD3870 video cards, and 3 Ea. WD 500Gb hard drives in raid 0 on a Gigabyte GA-MA-790FX-DQ6 (yea, it's a lot it took a long time to upgrade to). I also have a DLink EBR-2310 router with a DLink DGS-2205 Gigabit Switch connected to a Windstream provided Speedstream 4200 DSL modem (don't get me started about their 2-wire router stuff). At first I requested an AYIYA tunnel over NAT concerns. I do however use static private addresses which comes highly recommended. I had problems though because I wanted to use the GUI AICCU so I tried to install the v801 X64 TAP driver which Win7 promptly rejected as unsigned. I know about booting with unsigned drivers (can you say RAID?)but I didn't want to go through that again. In hindsight I had two options. I could have either went the V901 TAP driver and AICCU console version or request a new Heartbeat tunnel. However, I still like instant gratification so I converted my tunnel to Heartbeat instead since I was static behind my NAT anyway. Now I haven't mentioned yet that I was running ESET AV & firewall. It seems that V4 eats Protocol 41 packets that Heartbeat uses saying there is something wrong with packet length. It also still eats them even when the firewall is disabled. I have seen this documented on the 'net also. I no longer use ESET for that reason (thou shalt not mess with my packets when I disable you). I am currently using AVG which seems to at least pass packets through it. I have learned from this that a ping to www.sixxs.net gets you "general failure" when software is blocking you and other blocking normally gets you "request timed out" (although software can give you this sometimes). Speaking of things learned, if you can get your router to pass Protocol 41 and you have a static private IP behind a NAT, Heartbeat will work if you specify "behind NAT" in AICCU and use "netsh interface ipv6 add v6v4tunnel ...." with the interface name of your choice and the PRIVATE IP and tunnel IPV4 IP. The rest I have seen Win 7 autoconfigure although at times I have had to manually add the IPV6 local address to the interface ("netsh interface ipv6 add address...."). Oh, and before i forget make sure you disable all of the other tunnel stuff (ISATAP, 6to4, & Teredo) either through "netsh" or Device Manager ("netsh" is much nicer removing the devices other than 6to4 which stays but doesn't interfere then) BEFORE installing the v6v4tunnel. I have found out though that the DLink EBR-2310 rev a (with the latest 1.05 firmware) that I have refuses to pass Proto-41 packets even using the DMZ function. I tried the Speedstream 4200 DSL modem in router mode (I normally put it in "bridge" mode) and managed to get it to work on and off but for some reason once I turn the firewall on to pass P-41 packets it stops forwarding DNS calls most of the time (anyone got any ideas?)(although I am loath to trust its router now). So here I sit now with a reluctantly installed v901 TAP driver and the AICCU console waiting for Kredits and approval for a AYIYA tunnel. Remember, multiple tunnels may seem wasteful but may be necessary. (I'm keeping the Heartbeat up in good faith until then). I'm open to suggestions, ideas, and donations (of hardware to experiment with). I'd rather not even try Linksys but beggars can't be choosers. No sense in wasting flames here, since my last job was at a foundry and I can take the heat. 8^P Feel free to ask me anything related to this in the hope it may save you some time and heartache. Bob