Comment by mlhpdx
2 months ago
I’m working on a ground-up implementation of RADIUS with everything running on stateless compute. It’s a beast with many problems to solve but I have EAP-TLS, TTLS and PEAP all working. I’d love to connect with folks interested in this kind of thing.
Why RADIUS and not DIAMETER, the successor?
I didn’t see the successor in the field much, RADIUS seems entrenched. If they are similar enough I may build both but this was the place to start.
What motivated you to start this and which language did you choose?
Past trauma motivated it.
I was responsible for multiple RADIUS services used by millions of people every day. The existing software is slow to build with, difficult to scale and expensive. I couldn't let it go.
Step one was building the platform to run it on and make it sustainable as a business. Step two is implementing protocols like RADIUS that lack a separated compute/storage model but should really have one.
I chose C# because I know it, and build native single-file executables using AoT.
Sort of uncurious about your implementation, but very curious regarding your trauma. I have found a lot of the OSS options for RADIUS suck in specific ways. Never had to scale it however.
1 reply →
So you are looking to offer a managed RADIUS server once you've finished building the software?
1 reply →