passing Calling-Station-ID
Hello All, We would like to get your input on an issue we are facing: We are using two NASs and one FreeRadius 1.1.5, the first NAS authenticate the user "someuser" through Radius and assign an IP address with no problem. we can see the accounting start record with the calling-station-ID and other attributes. The issue is that we want the second NAS to get the calling-station-ID from the "someuser" session on Radius is there a way we can have this to work and pass this attribute from one session to another? Thank you -- |-Adil Azmi Bikarbass |-IT Manager |-MTDS S.A. |-tel +212.3.767.4861 |-fax +212.3.767.4863 |-gsm +212.6.139. 4541 |-14, rue 16 novembre |-Rabat, Kingdom of Morocco
Adil Azmi Bikarbass wrote:
The issue is that we want the second NAS to get the calling-station-ID from the "someuser" session on Radius
To do... what?
is there a way we can have this to work and pass this attribute from one session to another?
Sure. Store the Calling-Station-Id in a database when you receive it from the first NAS, then pull it out of the DB, and send it to the second NAS. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Alan DeKok a écrit :
Adil Azmi Bikarbass wrote:
The issue is that we want the second NAS to get the calling-station-ID from the "someuser" session on Radius
To do... what?
This is will be used for a mobile 3G application : the first NAS will authenticate the user and assign the IP and the second nas should get the assigned IP and the calling-Station-ID (cell phone number) for billing purposes
is there a way we can have this to work and pass this attribute from one session to another?
Sure. Store the Calling-Station-Id in a database when you receive it from the first NAS, then pull it out of the DB, and send it to the second NAS.
The solution should be fast enough to handle thounsads of request simultaniously, you thing going through a DB is fast enough? can we pass this info into the RAM between the two NAS sessions? AB
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
-- |-Adil Bikarbass |-IT Manager, MTDS |-tel +212.3.767.4861 |-fax +212.3.767.4863 |-gsm +212.6.139. 4541 |-14, rue 16 novembre |-Rabat, Kingdom of Morocco
Hello All, Do i need to create a whole DB for only one filed that i will pass from one NAS to another? Knowing that my Freeradius is running on Solaris 10 which DB you suggest to use? Thank you Alan DeKok a écrit :
Adil Azmi Bikarbass wrote:
The issue is that we want the second NAS to get the calling-station-ID from the "someuser" session on Radius
To do... what?
is there a way we can have this to work and pass this attribute from one session to another?
Sure. Store the Calling-Station-Id in a database when you receive it from the first NAS, then pull it out of the DB, and send it to the second NAS.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
-- |-Adil Bikarbass |-IT Manager, MTDS |-tel +212.3.767.4861 |-fax +212.3.767.4863 |-gsm +212.6.139. 4541 |-14, rue 16 novembre |-Rabat, Kingdom of Morocco
Adil Azmi Bikarbass wrote:
Do i need to create a whole DB for only one filed that i will pass from one NAS to another?
You have to store the data somewhere.
Knowing that my Freeradius is running on Solaris 10 which DB you suggest to use?
Postgres works. Recent versions of OpenLDAP are very fast, too. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
On Mon 02 Apr 2007, Alan DeKok wrote:
Adil Azmi Bikarbass wrote:
Do i need to create a whole DB for only one filed that i will pass from one NAS to another?
You have to store the data somewhere.
Knowing that my Freeradius is running on Solaris 10 which DB you suggest to use?
Postgres works. Recent versions of OpenLDAP are very fast, too.
Yep. I recommend Postgres for this type of thing. OpenLDAP is very fast (much faster than Postgres) for reads, but very slow (slower than postgres) for writes. Given that this sounds like a 50/50 app, go with Postgres. Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
participants (3)
-
Adil Azmi Bikarbass -
Alan DeKok -
Peter Nixon