[RADIATOR] AccountingTable Database Very big

2013-06-28 Thread sergio
Hello list I use mysql database and my AccountingTable has more than 40 million records per month. Does anyone here have any policy purge? I have an extract of CGI access for my users and is very slow because the bank is getting too big. Does anyone have any recommendation what I should do to h

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Heikki Vatiainen
On 06/28/2013 08:41 PM, Johnson, Neil M wrote: > Is there a recommended version of PERL to run Radiator 4.11 on? I'm > running a fairly old version on my windows boxen (Active State 5.12)? I think 5.16 is a good choice. I do not see anything wrong with 5.12 either but for new deployments I'd take

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Heikki Vatiainen
On 06/28/2013 07:56 PM, Mueller, Jason C wrote: > I have currently relented to specifying every individual IP address > that needs to listen for RADIUS across the set of systems running > Radiator (both v4 and v6), and I will just live with the binding > errors when Radiator starts. The reason is

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Johnson, Neil M
Heikki, Is there a recommended version of PERL to run Radiator 4.11 on? I'm running a fairly old version on my windows boxen (Active State 5.12)? Thanks. -Neil -- Neil Johnson Network Engineer The University of Iowa Phone: 319 384-0938 Fax: 319 335-2951 Mobile: 319 540-2081 E-Mail: neil-john...

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Alan Buxey
>The reason is that the Radiator config is managed in a single file that is >pushed to multiple systems to ensure consistency of the config We do the same thing... config created from database and then pushed. Avoids possible human errors that could arise from editing config on several systems

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Mueller, Jason C
Thanks for the information. I am still working on changing the system IPv6 default. I have currently relented to specifying every individual IP address that needs to listen for RADIUS across the set of systems running Radiator (both v4 and v6), and I will just live with the binding errors when R

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Heikki Vatiainen
On 06/28/2013 03:17 PM, Mueller, Jason C wrote: > I am still using ipv6:::, since I have not yet convinced system > administrators to change the bindv6only attribute to 1. > > The example above (which a couple of others also suggested) works for a > single address (i.e., ipv6::::128.255.90.

Re: [RADIATOR] R: digipass PinEnabled

2013-06-28 Thread Heikki Vatiainen
On 06/25/2013 09:19 PM, Fabio Prina wrote: > In any case I'll appreciate your help > All my tokens are "Digipass Go 6" I think your only choice is to see if there is a second file or a folder mentioning nonstatic or something similar in the name. We do not know enough about the dpx file format to

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Mueller, Jason C
Heikki, > When BindAddress is set to ipv6::: and request comes in from an IPv4 > address 172.20.3.170 you'll get this in the logs: > > DEBUG: client_addr: > <0><0><0><0><0><0><0><0><0><0><255><255><172><20><3><170> > > When BindAddress is commented out and defaults to IPv4 0.0.0.0 you'll > get t