HNHacker News
TopNewBestAskShowJobs

welterde

926 karma · joined March 31, 2013

submissionscomments
welterde··on AWS IPv4 Estate Now Worth $4.5B
You can tunnel IPv6 over IPv4 (which is how the very first deployments worked). And I think 6to4/6rd worked pretty to close to what you suggest: Each IPv4 gets assigned a block of IPv6 space which gets tunneled over IPv4.
welterde··on AWS IPv4 Estate Now Worth $4.5B
It's not clear to me how 240/4 would have helped anything. Or how it would have even be different from a tunneling approach on a high level.
welterde··on AWS IPv4 Estate Now Worth $4.5B
The issue is not how can we enable IPv4 C talk to IPv4 S, since that already works. The problem is how would C (ipv4-only) send a packet to S (ipv6-only) in the first place? It doesn't know how to deal with non-ipv4 packets, since it's ipv4-only. Thus if the server does not have a IPv4-address how does a IPv4-client send packets to it?

The inverse situation (IPv6-only client but IPv4-only server) is not really an issue, since for that situation NAT64 works, since you can embed IPv4 addresses into IPv6.

The only way C (ipv4-only) could communicate with S (ipv6-only) is by either allocating a dedicated ipv4-address to S (doesn't have to be directly connected to S - it can be sent to some translation box that does SIIT) or by upgrading C to support ipv6 and tunneling it (6to4, 6rd, teredo, etc.).

welterde··on AWS IPv4 Estate Now Worth $4.5B
It is. A typical enterprise might get allocated a /32, which gives them 32-bit to nicely design their network and give 64-bit to each individual network where devices are connected.

A typical ISP will get allocated a much larger allocation like a /20, which allows them to allocate a /56 for each of their customers while still having a few bits to play with. But all starting with the same <isp_network> prefix.

With IPv4 you will have many separate fragmented networks that have no numbers in common. And this will only get worse over time.

welterde··on AWS IPv4 Estate Now Worth $4.5B
I have yet to read any IPv6 alternative that can theoretically work or is not just IPv6 in disguise (or something that is implemented in IPv6 in a slightly similar fashion).

It may sound like a great plan as long as one doesn't look too closely at the details. IPv4 has fixed 32-bit addresses and one cannot cram more than 32-bit of information into a fixed 32-bit field. But one would need to do that for it to be forward compatible, since how would a IPv4-only client open communications with a expanded address space server?

One idea is to only upgrade the client and server and tunnel the expanded address space packets over IPv4. IPv6 has that - that's how it was bootstrapped before native IPv6 connectivity was a thing.

welterde··on AWS IPv4 Estate Now Worth $4.5B
If one has to go through the pain of changing everything why not make sure one doesn't have to do it again any time soon?

Also having 64-bit for the network address (and 64-bit for the device) does have certain benefits that make it easier to use than shorter addresses in practice for a single entity, since one can hierarchically model the network and do things like <my_network>:<site-id>:<vlan>. So even in absence of DNS one doesn't quite have to remember 128-bit of information for every device.

welterde··on AWS IPv4 Estate Now Worth $4.5B
That document has been going around for ages and is based on the same fundamental misunderstanding that one somehow can extend IPv4 in a way somehow, but remain compatible with IPv4-only clients. This is just not possible.

Most of the other criticism is not relevant anymore, since we now have a lot of transition technologies that allow IPv6 clients to interoperate with IPv4 servers (this way around is possible since IPv6 is a superset of IPv4). Overall we are now much further into the IPv6 migration than djb ever envisioned.

welterde··on AWS IPv4 Estate Now Worth $4.5B
You have to go back further in time and hit the designers of IPv4 on the head for not making it forward compatible.

IPv6 is as backward compatible as is possible within this constraint. You can embed IPv4 space within IPv6, there is NAT64, tunneling IPv6 over IPv4 and many other transition technologies. It's not possible to design a protocol that is any more backwards-compatible.

welterde··on Why does the USA use 110V and UK use 230-240V? (2014)
You are also mistaken about the configuration in Europe, since the 3-phase system has 400V between the different phases and 230V to neutral.
welterde··on Show HN: Halloy – A GUI Application in Rust for IRC
Polari [1] seems to support automatically uploading images and text to some imagebin/pastebin and then posting the link to the channel. The Lounge [2] also supports it (with the files self-hosted in thelounge instance).

[1] https://wiki.gnome.org/Apps/Polari [2] https://thelounge.chat/

welterde··on Lasers enable satellite internet backbone, might remove need for deep-sea cables
Every packet traverses multiple such core routers (most likely from multiple internet providers), so 1 Tbit/s from A to B requires many more Tbit/s of actual hardware capacity sold. Or take the edge capacity of small FTTH providers and you get to quite large theoretical numbers too. Hundreds of Tbit/s easily if one is offering Gbit/s or faster service (my ISP has around 1Tbit/s of equipment installed just to service around a 300m radius of residential homes). Both are true for Starlink as well: In case both source and target are not visible to the same satellite they have to be routed via multiple hops or sent upstream (ground station) to the rest of the internet. The edge capacity (RF up/downlink) boasts insane numbers, but the actual internal backbone is much more limited. For consumer it is less of an issue since they won't mostly fill up that 1Gbit/s service they have, but businesses will absolutely fill that up (so you can oversell much less).

Starlink doesn't have nice overview of actual specs of future satellites, so I can only use what people have figured out or what they have published. But you are right about the number of satellites, I looked at the wrong column (it was for phase 1 and not 3), so density will indeed be much higher, so from that perspective it will be somewhat more capable (depending on fast/slow their rollout is). And it's not clear if it would actually be cheaper for SpaceX to have such customers (since some of the traffic would go to the rest of the internet - requiring ground station resources) or go elsewhere on the planet (filling up inter-satellite capacity), but that's not too much different from how regular ISPs have to plan (some customers are cheaper for them than others).

welterde··on Lasers enable satellite internet backbone, might remove need for deep-sea cables
You are not comparing the same thing here though. If you applied the same theoretical maximum method to all networking hardware (or even just core router class hardware) sold today you would arrive at numbers very very much in excess of a couple Pbit/s.

For it to be really viable as a backbone it would need to be able to do several 100 Gbit/s from one location and that Starlink cannot do (or is built to do). A single satellite has less than 100Gbit/s of RF capacity and you will only have a couple visible above you at any one time. And after that bottleneck comes the inter-satellite link capacity bottleneck which is less than half of that if the information I have found is correct (4 links à 10Gbit/s). I don't think they will be able to sell more than 10 GBit/s service to anyone and that only in not so populated areas.

A single datacenter can reach low Tbit/s of connectivity _alone_ _today_. I don't see how it could make any dent whatsoever in the backbone market.

The other usecases are a different discussion and not as dependent on very high bandwidth numbers.

welterde··on Lasers enable satellite internet backbone, might remove need for deep-sea cables
I was only talking about the currently deployed constellation, which of course is much smaller, but for which we have actual numbers from measurements. For the completed Phase 3 constellation I have read numbers in the range from 1.7 - 2.3 Pbit/s as theoretical maximum. So would need around 8-12 PTX boxes to reach the same total routing capacity as the whole future constellation. The current single-fiber bandwidth record is 1.53 Pbit/s.

And nevermind that Starlink will run out of ground station / inter-satellite link capacity long before reaching the theoretical maximum.

welterde··on Lasers enable satellite internet backbone, might remove need for deep-sea cables
You are underestimating the capacity of modern core routers. A single PTX10016 router could route the entire starlink customer base with no over-subscription at all (230 Tbit/s vs 75 Tbit/s from 50 Mbit/s * 1.5M). Actual estimates of the total capacity of Starlink puts it more in the 20Tbit/s range (and that's without taking into account coverage over less populated areas).
welterde··on The NixOS Foundation’s Call to Action: S3 Costs Require Community Support
Most datacenters offer remote hands, so there is no need to travel to the DC for those kinds of things (just ship them the drives and have them replace it). One can also easily add extra spare hard drives to the pool that ZFS or mdraid can automatically put into production in case of drive failure, so there is no need for active intervention after each drive failure.

And if any downtime for upgrades is unacceptable one can go for distributed storage solutions like ceph, seaweedfs or minio. Or simply 1:1 mirror everything to a second machine (which you want for disaster recovery anyway) and switch over during the maintenance period. And since for this specific usecase the server(s) would only serve as CDN origin, a brief downtime might even have very little actual impact.

welterde··on Thinking about our passive exposure to IPv6 issues
Depending on what you mean exactly with "IPv6 could include IPv4 addresses inside its address scope", IPv6 actually does that.

For applications a subset of the IPv6 address space is set aside for IPv4 connections. So applications only need to support IPv6 and can communicate with IPv4 destinations using ::ffff:<ipv4-address>, so for example ::ffff:8.8.8.8 is a valid ipv6 address. But that still requires the host to have a IPv4 address for this to work (it's only so applications can support both while only requiring support for one address family).

For IPv6 hosts connecting to IPv4 hosts there are different methods that translate IPv6 to IPv4 (NAT64, SIIT, etc.), but most (if not all) just embed the whole IPv4 address space inside IPv6 (and again you can have something like 2001:db8::8.8.8.8) and then translate based on extracting the IPv4 address from the IPv6 address. And in combination with DNS64 you can have ipv6-only hosts that can communicate just fine with IPv4-only hosts (all ipv4 traffic gets routed via NAT64).

The problem is however the inverse. IPv4 is not forward-compatible. A IPv4-only host can only ever form outgoing connections to other IPv4 hosts, since there is no way to put more than 32-bits of information into the 32-bit destination field of the IPv4-packet. You can of course expose certain ipv6-only hosts to the ipv4-internet using for example SIIT, but that requires a 1:1 mapping between the IPv4 and IPv6 host. If you don't have that explicit mapping, how would a gateway know which IPv6 address you meant?

welterde··on LVMH becomes the first European company to surpass $500B in market value
They also have quite a lot of assets though. The shareholder equity is around $190B (for Tesla it's around $45B).
welterde··on I spent a week without IPv4 to understand IPv6 transition mechanisms
Except the devices are still quite well-hidden in IPv6 due to the large address space. Good luck scanning even a single /64 behind a normal home internet connection.

Only way around that is sniffing the communication (say some cloud service that some IoT device connects to) - which would also give you enough information to send your own packets through the NAT/firewall too. Not very feasible for the average attacker and assumes that the device initiates connections in the first place. If it doesn't, good luck finding it remotely.

welterde··on I spent a week without IPv4 to understand IPv6 transition mechanisms
How exactly do you propose this 4 to 6 mechanism to work? How do you fit more than 32-bit of information into the 32-bit destination field of IPv4?

Because that's what's required to make it fully interoperable. Anything else and it's not a pure IPv4 network anymore and you are in the exact same situation as we are with IPv6.

welterde··on I spent a week without IPv4 to understand IPv6 transition mechanisms
The problem is that IPv4 is not forward-compatible and therefore there cannot be a protocol that is entirely interoperable. There can only be ones that are somewhat interoperable. And IPv6 has plenty of mechanisms that make things interoperable (NAT64, embedding ipv4 addresses in ipv6, etc.).
welterde··on X12: Requirements for a successor to the X11 protocol (2013)
One common example is running data analysis/reduction remotely on a big fast box and then looking at the products on that machine via X11 forwarding. On a fast low-latency connection there is hardly any noticeable difference between running the application locally or remotely (it's just another window locally opposed to another window in another desktop in a window).
welterde··on “How America took out the Nord Stream pipeline”
> Also, blowing up your pipeline just as a competitor comes on line? Whatever you think of Hersh's article, it's undeniable that Norway made a lot of money on the sabotage.

Did they though? Looking at the gas futures chart it's not obvious to me at all. The prices suddenly spiked much higher when NS1 was suddenly shutdown. After the explosion they actually went down slightly. They did profit, but just from the actions from the Russian side (which were earlier in time).

As for whatever you mean with competitor coming online. Towards Germany the flows from Norway didn't change that much after the invasion, Europipe II from Norway to Germany was already maxed out since January 2021 pretty much.

welterde··on “How America took out the Nord Stream pipeline”
In that case they still have exactly same leverage as before, since one NS2 pipe is still available and several land-based pipelines are also still online.

My personal belief is that we will never know who actually performed the acts of sabotage. But taking some Biden soundbites, mixing it with some public information and some hand-waving doesn't produce any actual evidence about who actually did it.

welterde··on “How America took out the Nord Stream pipeline”
Russia already had no leverage anymore. Shutting them down was their "all in" move, but that clearly didn't cut it, so no, there was no point anymore. For Russia there were more upsides to this however: Getting out of contracts (since they can only halt deliveries for so long before fines kick in), solidifying internal positions, sending a message (since it happened 1-2 days after the opening of a Norway-Poland pipeline; also it was less than 500m from a sweden-poland undersea electrical cable), sewing chaos in the west. Not that there is any more evidence that they have done it than for the US..

And the rest is all putting the cart in front of the horse. Would it look any different if Russia (or anyone else) were the culprit? No, it wouldn't (since otherwise the fact it's classified itself leaks information). Maybe the investigation just yielded nothing conclusive? Which given the location and event (big explosion and lots of gas output making sure everything gets nicely distributed elsewhere) wouldn't be that surprising?

welterde··on “How America took out the Nord Stream pipeline”
The second string of NS2 is undamaged (but denied operation from the German side). In addition Russia there are several land-based pipelines from Russia to central Europe (only used for small volumes at this point - much below capacity).
welterde··on “How America took out the Nord Stream pipeline”
Neither the mechanism nor the reasoning in the article sound plausible to me (nor the involvement of Norway..). NS1 was already shutdown by Russia within weeks of the supposed time of installation of the explosives, after which there was no more point to explode them and it would make more sense to silently remove them again. NS2 was already dead in the water since couple days before the invasion.

In addition the bad-trigger scenario would imply that the explosives and triggering mechanism remained in place on the remaining pipe, which would require the US to rush there to remove them or trigger the missing one to avoid terrible diplomatic consequences if the unexploded device were to be discovered.

welterde··on “How America took out the Nord Stream pipeline”
NS1 and NS2 are not the only pipelines Russia could be using to export gas to Europe, but there are several land-based ones too. After shutting down NS1 (they claimed equipment issues) they only moved marginal flows (if any) onto those pipelines. Blowing up NS1/NS2 doesn't really change anything here..
welterde··on “How America took out the Nord Stream pipeline”
Why destroy NS1 then and not NS2 (NS1 and NS2 both have two pipes and only one of the two NS2 pipes were destroyed)? And why destroy it at this exact time when Russia was already coming up with less and less plausible excuses to halt deliveries via NS1 (both NS1 pipes were destroyed)? Why not wait with the nuclear option until there were even signs that NS2 would come online (Germany had already halted the certification process for NS2 shortly before the invasion).. NS2 was already dead.
welterde··on Stop the proposal on mass surveillance of the EU
Didn't Lavabit shutdown because of exactly that [1]? So pretty sure the US secret courts can very much force companies to do just that and worse (even require them to be silent about it, which clearly is not the case in Germany).

[1] https://www.theguardian.com/commentisfree/2014/may/20/why-di...

welterde··on First LNG tanker arrives at Germany's new floating terminal
That we cannot know. But what we do know is that Germany pledged delivery of the Iris-T anti-air system (which btw is among the newest systems on the market) back in May and it being delivered in October of last year.

But given that and that Poland initially agreed to the delivery and only afterwards started changing their tune, I don't think the PR angle is that far-fetched?

← PreviousPage 2 of 18Next →