[fChk]

Believe or not, I was searching for it too last bight but I couldn't find anything, how did you manage to make it work?

I thought I answered that question (for Linux) when I mentioned the installation of 'miredo'. If you're on Windows, I think it supports the teredo protocol out-of-the-box. You just have to set the server to something that is actually still working (i.e. teredo.remlab.net.) For the specifics on windows, you have to look it up (it may involve tweaking its registry, not sure though.)

If you're on Linux though and still can't get miredo work, just tell us where things fail in that process. The main thing is that when the miredo service is started it will create a pseudo-interface named teredo (you'll find it when you  run the ifconfig or ip -a commands.) That interface will get the dynamic IPv6 that the server will assign it.

Just remember, for as long as that interface is up (ie miredo service is running), you'll no longer be invisible -because of the NAT-, but exposed via that dynamically assigned IPv6 address.

Anyway, I intend to open a thread -when I have time- to document my current understanding of the whole IPv4/IPv6 interoperability (before I forget all that again!)

---

@angelia

You're not being specific for us to be of any help!

For the unresponsiveness of the VPS, that might be due to the Server being overloaded. I've seen a CPU load of up to 135 !!!!! on one of my boxes (the third I've recently created), while the first two generally never exceed 20/30. So, that may be one reason of your issue.

For the Apache Web server, again lack of information, it might be the firewall that you may have forgot to open for 80 and 443, or some misconfiguration in the httpd.conf file; ... or simply the server's CPU reaching the 100s.... Anything goes really without enough information.