Re: [RADIATOR] Some information lost during Diameter to Radius conversion

2014-04-01 Thread Arthur
31.03.2014 16:16, Heikki Vatiainen kirjutas: > On 03/31/2014 10:30 AM, Arthur wrote: > >>SDP-Session-Description: VM., v=0 >>SDP-Session-Description: VM., o=- 640284584 403958478 IN IP4 >> 94.50.86.245 >>SDP-Session-Description: VM., s=- >>SDP-Session-Description: VM

Re: [RADIATOR] logging (radiator and authlog) and accounting to ElasticSearch

2014-04-01 Thread Hartmaier Alexander
On 2014-03-28 09:02, Hartmaier Alexander wrote: > On 2014-03-27 20:43, Heikki Vatiainen wrote: >> On 03/27/2014 05:22 PM, Hartmaier Alexander wrote: >> >>> Did you have time to work on this feature? >> We have worked on EAP-SIM, Diameter and other RADIUS functionality, but >> not this. It's still o

Re: [RADIATOR] Some information lost during Diameter to Radius conversion

2014-04-01 Thread Heikki Vatiainen
On 04/01/2014 02:12 PM, Arthur wrote: > One mystery (or bug?) needs explaining, though. > I have the following Diameter request part: Can't really say why you need to use get_attrs. What does your dictionary have for MMT-Information and Calling-Party-Address-Presentation-Status? Thanks, Heikki

Re: [RADIATOR] Some information lost during Diameter to Radius conversion

2014-04-01 Thread Arthur
1.04.2014 17:33, Heikki Vatiainen kirjutas: > On 04/01/2014 02:12 PM, Arthur wrote: > >> One mystery (or bug?) needs explaining, though. >> I have the following Diameter request part: > Can't really say why you need to use get_attrs. What does your > dictionary have for MMT-Information and > Callin

Re: [RADIATOR] Preventing Computer/Machine Authentication in AuthBy NTLM

2014-04-01 Thread Michael Rodrigues
Hi Heikki, Thanks for your input, this mailing list has always been extremely helpful. I attempted to implement your suggestions on items 1 and 2. 1 is straightforward, but I'm still a bit puzzled by 2. I looked at eap_peap and eap_multi in goodies to get an idea of what to do. Using your comm

[RADIATOR] Define a global array

2014-04-01 Thread Steve Phillips
Hi there, I am trying to setup a system that, on startup reads a DB table into a hashed array and then makes this available to the rest of the hooks. A later hook then takes this hashed array and parses it to add a value to a custom attribute which is then used for later processing within a han

Re: [RADIATOR] Define a global array

2014-04-01 Thread Hugh Irvine
Hello Steve - What you describe makes perfect sense - and this is exactly what globals are for. See the hooks in “goodies/hooks.txt” for lots of examples. regards Hugh On 2 Apr 2014, at 10:59, Steve Phillips wrote: > Hi there, > > I am trying to setup a system that, on startup reads a DB

Re: [RADIATOR] Define a global array

2014-04-01 Thread Steve Phillips
Hey Hugh, Yep, had a look through there but can't see how you'd use this to set an array variable, or would &main::setVariable allow you to set a complex variable (a hashed array for example) as opposed to a simple singular variable? I've sort of got this working to set a value based on what w

Re: [RADIATOR] Define a global array

2014-04-01 Thread Steve Phillips
Actually, flag that - I found why it wasn't working and it was me failing at perl. &main::setVariable($varName.$key, $columns{$key}); should have been &main::setVariable($varName . "." . $key, $columns{$key}); -- Steve. On 2/04/2014 11:56 am, Steve Phillips wrote: > Hey Hugh, > > Yep, had a

Re: [RADIATOR] Some information lost during Diameter to Radius conversion

2014-04-01 Thread Heikki Vatiainen
On 04/01/2014 09:52 PM, Arthur wrote: > File diameter_attrs.dat has for those AVP's: Thanks. If you can pass me diamter_attrs.dat and the tcpdump file, I can check what happens. If this is a bug, we'd be very interested to fix it. > Any ideas? May be you need a complete tcpdump for analysing? Y