While it's technically possible to build a NAT gateway that allows IPv4-only clients to access IPv6 servers, it would be a rather messy blob of state tracking and fake IPs. You're better off deploying IPv4 NAT alongside native IPv6. If a customer doesn't have IPv6-capable equipment, then they'll still be able to access most of the webby stuff for years to come, since anyone running a server of consequence will have IPv4.
IPv4 NAT will impede P2P networking, but if the customer really wants that, they can upgrade to some IPv6-compatible equipment.
IPv4 depletion was a looming problem in 2005, and today it's an even more closely-looming problem. It's not like we discovered more numbers since then.
But what if you have a fancy cesium clock, and one day your datacenter accelerates to near the speed of light and returns to its original location? With GPS, you at least know that your time is synchronized with all the other systems using GPS.
The GPS satellites all have synchronized atomic clocks on board. If your GPS receiver also had an atomic clock, then the distance to each satellite could be computed by subtracting the times and multiplying by the speed of light. So, with 3 satellites, you could calculate your location.
However, GPS receivers are cheap, and don't have atomic clocks. But if you get a signal from *four* satellites, then you can use the redundant information to deduce the correct time, and then use that time to find your location.
I don't have a specific model to recommend, but pretty much all the most powerful routers today are on the Atheros ar71xx platform. Atheros is much better than Broadcom at supporting open drivers.
Windows automatically assigns a 6to4 address if you have a public IPv4 address. Unless you're getting an address from Comcast's IPv6 block, there's nothing notable going on here.
Is this just the 4th-generation iPhone, or will it operate on 4G LTE/WiMAX networks?
Apple really seeded confusion when they called their second-generation device the "3G", but got back in sync by calling their third-gen device the "3GS". If their 4th-gen device doesn't have 4G wireless, it'll be a mess again.
You know that every IPv4 address is by definition also an IPv6 address as in::127.0.0.1?
That's sort of true, but it doesn't really mean anything. You could use that format to store an IPv4 address locally in an IPv6 data structure, but if you try to put that on the wire, nothing will understand it in any useful way.
The problem with Ubuntu is that their patched version of glibc always asks for AAAA records when IPv6 is enabled, regardless of whether the machine has an IPv6 route. Then when a client attempts to connect to an IPv6 host, it times out almost instantly because the kernel reports the lack of route. But that timeout isn't the problem.
The real problem is in the AAAA DNS query itself. This can go wrong in a few ways:
1) The authoritative DNS server is misconfigured, such that it completely drops AAAA queries. The user experiences a long delay connecting to these hostnames. 2) The authoritative DNS server has empty AAAA responses without any TTL field, so the respone is not cacheable. This includes slashdot. If you "dig AAAA www.slashdot.org" repeatedly, you will never see an instant cached response, because the record doesn't have a TTL. 3) The user's router has a poorly-written DNS proxy, such that it drops AAAA queries. This causes a long delay for *every* hostname.
These problems will affect any user with real IPv6 connectivity, but they especially affect Ubuntu because it always asks for AAAA records, even on an IPv4-only connection. I haven't checked within the last couple months to see if they ever fixed the problem.
The reason it's a somewhat difficult problem to fix is that completely disabling AAAA also disables literals, like [::1], and IPv6 entries in the/etc/hosts file, like localhost. They could fix the problem by only allowing *local* AAAA queries when the machine has no IPv6 route, but even if they did that, all the problems would resurface once the machine gets a real IPv6 connection.
You're confusing symmetric with asymmetric encryption. 128 bits is still pretty good for a symmetric key (like AES), while 2048 bits is pretty good for an asymmetric key (like RSA).
Slashdot Mirror
Are you sure about that? Their website says $40 for 1GB, $60 for 5GB:
http://www.virginmobileusa.com/mobile-broadband
T-mobile has a data-only SIM for $40/month with a $35 activation fee. They claim "No overages! (After 5 GB, data speeds may be reduced)."
http://www.t-mobile.com/shop/plans/cell-phone-plans-detail.aspx?tp=tb1&rateplan=Even-More-Plus-webConnect-Overage-Free
Google already has a 45-degree bird's eye view in some areas. Switch to satellite view and zoom into their Mountain View headquarters, for example.
While it's technically possible to build a NAT gateway that allows IPv4-only clients to access IPv6 servers, it would be a rather messy blob of state tracking and fake IPs. You're better off deploying IPv4 NAT alongside native IPv6. If a customer doesn't have IPv6-capable equipment, then they'll still be able to access most of the webby stuff for years to come, since anyone running a server of consequence will have IPv4.
IPv4 NAT will impede P2P networking, but if the customer really wants that, they can upgrade to some IPv6-compatible equipment.
IPv4 addresses are globally unique too. That's why we're running out of them.
Building an ISP with dark fiber is easy! Just set up millions of tiny apartments inside the Internet Exchange buildings, and get some cat5.
IPv4 depletion was a looming problem in 2005, and today it's an even more closely-looming problem. It's not like we discovered more numbers since then.
But what if you have a fancy cesium clock, and one day your datacenter accelerates to near the speed of light and returns to its original location? With GPS, you at least know that your time is synchronized with all the other systems using GPS.
The GPS satellites all have synchronized atomic clocks on board. If your GPS receiver also had an atomic clock, then the distance to each satellite could be computed by subtracting the times and multiplying by the speed of light. So, with 3 satellites, you could calculate your location.
However, GPS receivers are cheap, and don't have atomic clocks. But if you get a signal from *four* satellites, then you can use the redundant information to deduce the correct time, and then use that time to find your location.
Hell, it can't be worse than "Flash". Flash means everything.
I don't have a specific model to recommend, but pretty much all the most powerful routers today are on the Atheros ar71xx platform. Atheros is much better than Broadcom at supporting open drivers.
https://dev.openwrt.org/wiki/ar71xx
Windows automatically assigns a 6to4 address if you have a public IPv4 address. Unless you're getting an address from Comcast's IPv6 block, there's nothing notable going on here.
From everything I've seen, they're not providing IPv6, they're talking about providing IPv6 later this year. Do you have any evidence to the contrary?
That site's been dead for years. Not that it was ever alive in the first place.
Is this just the 4th-generation iPhone, or will it operate on 4G LTE/WiMAX networks?
Apple really seeded confusion when they called their second-generation device the "3G", but got back in sync by calling their third-gen device the "3GS". If their 4th-gen device doesn't have 4G wireless, it'll be a mess again.
Doesn't Shoutcast use MP3? That's certainly not optimized for low-bitrate voice.
You know that every IPv4 address is by definition also an IPv6 address as in ::127.0.0.1?
That's sort of true, but it doesn't really mean anything. You could use that format to store an IPv4 address locally in an IPv6 data structure, but if you try to put that on the wire, nothing will understand it in any useful way.
74.82.42.42
The problem with Ubuntu is that their patched version of glibc always asks for AAAA records when IPv6 is enabled, regardless of whether the machine has an IPv6 route. Then when a client attempts to connect to an IPv6 host, it times out almost instantly because the kernel reports the lack of route. But that timeout isn't the problem.
The real problem is in the AAAA DNS query itself. This can go wrong in a few ways:
1) The authoritative DNS server is misconfigured, such that it completely drops AAAA queries. The user experiences a long delay connecting to these hostnames.
2) The authoritative DNS server has empty AAAA responses without any TTL field, so the respone is not cacheable. This includes slashdot. If you "dig AAAA www.slashdot.org" repeatedly, you will never see an instant cached response, because the record doesn't have a TTL.
3) The user's router has a poorly-written DNS proxy, such that it drops AAAA queries. This causes a long delay for *every* hostname.
These problems will affect any user with real IPv6 connectivity, but they especially affect Ubuntu because it always asks for AAAA records, even on an IPv4-only connection. I haven't checked within the last couple months to see if they ever fixed the problem.
The reason it's a somewhat difficult problem to fix is that completely disabling AAAA also disables literals, like [::1], and IPv6 entries in the /etc/hosts file, like localhost. They could fix the problem by only allowing *local* AAAA queries when the machine has no IPv6 route, but even if they did that, all the problems would resurface once the machine gets a real IPv6 connection.
Wait, sorry, that should be:
$ chromium-bin --no-sandbox --enable-webgl
Although the --no-sandbox flag seems to have no effect here. Perhaps Chromium's sandboxing doesn't support my Gentoo configuration yet.
WebGL works on Linux. For Chromium, you need to launch:
$ chromium-bin --disable-sandbox --enable-webgl
And view some demos: http://www.khronos.org/webgl/wiki/Demo_Repository
There's no point in having ANGLE on Linux, because Linux already has OpenGL support in most drivers.
It was deemed newsworthy because:
1. There's a video.
2. A girl made it.
You're confusing symmetric with asymmetric encryption. 128 bits is still pretty good for a symmetric key (like AES), while 2048 bits is pretty good for an asymmetric key (like RSA).
But we won't nee... ohhh.
AES support is mandatory for WPA2 devices. If it doesn't support AES, it doesn't have WPA2.