There's been other posts about IPv6 and the TL;DR is that while there are shitty implementations everywhere, the USA seems to be ahead of the game of doing it badly, if at all.
That is interesting. I figured they would be something like cloudflare/other redirection for github pages. But the IPv6 address space is github registered.
So, really not sure why they don't have the rest of their site enabled.
But new IPv4 allocations have run out. I've seen ISPs that won the lottery in the 90s/2000s (when the various agencies controlling IP allocations just tossed them around like they were nothing) selling large blocks for big money.
Many ISPs offer only CGNAT, require signing up to the higher speed/more expensive packages to get a real IP, or charge extra on top of the standard package for one. I fully expect this trend to continue.
The non-move to IPv6 is laziness, incompetence, or the sheer fact they can monetize the finite resource of IPv4 addresses and pass the costs onto the consumer. I wonder which it is.
In the USA they charge extra for IPv6? I'm in the UK and while there are some ISPs that don't provide IPv6 at all, and some that do shitty things like dynamic prefixes on IPv6, I've not seen anyone charging for it.
Likewise, server providers generally don't charge for it. In fact, they will often charge less if you don't need IPv4.
github.com doesn't have a AAAA DNS entry. So it's not serving anything directly over IPv6. Likewise, ping -6 github.com fails. So, what are you seeing that is supporting ipv6?
Generally, a device cannot get an internet facing IP address unless something else on your network is advertising the prefix. In fact, I'd argue there's little point using DHCPv6 now. Some devices are only interested in SLAAC. But, if you have a router that gets an IPv6 prefix from your ISP (usually /48 or /64, but you can get other sizes) it will usually then advertise that onto your local network.
As for the IP addresses. I would say that you should definitely still have a firewall in place. But the setup is the same as IPv4 just without NAT. e.g. you set a blanket rule for your prefix to allow outbound and block unrelated inbound. Then poke holes through for specific devices and services.
By default, IPv6 implementations make an assumption that they're not going to be a server (if you want a device to be a server, you can just set a static IP) and their "main" IP will be a random looking one (and the configuration will depend on whether it uses an interface identifier to create the address, or if it is random) within your (usually huge) allocation. But more than that, they will usually be configured to use the IPv6 privacy extensions (RFC4941). This generates extra temporary addresses per device, which are used for outbound connections and do not accept incoming connections. That is, people cannot see your IP address on their host from your connection and then port scan you, since no ports will respond. You could still have ports open on your "real" IP address. But, that one isn't ordinarily used for outgoing connections, so no-one will know it exists. To discover it they would need to scan your whole prefix (remember that the /64 allocation you will generally get is the internet the internet in terms of address space, that is much harder to brute force scan).
I think the differences between IPv4 and IPv6 might seem scary, but most of them are actually improvements on what we had before, making use of the larger pools we have available. Once you work it out, it's really not so bad.
I would like to see routers setup to firewall ipv6 by default to give the same protection as NAT though, meaning users need to poke holes into the firewall for incoming connections. Maybe some do. I know mine did not and it was one of the first things I did.
Yeah. The 7.5 times (or is it 9.5 times, I forget) thing that has been thrown around since the cold war days never rings true to me.
The primary and secondary strikes for both sides will take out people living close to either a military installation or a major city.
Also there's no way even a world war would involve every single country and every single island. There's no way human life would be entirely obliterated. Most us posting here, perhaps. Certainly I'd likely be taken out in the second or third wave (close to London and also close to a military base). But life would go on.
I'm fairly sure it must take extra work to make dynamic prefixes. I've heard some weird justifications about localised routing. But modern ISPs generally don't work that way at all. For example, my ISP has endpoints in multiple cities, and can fail over to another city if need be. All my static IPv4 and IPv6 instantly move with me in that event.
I'm lucky that I have a choice of multiple ISPs all offering service on gigabit symmetric fibre. I've managed to keep my old setup of a /29 IPv4 allocation and /48 IPv6 allocation. But before IPv6 was available, I used tunnels at the point of the router with no problem. As such, the internal network doesn't need to know there's a tunnel and gets native IPv6.
There's literally nothing stopping a moderately skilled IT team from integrating ipv6. You can run any site easily using both. The exceptions are few and even those aren't that hard to deal with.
Source: been running dual ipv4/ipv6 Web servers for over 10 years (maybe 15 would need to check) . Likewise had ipv6 dual stack at home for a similar amount of time, initially using tunnels and then native.
Almost every server provider will give you ipv6 for free. There's really no excuse these days not to run your services on both protocols now.
GPS Navigation didn't become widely available at a decent size until the mid 2000s I would say. I remember for sure I had GPS navigation on a laptop which was just as ridiculous as it sounds in around 2002-2003.
The GPS was a PCMCIA card with an aerial you put near the windscreen. The software would just stop showing a map when you went faster than 50mph or so, and only provide basic instructions and your speed. Buying a laptop charger that plugged into the cigarette lighter socket wasn't as cheap as it is now either.
Needless to say, it was a novelty thing. The main problem with paper map navigation when driving is, you really need to compress the instructions down to something you can remember if driving on your own. Since you need to stop if you lose track of your route. I don't miss that to be honest.
I always saw open source as more socialist than specifically communist. Similar to volunteering in your community. Except the community is the whole world, and you don't need to leave your house. Bonus!
If you're using the ETF as a long term investment and you believe EVs are key to our future then you shouldn't worry about this too much (unless the ETF is made up of mostly TSLA in which case I'd not be too happy).
You've not lost money until you take it out of your investment.
r00ty @ r00ty @kbin.life Posts 2Comments 1,275Joined 2 yr. ago
When people read my code, they usually say they like that I comment so much, it makes it easier to understand what's happening.
I say, I comment so much because my memory is terrible. It's for me!