I've had some hard luck on the hardware front and have taken EXP5 offline while I use it for data recovery. At this point I'm not sure how long that will take.
BOT House is up.
BOT House Twitter feeds have been down for some time. I think they finally fixed that Android hack I've been using to get around their new security policies. It was fun while it lasted.
Anyway, I've been considering getting out of the UT99 business. It's been eight wonderful years, but I don't play as much as I used to and these catastrophic hardware failures are starting to wear thin on my nerves.
Monday, March 21, 2011
Monday, March 07, 2011
"Press any key to access system."
Yeah, I don't believe it either.
You'd think that phrase would show up somewhere on the Web, but Google has never seen it.
Go figure.
It took them a few minutes to get it, but I now have the #2 hit without quotes and the #1 hit with quotes.
So why does this phrase not exist? I at least expected to find it in a user manual for the network device I stumbled on the other day, but no.
I suppose it has something to do with the fact that no manufacturer is his right mind would design "access control" and "user authentication" around the "any key".
It just doesn't happen.
You'd think that phrase would show up somewhere on the Web, but Google has never seen it.
Go figure.
It took them a few minutes to get it, but I now have the #2 hit without quotes and the #1 hit with quotes.
So why does this phrase not exist? I at least expected to find it in a user manual for the network device I stumbled on the other day, but no.
I suppose it has something to do with the fact that no manufacturer is his right mind would design "access control" and "user authentication" around the "any key".
It just doesn't happen.
Wednesday, February 23, 2011
IPv6 @ DinkNet
Since the IPv4 address pool ran dry this month I decided it was high time I started practicing what I've been preaching for these last seven years and get DinkNet ready for World IPv6 Day on June 8th. Having dealt with the brain-dead technical support folks at my ISP too many times (once) in the past, I knew that wasn't the route to go, so I logged on to Hurricane Electric's IPv6 tunnelbroker site and signed up.
Now, all the boxes on my wired network have globally routeable IPv6 addresses.
No more stinking NAT.
All my IPv6 traffic leaves the DinkNet wrapped in my ISP's IPv4 packets (6in4, not 6to4) and travels to Hurricane's IPv6 NOC in California, from which it goes wherever on the world wide IPv6 network, and back again.
Unfortunately I'm stuck on this end with some IPv4-only junk that's gotta go. The proxy, SQUID 2.x, doesn't do IPv6. My wireless access point (not a wireless router) is a dinosaur. My DNS, on Windows 2003, isn't going to hack it, which is yet another nail in the Windows coffin I've been constructing.
Luckily, upgrading SQUID to 3.1.11 fixed the other two problems. Wireless IPv4 clients can get IPv6 content just by using the proxy and since it does the DNS lookups on behalf of the clients that fixes the Windows DNS problem. IPv6-only clients can get IPv4 content as well.
And, with the addition of an IPv6 router advertising daemon (radvd), DHCP and all its headaches are out the fucking door, baby! All the IPv6-aware clients, including kludgy old Windows XP, self-configure and pick up their own globally-routable IPv6 addresses.
World IPv6 Day, get ready for Hinky!
Now, all the boxes on my wired network have globally routeable IPv6 addresses.
No more stinking NAT.
All my IPv6 traffic leaves the DinkNet wrapped in my ISP's IPv4 packets (6in4, not 6to4) and travels to Hurricane's IPv6 NOC in California, from which it goes wherever on the world wide IPv6 network, and back again.
Unfortunately I'm stuck on this end with some IPv4-only junk that's gotta go. The proxy, SQUID 2.x, doesn't do IPv6. My wireless access point (not a wireless router) is a dinosaur. My DNS, on Windows 2003, isn't going to hack it, which is yet another nail in the Windows coffin I've been constructing.
Luckily, upgrading SQUID to 3.1.11 fixed the other two problems. Wireless IPv4 clients can get IPv6 content just by using the proxy and since it does the DNS lookups on behalf of the clients that fixes the Windows DNS problem. IPv6-only clients can get IPv4 content as well.
And, with the addition of an IPv6 router advertising daemon (radvd), DHCP and all its headaches are out the fucking door, baby! All the IPv6-aware clients, including kludgy old Windows XP, self-configure and pick up their own globally-routable IPv6 addresses.
World IPv6 Day, get ready for Hinky!
Subscribe to:
Posts (Atom)