Re: (RADIATOR) Multiple Items in the same AcctColumnDef
Hi Brian, Probably this is not possible by standard ways of radiator but you can make a preauthhook where you join these to parameters into one (your own) parameter and the log it. Rgds. Toomas Kärner - Original Message - From: "Brian Morris" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 09, 2002 9:38 AM Subject: (RADIATOR) Multiple Items in the same AcctColumnDef > Hi All, > > We receive session info from a few different NAS's but I would like to store > all the connection specific information in a single table element. EG: I > would like to store the Ascend-Disconnect-Cause as well as the standard > Account-Terminate-Cause into the same table column. > > Is this possible to do? If so, what is the syntax for the ACCTCOLUMNDEF > entry? > > Thanks in advance. > > Brian Morris > > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. > === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Multiple Items in the same AcctColumnDef
Thanks Hugh, Just one further question - if one of the NAS's does not return one of the attributes, will it cause an error? Regards, Brian. - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Brian Morris" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, December 09, 2002 6:49 PM Subject: Re: (RADIATOR) Multiple Items in the same AcctColumnDef > > Hello Brian - > > Yes this is possible, simply specify the AcctColumnDef twice. > > Ie: > > . > AcctColumnDef TERMINATECAUSE, Ascend-Disconnect-Cause > AcctColumnDef TERMINATECAUSE, Acct-Terminate-Cause > . > > regards > > Hugh > > > On Monday, Dec 9, 2002, at 18:38 Australia/Melbourne, Brian Morris > wrote: > > > Hi All, > > > > We receive session info from a few different NAS's but I would like to > > store > > all the connection specific information in a single table element. > > EG: I > > would like to store the Ascend-Disconnect-Cause as well as the standard > > Account-Terminate-Cause into the same table column. > > > > Is this possible to do? If so, what is the syntax for the > > ACCTCOLUMNDEF > > entry? > > > > Thanks in advance. > > > > Brian Morris > > > > > > === > > Archive at http://www.open.com.au/archives/radiator/ > > Announcements on [EMAIL PROTECTED] > > To unsubscribe, email '[EMAIL PROTECTED]' with > > 'unsubscribe radiator' in the body of the message. > > > > > > -- > Radiator: the most portable, flexible and configurable RADIUS server > anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. > - > Nets: internetwork inventory and management - graphical, extensible, > flexible with hardware, software, platform and database independence. > === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Multiple Items in the same AcctColumnDef
Hello Brian - Yes this is possible, simply specify the AcctColumnDef twice. Ie: . AcctColumnDef TERMINATECAUSE, Ascend-Disconnect-Cause AcctColumnDef TERMINATECAUSE, Acct-Terminate-Cause . regards Hugh On Monday, Dec 9, 2002, at 18:38 Australia/Melbourne, Brian Morris wrote: Hi All, We receive session info from a few different NAS's but I would like to store all the connection specific information in a single table element. EG: I would like to store the Ascend-Disconnect-Cause as well as the standard Account-Terminate-Cause into the same table column. Is this possible to do? If so, what is the syntax for the ACCTCOLUMNDEF entry? Thanks in advance. Brian Morris === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Multiple Items in the same AcctColumnDef
Hi All, We receive session info from a few different NAS's but I would like to store all the connection specific information in a single table element. EG: I would like to store the Ascend-Disconnect-Cause as well as the standard Account-Terminate-Cause into the same table column. Is this possible to do? If so, what is the syntax for the ACCTCOLUMNDEF entry? Thanks in advance. Brian Morris === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Session database
Hello Ganbold - The answer to this depends on what else you are doing, but you can either use Handlers with a SessionDatabase NULL, or you can use a very large value for the Simultaneous-Use check item (or NULL if you are using an SQL database). regards Hugh On Monday, Dec 9, 2002, at 15:16 Australia/Melbourne, Ganbold wrote: Hi, I have some dial-up users for whom I don't want to use Session Database. How do make radiator not to use Session Database for particular users? TIA, Ganbold === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Session database
Hi, I have some dial-up users for whom I don't want to use Session Database. How do make radiator not to use Session Database for particular users? TIA, Ganbold === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) dictionary and attribute
Hi Hugh, Thanks a lot for replying. Uhhhmmm, may I ask where can I get the Radiator 3.4 dictionaries? By the way, I tried downloading the new version, but unfortunately nobody int he company knows of the username and password for the radiator website to download the latest version. I presume, to get the username and password I need to provide some sort of information that we have the license. Is it possible for you to let me know what information do I have to present to open.com.au to get the username and password to download the latest version of radiator? Regards, Zia |-Original Message- |From: Hugh Irvine [mailto:[EMAIL PROTECTED]] |Sent: Sunday, December 08, 2002 5:12 PM |To: [EMAIL PROTECTED] |Cc: [EMAIL PROTECTED] |Subject: Re: (RADIATOR) dictionary and attribute | | | |Hello Zia - | |Vendor 4874 is Unisphere, vendor 2352 is Redback, and vendor 0 is the |standard RFC numbers. | |I think you will find that almost all (if not all) of these attributes |are defined in the Radiator 3.4 dictionary(s). | |regards | |Hugh | | |On Sunday, Dec 8, 2002, at 01:13 Australia/Melbourne, Ziaur Rahman |wrote: | |> |> Sorry about the prev. mail without subject. |> |> |-Original Message- |> |From: Ziaur Rahman [mailto:[EMAIL PROTECTED]] |> |Sent: Saturday, December 07, 2002 10:12 PM |> |To: [EMAIL PROTECTED] |> |Subject: |> | |> | |> | |> |Hi, |> | |> |I am getting a lot of following ERR in the logs: |> | |> |Sat Dec 7 22:00:40 2002: ERR: Attribute number 24 (vendor 4874) |> |is not defined in your dictionary |> |Sat Dec 7 22:00:40 2002: ERR: Attribute number 143 (vendor 2352) |> |is not defined in your dictionary |> |Sat Dec 7 22:00:40 2002: ERR: Attribute number 142 (vendor 2352) |> |is not defined in your dictionary |> |Sat Dec 7 22:00:41 2002: ERR: Attribute number 55 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:41 2002: ERR: Attribute number 87 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:41 2002: ERR: Attribute number 24 (vendor 4874) |> |is not defined in your dictionary |> |Sat Dec 7 22:00:41 2002: ERR: Attribute number 52 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:41 2002: ERR: Attribute number 53 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:42 2002: ERR: Attribute number 87 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:42 2002: ERR: Attribute number 24 (vendor 4874) |> |is not defined in your dictionary |> |Sat Dec 7 22:00:42 2002: ERR: Attribute number 55 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:42 2002: ERR: Attribute number 87 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:42 2002: ERR: Attribute number 24 (vendor 4874) |> |is not defined in your dictionary |> |Sat Dec 7 22:00:42 2002: ERR: Attribute number 52 (vendor ) is |> |not defined in your dictionary |> |Sat Dec 7 22:00:42 2002: ERR: Attribute number 53 (vendor ) is |> |not defined in your dictionary |> | |> | |> |I can guess from here that the Attribute is not defined in the |> |dictionary, but strange thing is the vendor is null for some ERRs. |> |Can anyone give me a clue, when can it be null? |> | |> |Also, I never used to get these errors even 1/2 weeks back, all of |> |sudden I am getting this. Can I assume safely here that our ADSL |> |line upstream provider's NAS is being updated and those NAS's are |> |sending new VSAs to the radius? |> | |> |What would be the easiest way to upgrade the dictionary? or do I |> |have to find the attributes manually one by one and add it to the |> |dictionary. |> | |> |FYI, our radiator version is way too old: Radiator 2.17.1. (I just |> |joined the company, this version of the radiator was running since |> |2001, *geeezzz*). |> | |> |TIA. |> | |> |Regards, |> | |> |Zia |> === |> Archive at http://www.open.com.au/archives/radiator/ |> Announcements on [EMAIL PROTECTED] |> To unsubscribe, email '[EMAIL PROTECTED]' with |> 'unsubscribe radiator' in the body of the message. |> |> | |-- |Radiator: the most portable, flexible and configurable RADIUS server |anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. |- |Nets: internetwork inventory and management - graphical, extensible, |flexible with hardware, software, platform and database independence. | === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) dictionary and attribute
Hello Zia - Vendor 4874 is Unisphere, vendor 2352 is Redback, and vendor 0 is the standard RFC numbers. I think you will find that almost all (if not all) of these attributes are defined in the Radiator 3.4 dictionary(s). regards Hugh On Sunday, Dec 8, 2002, at 01:13 Australia/Melbourne, Ziaur Rahman wrote: Sorry about the prev. mail without subject. |-Original Message- |From: Ziaur Rahman [mailto:[EMAIL PROTECTED]] |Sent: Saturday, December 07, 2002 10:12 PM |To: [EMAIL PROTECTED] |Subject: | | | |Hi, | |I am getting a lot of following ERR in the logs: | |Sat Dec 7 22:00:40 2002: ERR: Attribute number 24 (vendor 4874) |is not defined in your dictionary |Sat Dec 7 22:00:40 2002: ERR: Attribute number 143 (vendor 2352) |is not defined in your dictionary |Sat Dec 7 22:00:40 2002: ERR: Attribute number 142 (vendor 2352) |is not defined in your dictionary |Sat Dec 7 22:00:41 2002: ERR: Attribute number 55 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:41 2002: ERR: Attribute number 87 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:41 2002: ERR: Attribute number 24 (vendor 4874) |is not defined in your dictionary |Sat Dec 7 22:00:41 2002: ERR: Attribute number 52 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:41 2002: ERR: Attribute number 53 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:42 2002: ERR: Attribute number 87 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:42 2002: ERR: Attribute number 24 (vendor 4874) |is not defined in your dictionary |Sat Dec 7 22:00:42 2002: ERR: Attribute number 55 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:42 2002: ERR: Attribute number 87 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:42 2002: ERR: Attribute number 24 (vendor 4874) |is not defined in your dictionary |Sat Dec 7 22:00:42 2002: ERR: Attribute number 52 (vendor ) is |not defined in your dictionary |Sat Dec 7 22:00:42 2002: ERR: Attribute number 53 (vendor ) is |not defined in your dictionary | | |I can guess from here that the Attribute is not defined in the |dictionary, but strange thing is the vendor is null for some ERRs. |Can anyone give me a clue, when can it be null? | |Also, I never used to get these errors even 1/2 weeks back, all of |sudden I am getting this. Can I assume safely here that our ADSL |line upstream provider's NAS is being updated and those NAS's are |sending new VSAs to the radius? | |What would be the easiest way to upgrade the dictionary? or do I |have to find the attributes manually one by one and add it to the |dictionary. | |FYI, our radiator version is way too old: Radiator 2.17.1. (I just |joined the company, this version of the radiator was running since |2001, *geeezzz*). | |TIA. | |Regards, | |Zia === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
