freeradius and google protocol buffers.
ruslan at shevchenko.kiev.ua
Thu Nov 3 17:35:11 CET 2011
On Tue, Nov 1, 2011 at 4:56 PM, Alan DeKok <aland at deployingradius.com> wrote:
> 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:
> 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.
Just submit pull request with next commit:
>> 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
> Encoding each attribute as an independent message would be best.
Ok, I have rewrote vsa.proto IDL in such style.
>> 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.
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
More information about the Freeradius-Devel