(RADIATOR) passing information between Radiators and authby question

[Viraj Alankar]

Hello,

I am trying to determine what's the best way to pass information between 2
Radiator's, one proxying requests to the other. For example, say I have
Radiator A proxying requests to Radiator B. I would like to pass some request
specific information from A to B, such as a VISP ID. I thought of using Class,
but there could be requests coming to A that are already using Class, so there
may be some conflict.

So I'm wondering what's the best way to deal with this. Create a new attribute
in each dictionary and use that? If so, how can I use something that I'm sure
will not conflict with other vendors? Also, I need the attribute to come in
accounting packets as well. I only know of Class that is honored by RASes as
being returned in accounting.

Another question I have is using Auth-By in a users file. For example:

<Handler NAS-IP-Address = 1.2.3.4>
        <AuthBy FILE>
                Filename nas-1.2.3.4
        </AuthBy
</Handler>

nas-1.2.3.4:

DEFAULT Calling-Station-Id = 111, Auth-Type = DoA

DEFAULT Calling-Station-Id = 222, Auth-Type = DoB

First, is this method efficient if we have up to 500 RASes?

Suppose I want to do a RewriteUsername to ALL the authbys (DoA and DoB), is
there a way I can do something like:


DEFAULT Auth-Type = DoRewrites

DEFAULT Calling-Station-Id = 111, Auth-Type = DoA

DEFAULT Calling-Station-Id = 222, Auth-Type = DoB

where it will fall through after the first one? I was thinking of making an
AuthBy DoRewrites that returns IGNORE. In that case it should fall through
correct?

Basically I would like to do the rewrites in the users file level and not in
the Handler level.

Thanks,

Viraj.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.