Re: "acts of God"
I like to use "acts of Gods". Also, whenever anyone says "For Gods' sakes!", I compliment them on their catholicism (small "c").
2662 publicly visible posts • joined 8 Nov 2007
Induced electrical fields, winding numbers, inverse square law, ... thinking of things from the squirrel's point of view, a minor hair-raising incident followed by a slightly-painful static discharge is probably going to be enough to induce a kind of negative magnetism against the HV air gap that was going to be its original LZ. Like an RFID bug zapper.
The Japanese also beat the Americans in their first semi-official baseball game, IIRC. Not that I was around to remember it, mind. It was (according to the net) back in 1896. The Samurai Champloo episode entitled "Baseball Blues" seems to conflate this match with the actual introduction of baseball by Perry's Black Ships in the run up to the Meiji Restoration period. でもさ、この番組は時代錯誤がたくさんあるよね。
> France Telecom - managed to get assigned a /19 of IPv6 address space
Unlike IPv4 addresses, IPv6 allocations aren't "owned". FT would presumably have to show that they're actually using their allocation or some of it would be taken back. In theory, anyway, that's how it works. I'm not sure what justification they had for a /19, though...
> And there are more than 65,536 autonomous systems
Not sure what you mean by "autonomous system".
would almost certainly have had a direct mapping from the public IPv4 addresses to a (tiny) subset of the IPv6 addresses. If that had been the case then IPv6 would have been in widespread use years ago.
This is also in reply to the first poster above...
One of the goals of IPv6 was to make things easier for the routing system. Basically, the address space is carved out hierarchically with a top-level address registrar feeding down through RIRs (regional IP? registries) and so on down to local resellers and eventually users. It is assumed that the mainly geographical hierarchy will match up more or less with the actual routing infrastructure at at least the higher levels. Ultimately, the aim is to shrink the routing tables down.
IPv4 is decidedly not based on a geographical hierarchy. If you try and graft IPv4 addresses into the IPv6 system, you end up with an explosion of routing table entries that need to be taken care of. So no matter how you try to devise an IPv4 to IPv6 transition mechanism, if it involves a 1:1 mapping of old to new addresses in any way, you effectively break routing (or at least negate IPv6's native advantage there), and thus pretty much break IPv6 for everyone.
At least that's what struck me when reading the article.
Canonical never knows you opted out and you've lost your chance to let the Ubuntu-maker know you didn't like the data collection.''
I'm sorry. Can you explain that? You seem to be saying that if you opt out, a message is sent to Canonical saying that you have opted out.
So either your reporting/logic here is wrong, or you are saying that the package is reporting your opt-out status to Canonical, despite you clicking the box that says you don't want to share anything.
Which is it?
Why did they have to completely redesign the protocol for IPv6? All that we needed was a few more bits for the address fields
Well, for a starter, adding a few extra bits (bytes) to the address field will break things. If you're going to break things, it's better to engineer something new and completely incompatible rather than just using a sticking plaster approach.
before opening a huge security hole into a home or office
NAT is not security, especially given that uPNP NAT traversal exists. Also, you're not going to run IPv6 without firewall rules on your router, are you? And anyway, I'd wager that most security problems don't come from attacks from outside the network but from numpties inside it.
Instead with IPv6 we have wacky huge address fields
Which, if (as you should) you assign addresses randomly, improves your protection against network mapping and hence port scanning, even if you do accidentally forget to do ingress filtering. You can't scan what you can't find, and /64 is plenty big of a space to hide a few hundred machines in.
massive /64 allocations to small businesses as standard
A /64 allocation is for a LAN. Actual allocations to businesses would be larger, like a /48, so you can have up to 65535 LANs.
Why did they have to completely redesign the protocol for IPv6?
Coming back to the first point, although I'm not sure about how well this works right now, IPv6 also has features for device mobility. So new protocols open up the possibility of new ways of working.
If you're on Linux, add the 'privext 2' option to your interfaces(5) file for any network interface that will have an IPv6 address. This makes the MAC-based address local in scope, so it won't appear over the net. Addresses derived from MAC addresses are also easy to block at your router since they follow a standard pattern (with ff:fe stuck in the middle), so even if you misconfigure some machines, they won't be allowed to leak their MAC address to the outside.
Why should they; nobody wants, needs or uses IPv6.
Well, I'll answer the wants/needs part of that. Say you're stuck with a bog-standard "home" level broadband connection. You're stuck behind a NAT along with quite a few other home users. You decide that you want to put an FTP service up so that your aunts can see all the old photos that you've been digitising. Or some other such service (like email) that you want to self-host. You go to your ISP and ask them to open up a certain port and forward it to the right machine in your DMZ. What do they say? They say "sod off", followed by "unless you upgrade to a business package"...
... Too many mind-altering substances whilst hiding out in the Latin American jungle? The man is seriously deranged...
... And the SEC is far behind / Down in the Swamp / With the Gators and Flamingos / A long way from Lichtenstein / I'm a Junk-bond King playing Seminole Bingo
https://www.youtube.com/watch?v=mbNhWbeP-k0
Article didn't mention socket type. A quick check on Wikipedia tells me that these aren't a drop-in replacement for previous-gen AMD CPU/APU jobbies (FM2+ → AM4).
Yeah, I know, I'm a little behind the curve on this one...
Astrophysics has never been my forte. The time periods are too, well, astronomical. I've decided instead to invest in forestry. Granted, even there, I may not live to personally see the benefits. Still, as they say, "die young and leave a beautiful copse.".