• 0 Posts
  • 180 Comments
Joined 1 year ago
cake
Cake day: April 13th, 2024

help-circle
  • that’s just how they are made.

    Can confirm, even the little training compiler we made at Uni for a subset of Java (Javali) had a backend and frontend.

    I can’t imagine trying to spit out machine code while parsing the input without an intermediary AST stage. It was complicated enough with the proper split.








  • They don’t deserve all this media attention just because they got a lucky birth

    While I agree with you in principle, this guy in particular didn’t have a lucky birth. His parents were not aristocrats, his father is a felon and didn’t stick around, his mother raised him alone at first. His grandparents on the mothers side are divorced and his grandpa is also a felon.

    However when he was four and a half his mother married into the royal house. So he would have had a privileged upbringing from then on. So he’s still super fucked up, to piss it into the wind with violent crime.








  • As @[email protected] says, you can use the same public port for many different destination address, vendors may call it something like “port overloading”.

    I just responded to him on that point, while you were typing to me. I didn’t know this existed, thanks for pointing it out!

    More importantly, you can install a large pool of public address on your CGNAT. For instance if you install a /20 pool, work with a 100 users / public address multiplexing, you can have 400,000 users on that CGNAT. 100 users / address is a comfortable ratio that will not affect most users. 1000 users / address would be pushing it, but I’m sure some ISP will try it.

    Sure, yeah, I have seen a few threads on NANOG about the NAT address ratios people are using. I also think I remember someone saying he was forced to use 1000 and it kind of worked as long as he pulled the heaviest users out of the pool. But if I recall correctly he was also saying he made IPv6 available in parallel to reduce the CGNAT load.

    But the point that made this post ridiculous and an obvious joke is that it said “one address” :-)


  • A TCP session is a unique combination of client IP, client port, server IP, and server port. So you can use the same IP and port as long as the destination is a different IP or port.

    Fair point! I wasn’t aware of any NAT working that way, but they could exist, I agree. It does blow up the session table a bit, but we are taking about a hell of a large theoretical system here anyway, so it’s not impossible.

    This wouldn’t help going to popular destinations, since they have a lot of people going to the same IP address and port, but for many (most?) of them you probably have some sort of CDN servers in your data centers anyway.

    Actually we have recently seen a few content providers not upgrading their cache servers and instead preferring to fall back to our PNIs (which to be fair are plenty fast and have good enough latencies). On the other hand others made new ones available recently. Seems there isn’t a universal best strategy the industry is converging on at the moment.