Hello Sven -
What you describe below is exactly what we need to know to be able to
code the NasType.
Unfortunately, we do not have *any* NAS gear (suppliers don't give us
anything for development), so we have to rely on customers such as
yourself to get the information that is required.
BTW - even with Cisco it is not easy because of (vast) differences in
IOS versions and configuration differences.
regards
Hugh
On Friday, August 2, 2002, at 05:49 PM, Sven Holz wrote:
> On Fri, 2 Aug 2002, Hugh Irvine wrote:
>
>>
>> Hello Sven -
>>
>> There are many readers of this list who use Redback equipment, and
>> there
>> are people at Redback on this list as well.
>
> Well, thats really nice, cause many locations I asked for the snmp
> features gave back a not so well statement for Redbacks SMS. I just
> thought there could not be many providers who use this kind of hardware
> :o) And the standart answer was "use cisco"... :o(
>
>>
>> Radiator maintains one or more session databases (in memory, SQL,
>> DBM, ...) and tries to keep track of current sessions by using the
>> accounting starts to add records and accounting stops (and access
>> requests) to delete records.
>>
>> The NAS itself is only contacted if Radiator detects what it thinks
>> is a
>> simultaneous-use exception, and then only if the NasType parameter is
>> set in the corresponding Client clause(s). In this situation, Radiator
>> goes through the list of sessions for the particular user and queries
>> the NAS(s) to verify that the sessions are still active. If any session
>> has gone away, that record in the session database is deleted and the
>> connection is allowed to proceed. If on the other hand, all the
>> sessions
>> are still active, then the connection is rejected.
>
> Yeah I know but the prob I got is that our sms500 replys to a snmpwalk
> with not many informations and especially not with session information.
> So the question was will I be able to get this in general with one of
> the
> perl scripts or not.
>
> To the Prob with the missing informations I talked to our supporter at
> Redback and I hope we will solve it in the next days.
>
> I didn't found one for redback so I think I`ve to change for example the
> cisco one for my requirements?
>
> But I'm also interested on what kind of data the session is identified
> on
> the NAS? There must be a special tree with maybe information on active
> ports with special address (mac/ip) given by the dedicated session or
> not?
> So i did a snmpwalk on a portmaster an i couldn`t find any data that
> could
> be needfull.
> I know that der sms knows about the UID that is got a session but in
> case
> of missing a well running snmp-agent on our sms I don't know if this
> information will normally be reported via snmp...
>
>> You will find the mechanisms used to query the different NasTypes in
>> section 6.5.5 of the Radiator 3.1 reference manual ("doc/ref.html") and
>> you will find the corresponding code in the "Radius/Nas" directory.
>
> I still found them but see upper text and by the way, redback is not in
> list so I was not sure... :-)
>
> So thanx a lot
>
> with kind regards || Mit freundlichen Gruessen
>
> Sven Holz
>
>
> --
> Sven Holz - IP-Services - WOBCOM GmbH Phone : +49.5361.189.473
> Hesslinger Str. 1-5, D-38440 Wolfsburg Fax : +49.5361.189.199
> Email: [EMAIL PROTECTED] - IRC: bofw2 Mobile : +49.170.920.153.5
>
>
>
--
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.
