freeradius and google protocol buffers.

[Alan DeKok]

Ruslan Shevchenko wrote:
> 1. I need to organize interaction of freeradius with java-based
> backend, running as web service.
> So,  I wrote small module, which  packed received radius packet into
> google protocol buffer message
> and submit one to web service via persistent http connection:
> https://github.com/rssh/rlm_protobuf

  It looks interesting.

> I want submit this module to freeradius, when It will be mature, but
> not sure: will one be generally useful and
> are you will be happy with 2 new optional dependencies (curl and
> protobuf-c) [?].  If yes -- I will start submit path requests after
> achieving working state.
> (now I assured that requests flow works, but yet not test all possible
> issues with authorization and service restart)

  For submitting it back, fork the main "freeradius-server" repository,
add your code, and send an email.

> 2. Yet one question for community -- it's about how people prefer to
> see representation of radius attributes in protocol buffers IDL.  In
> present 'zero' version all nontrivial attributes are stored as array
> of bytes. In my task this is enough, but potentially such choice can
> cause issues with byte ordering, so may be better to create special
> message types for each type of attribute. So, I will be happy to see
> community opinion: (especially for #define PW_TYPE_ETHERNET  and
> PW_TYPE_IFID)

  Encoding each attribute as an independent message would be best.

> At last, I will be glad to see any feedback about this idea and thanks
> for great software.

  If the module works, use it.

  Alan DeKok.