Ipv4 is not even ipv4 compatible. You use nat to translate one type of ipv4 into another to talk on the internet. Ipv6 is using nat in the same way.
The problem is that ipv4 is not forward compatible ( naturally ). So ipv6 can talk to both, ipv4 only to ipv4.

That must have been a concerted effort. The amount of anti-mozilla posts and comments that totaly permeated everything for a short while, was very suspicious.

I install molly-guard on important machines for this reason. So fast to do a reboot on the wrong ssh session

Everybody knew exactly what kilo mega and giga ment. when drive vendors deliberatly lied on there pdf’s about their drive sizes. Warnings were issued: this drive will not work in a raid as a replacement for same size!!. And everybody was throwing fumes on mailinglists about the bullshit situation.

But money won, as usual.

Source: threw fumes!

Thanks. Especialy for the graphs. My browser did not like the site!.

People have experience.

The probably did at the time. There must be something in the water, or after effects of leaded gasoline, or something.
I am from norway so I only see this slow train wreck from the sidelines, but how the heck else can that wierd clown DT have a cult of personality. It boggles the mind.

It is grief. Perfectly natural in those circumstances. Very similar to people loosing their parents to dementia or ALS.

Total cookie protection can have site breakage, even for very casual users. And it is enabled by default. That beeing said it is easy to stop for a site. And quite rare. Total cookie protection is a very nice fix for the cookie tracking issue imho.

That they are miles better then the competition, does not mean there are no room for improvements.

Steam is the only store putting the customer first. The refund policy is top notch. Heck just making proton, giving gamers the choice of os, is the best thing for gamers since computers was invented!

https://youtu.be/gwoAmifo9r0

Insane!! So… where is this drawing?

2 weeks! It is 3 months in norway for most work. This is mutual so it works both ways.
Seasonal/contract work is different tho, they know the start and end date when signing.

You have my sympathy. I do not know of a sure way to get isp’s to behave. Espesially not if they have regional monopoly

Thank you! :) I also notice i compleatly forgot the port exhaustion issue we see with larger networks behind roo few ipv4 NAT addresses…

I guess I am lucky. 3 out of 3 isp’s available from in my region provide IPv6 with a dhcp-pd assigned stable address by default. (Norway)

If there is a ipv6 service online. That you want to reach from a v4 only client. You can set up a fixed 1:1 nat on your firewall where you define a fake internal ipv4 address -> destination NAT onto the public ipv6 address of the service. And SRC NAT64 embed your clients internal v4 into the source ipv6 for the return traffic. And provide a internal dns view A record pointing to the fake internal ip record. It would work, but does not scale very well. Since you would have to set this up for every ipv6 ip.

A better solution would be to use a dualstack SOCKS5 proxy with dns forwarding where the client would use the IPv6 of the proxy for the connection. But that does not use NAT tho.

The best solution is to deploy IPv6 ofcourse. ;)

That is not how it works. You can have a home network on ipv6. And it can reach all of ipv4 via nat ( just like ipv4 do today). A net with only ipv4 can not reach any ipv6 without a proxy that terminst the v4 connection and make a new v6 connection. since ipv6 is backwards compatible. But ipv4 is naturally not forwards compatible.

Also it is the default deny of the stateful firewall that always coexist with NAT, since NAT depends on that state, that is the security in a NAT router.
That default deny is not in any way dependant on the NAT part.

But DNS rarely break. The meme about it beeing DNS’s fault is more often then not just a symptom of the complexity of IPv4 NAT problem.

If i should guesstimate i think atleast 95% of the dns issues i have ever seen, are just confusion of what dns views they are in. confusion of inside and outside nat records. And forgetting to configure the inside when doing the outside or vice verca. DNS is very robust and stable when you can get rid of that complexity.

That beeing said, there are people that insist on obscurity beeing security (sigh) and want to keep doing dns views when using IPv6. But even then things are much easier when the result would be the same in either view.

I assume the normal fear of unknown things. It is hard to hate ipv6 once you have equivalent competence in ipv4 and ipv6.