Hacker News Reader

Comment by justinsaccount | Hacker News Reader

That's pretty amazing. I've been keeping my on this stuff since it seems one of the few simple PaaS that give you access to tcp sockets.

tons of PaaS providers are no help at all if you want to run an app that uses ZeroMQ or basically anything that isn't http.

One super small nitpick though, and maybe it's just me, but

> Technically, what we end up delegating to each instance is a /112, which is the IPv6 equivalent of an IPv4 Class B address

> WireGuard peers get /120 delegations (the equivalent of an IPv4 class C)

Should be

> Technically, what we end up delegating to each instance is a /112, which is the IPv6 equivalent of an IPv4 /16 network.

> WireGuard peers get /120 delegations (the equivalent of an IPv4 /24)

classes haven't really been a thing for almost 30 years.

View on HN

I thought about that, and just thought it read better the other way, but also I'm the oldest 40-something on Hacker News so "class C" and "class B" might just be more vivid for me than for normal people.

If there is something with a socket of any sort that you can't do on Fly, I'd like to know about it, so I can make Kurt write some BPF code for a change.

In the spirit of nitpicking, class A, B, and C referred to specific address blocks, not network sizes. A /24 in the class A range was still class A rather than class C.

I worked on network/firewall at a rather large bank from 2009-2019 and we used the class labels and "slash 24s" etc. interchangeably when talking. Not that you're incorrect, but that the slang was used and everyone knew what people meant by it.

See, I had no idea. This is the best kind of nitpicking.

Look up CIDR on Wikipedia, which is what we use now and you know it already, but more so to learn the difference from the old classful networking.

Then you'll never use "Class A/B/C" again. :) It's correct to just say /24 while Class C isn't, because it has a more specific but outdated meaning.

I'm familiar with CIDR, I just always understood it to mean "arbitrary prefix lengths, not just on byte boundaries".

>but also I'm the oldest 40-something on Hacker News so

Soo...Happy 50th birthday? (all the 49.9999 year olds will get this joke...)

Last I looked, I can't receive SMTP on Fly. But that sounds more like a policy decision.

> You can configure an application to listen for global traffic on ports 80, 443, 5000, and ports 10000 - 10100.

https://fly.io/docs/reference/configuration/#services-ports

Fair enough :)

If I were to run a container that handled tcp connections, is there any sort of max connection duration?

One of the projects I have worked on involved accepting tcp connections from cellular connected race timing boxes, dealing with their protocol and sending the resulting data into another system.

I guess you could think along the lines of syslog or MQTT.

This isn't very bandwidth or CPU intensive, but does require keeping the sockets open for hours at a time.

This has come up before! If you like, you can hit me up at thomas@fly.io and I can take a whack at telling you how well this'll work out-of-the-box. What I can say is that "ordinary" TCP connections at Fly run through our Anycast proxy infrastructure, which does expect that it can bounce connections whenever it needs to --- but we can route around that for long-term connections, which is a thing that people doing, for instance, WebRTC want.

Cool! With covid I haven't had the chance to work on any races lately, so I don't have an immediate need for this right now.

heroku/app engine/lambda/cloud run all replace CGI in one way or another, but none of them can replace inetd.

GCP PaaS stuff allows gRPC and WebSockets but that's it from what I've seen.

You might want to have a look at Cloud 66 as well. It’s like a PaaS but on your own cloud / servers so you get full control.

Reply on news.ycombinator.com