[RADIATOR] radpwtst changes from v4.9 to v.14 (or Starent atributes?)

2015-02-13 Thread Bruno Tiago Rodrigues
Hi everyone We've been running v4.9 on some of our production systems for quite a while now. The authentication instance is receiving packets from a Starent device forwarded to a Radiator instance on 4.9 and the authentication packet I get on my side looks something like this: Code: Access

Re: [RADIATOR] radpwtst changes from v4.9 to v.14 (or Starent atributes?)

2015-02-16 Thread Heikki Vatiainen
On 13.2.2015 17.59, Bruno Tiago Rodrigues wrote: > By changing the vendorByNum function at RDict.pm we managed to get it > working, but it doesn't feel right to be changing the code for something > that oughta be backwards compatible. You are correct, that change should not be needed. For example

Re: [RADIATOR] radpwtst changes from v4.9 to v.14 (or Starent atributes?)

2015-02-16 Thread Heikki Vatiainen
On 02/16/2015 04:55 PM, Heikki Vatiainen wrote: > I tried replicating the problem but could not get it to fail. Can you > make sure you are using a radpwtst from Radiator 4.14? Also, check that you are using dictionary that includes this line: VENDORStarent8164format=2,2 If the lin

Re: [RADIATOR] radpwtst changes from v4.9 to v.14 (or Starent atributes?)

2015-02-17 Thread Bruno Tiago Rodrigues
Hi Heikki Thanks for the help. We were indeed using radpwtst from 4.14, the host was a fresh install, dedicated to Radiator, nothing else besides perl dependencies had been installed. Anyway, by adding the "VENDOR Starent 8164 format=2,2" line to the dictionary file we had been using ever since

Re: [RADIATOR] radpwtst changes from v4.9 to v.14 (or Starent atributes?)

2015-02-17 Thread Heikki Vatiainen
On 02/17/2015 01:00 PM, Bruno Tiago Rodrigues wrote: > Anyway, by adding the "VENDOR Starent 8164 format=2,2" line to the > dictionary file we had been using ever since fixed the issue. > The servers were migrated yesterday and everything is running smoothly. Thanks for the update. I think we'll