For some reason, Microsoft mixed up how the interface identifier should be created even though Microsoft engineers helped write RFC 4941. Be that as it may, you can force Windows 7 to use the correct method by issuing the following command from a DOS prompt:
netsh interface ipv6 set global randomizeidentifiers=disabled
— http://itexpertvoice.com/home/troubleshooting-ipv6-on-windows-7-and-why-its-worth-the-bother/“Test your IPv6 connectivity” score at home:
10/10 for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
10/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only
- was missing an IPv6 resolver. Happier now :-)
“Test your IPv6 connectivity” score at home:
10/10 for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
9/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only
- Yay!
“Test your IPv6 connectivity” score at work:
7/10 for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
0/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only
- Boo!
The Thawte SSL Installation Checker - requires Java and doesn;t seem to show up at all in Google, but at least it works.
smtp.gmail.com some.user@gmail.com:PASSWORD
We’ve recently received an iLamp for our “museum of old tech” in the office. Got RAM upgrades for it, and I’m pretty sure we can bung Leopard on and make it live again (at least for a few months until Apple bring out 10.7 and kill off support for 10.5).
Denied hosts since August 2009
I’ve been running a virtual server from bitfolk since the middle of August. To keep it snug and safe, it’s running denyhosts because port 22 is exposed to the Internet. Had a quick look this morning (October 20 2009) to see what it’s caught:
jmi@heavy-lifting:/etc$ cat hosts.deny | grep sshd | wc -l
337
Sigh…
