(RADIATOR)

Hello. I attempt to update to 3.5 from 3.1 and have problem. The handler is not work in 3.5. :-( All packets isn't agree to this handler. I use this for process Access-Request packets. Separately I use for process Accounting-Request packets Is whis bug or new future ? :-) -- Regards,

(RADIATOR) tigris and Accounting-Request

Hi, I got strage problem with radiator 3.5 and tigris with 12.3.1.15 firmware. Tigris is sending me Accounting-Requests with Nas-Reload many times with the same acct-session-id, and after that radiator wants to delete all sessions which belongs to this NAS. I dont know if its tigris bug or feature.

(RADIATOR) MySQL accounting massively slows responses

Title: MySQL accounting massively slows responses We intended to use MySQL for both session databases, IP allocation and accounting; the former two seem to work fine, however as soon as we put accounting onto SQL the Accounting-Response packets take several seconds to be sent. The MySQL connec

Re: (RADIATOR) MySQL accounting massively slows responses

Hello Matthew - It sounds like your accounting table is much too large, causing SQL inserts to take a very long time. In general you should keep the accounting table as small as possible by archiving the older data. You should be able to see what is happening by looking at the database logs. As

Re: (RADIATOR) tigris and Accounting-Request

Hello Adam - This looks very much to me like a NAS bug. If you are not using a session database at all, you can set up the following: # define NULL session database Identifier NULLSDB And you could also set up a special Handler to catch these requests: # define Handler for Accountin

Re: (RADIATOR)

Hello Sergey - I would suggest you do this: The clause will catch everything not processed by the previous Handlers and it will be much faster. regards Hugh On Monday, Mar 31, 2003, at 20:15 Australia/Melbourne, Sergey Y. Afonin wrote: Hello. I attempt to upd

(RADIATOR) FYI: SNMP errors for win32

Hi, Someone else may find this useful. For Win32 environments, we use either net-snmp (v5.0.8) (or ucd-snmp v4.2.3). The errors returned by snmpwalk may be slightly different to that preconfigured in SNMP.pm in Radiator v3.5. For example, instead of "No Response", we get "Timeout". A minor change

Re: Fwd: (RADIATOR) FYI: SNMP errors for win32

Hello Achint, Thanks for letting us know about this. We have added something to the FAQ about the Windows SNMP clients, and patched SNMP.pm to recognise the Timeout error message from those clients. The new version of SNMP.pm is available in the Radiator 3.5 patches area. Thanks again. Cheers.