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.

8 comments

mlhpdx

Reply
pabs3  2 months ago

Why RADIUS and not DIAMETER, the successor?

  • mlhpdx  2 months ago

    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.

MaKey  2 months ago

What motivated you to start this and which language did you choose?

  • mlhpdx  2 months ago

    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.

    • protocolture  2 months ago

      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 →