I am running RRAS successfully now after much effort. Here's what I did. I
used ODBC mode and and I modified the relationship between the Servers and
Calls table. Instead of Servers:IPAddress relating to Calls:NasIdentifier,
I used Servers:Server to Calls:NasIdentifier. This made authentication work
since it makes use of the machine ( NetBIOS ) name instead of the NAS IP
Then to get Concurrency Control, I did this: I added an entry in
RADATConfigs. Here it is: PPP, 4, 172.31.1.1 ( which is my one and only
RRAS machine's address ).
Of course, this is assuming you got the right RRAS fix.
Let me know if this works for you too.
- Danny Sinang
> From: David Harris <firstname.lastname@example.org>
> To: RadiusNT@iea-software.com
> Subject: Re: RARAS Accounting Info
> Date: Saturday, December 06, 1997 1:02 AM
> Since I didn't get an answer to my last question I have decided to go
> positive on the list and propose a solution to the RARAS problem, the way
> read the RFC for accounting, you are in compliance when you send either
> attribute 4 (NAS IP Address) OR attribute 32 (Machine Name) or BOTH...
> sends Both, RARAS sends 32, everyone else it seems sends attribute 4.
> to make Radius-NT work with any compliant port server, if attribute 4
> sent, have it use attribute 4 as the NAS Id. if attribute 4 is not sent,
> look up the ip address of attribute 32 and use that as the nas Id.
> this may be a quick code change (I think it should be), anyway I
> currently have a test platform set up with an end to end isolated system
> test on if I can be of any assistance testing a fix let me Know...
> "The woods are lovely, dark and deep. But I have promises to keep,
> And lines to code before I sleep, And lines to code before I sleep."
> David Harris
> Operations Manager
> StarNet OnLine Systems
> RadiusNT Mailing List email@example.com