[RadiusNT] Re: Concurrency Control Does Not Work...HELP!!!

TIA ( (no email) )
Sun, 13 Feb 2000 13:35:56 -0600

Subject: [RadiusNT] Re: RadiusNT Digest
From: "Todd K. Tuttle" <ttuttle@nckcn.com>
Date: Fri, 11 Feb 2000 12:24:19 -0600

Thanks a million Dale for all your help. Answers below...

----- Original Message -----

Dale E. Reed Jr. Wrote:

> > I have ran this script numerous times and it does not change any of the
> > ports in any way as they are exactly the same as reported by the NAS ,
as
> > reported in the Servers Table, as reported in the ServerPorts table, and
> > reported as well as in the Calls Table. They all report or coincide
exactly.

> First, are you getting accounting packets (type=4)?

Yes, from -x15:

radrecv: Request from host cefd387c (rtr3-beloit) code=4, id=116, length=82
NAS-Identifier = 206.253.56.124
NAS-Port = 2
User-Name = "testuser"
Acct-Status-Type = Start
Class = "IEAS1\00112\0016"
User-Service = Framed-User
Acct-Session-Id = "00000020"
Framed-Protocol = PPP
Sending Accounting Ack of id 116 to cefd387c (rtr3-beloit)
Resp Time: 360 Auth: 13/3 -> 17 Acct: 20/0/0 -> 20

radrecv: Request from host cefd387c (rtr3-beloit) code=4, id=117, length=88
NAS-Identifier = 206.253.56.124
NAS-Port = 2
User-Name = "testuser"
Acct-Status-Type = Alive
Class = "IEAS1\00112\0016"
User-Service = Framed-User
Acct-Session-Id = "00000020"
Framed-Protocol = PPP
Framed-Address = 209.42.65.241
Sending Accounting Ack of id 117 to cefd387c (rtr3-beloit)
Resp Time: 344 Auth: 13/3 -> 17 Acct: 21/0/0 -> 21

> Secondly, do you have
> some kind of trigger or manual calls update enabled? If you don't have
> one of those two, then the calls online (server ports) will not be
> updated.

I have Emerald and MSSQL 7. The manual, (RadiusNT v3, ppg 22 and again on
ppg. 34), states you do not have to have this set on an active database
setup such as Emerald/SQL. But I need to have this set for Concurrency
Control to work no matter what Database? I have set the Manual Calls Update
enabled in the RadiusNT Admin and it still doesn't work. I can view both
logins on the Emerald "On-line" utility. Both logins are there just big as
you please, where does this come from and why do they both show up if it is
not updating the calls table? Here is a snip from the -x15 with Manual Calls
Update enabled:

radrecv: Request from host cefd387c (rtr3-beloit) code=4, id=179, length=82
NAS-Identifier = 206.253.56.124
NAS-Port = 1
User-Name = "taterboy"
Acct-Status-Type = Start
Class = "IEAS1\00112\0016"
User-Service = Framed-User
Acct-Session-Id = "00000030"
Framed-Protocol = PPP
SQL Statement: UPDATE ServerPorts SET
Username='taterboy',AcctStatusType=1,AcctS
essionID='00000030',CallDate='20000213 13:8:7' FROM Servers s, ServerPorts
sp WH
ERE sp.ServerID = s.ServerID AND
COALESCE(sp.IPAddress,s.IPAddress)='206.253.56
..124' AND sp.Port=1 AND (DateAdd(Second, 0-0, '20000213 13:8:7') >=
sp.CallDate
OR sp.CallDate IS NULL)
Sending Accounting Ack of id 179 to cefd387c (rtr3-beloit)
Resp Time: 656 Auth: 2/3 -> 5 Acct: 4/0/0 -> 4

radrecv: Request from host cefd387c (rtr3-beloit) code=4, id=180, length=88
NAS-Identifier = 206.253.56.124
NAS-Port = 1
User-Name = "taterboy"
Acct-Status-Type = Alive
Class = "IEAS1\00112\0016"
User-Service = Framed-User
Acct-Session-Id = "00000030"
Framed-Protocol = PPP
Framed-Address = 209.42.65.240
SQL Statement: UPDATE ServerPorts SET
Username='taterboy',AcctStatusType=3,AcctS
essionID='00000030',FramedAddress='209.42.65.240',CallDate='20000213 13:8:8'
FRO
M Servers s, ServerPorts sp WHERE sp.ServerID = s.ServerID AND
COALESCE(sp.IPAd
dress,s.IPAddress)='206.253.56.124' AND sp.Port=1 AND (DateAdd(Second, 0-0,
'200
00213 13:8:8') >= sp.CallDate OR sp.CallDate IS NULL)
Sending Accounting Ack of id 180 to cefd387c (rtr3-beloit)
Resp Time: 641 Auth: 2/3 -> 5 Acct: 5/0/0 -> 5

SQL Statement: {CALL RadGetCacheUsers('20000213 13:3:12',1)}
radrecv: Request from host cefd387c (rtr3-beloit) code=1, id=181, length=72
NAS-Identifier = 206.253.56.124
NAS-Port = 2
User-Name = "taterboy"
Password = "\343q;\204\025\376\341\317\371\276-\004\310E!\254"
User-Service = Framed-User
Framed-Protocol = PPP
Checking for duplicate logins.
SQL Statement: {CALL RadCheckOnline('taterboy')}
taterboy found on-line 0 time(s).
Checking for port access.
Sending Ack of id 181 to cefd387c (rtr3-beloit)
User-Service = Framed-User
Framed-Protocol = PPP
Session-Timeout = 18000
Idle-Timeout = 900
Class = "IEAS1\00112\0016"
Resp Time: 640 Auth: 3/3 -> 6 Acct: 5/0/0 -> 5

radrecv: Request from host cefd387c (rtr3-beloit) code=4, id=182, length=82
NAS-Identifier = 206.253.56.124
NAS-Port = 2
User-Name = "taterboy"
Acct-Status-Type = Start
Class = "IEAS1\00112\0016"
User-Service = Framed-User
Acct-Session-Id = "00000031"
Framed-Protocol = PPP
SQL Statement: UPDATE ServerPorts SET
Username='taterboy',AcctStatusType=1,AcctS
essionID='00000031',CallDate='20000213 13:9:2' FROM Servers s, ServerPorts
sp WH
ERE sp.ServerID = s.ServerID AND
COALESCE(sp.IPAddress,s.IPAddress)='206.253.56
..124' AND sp.Port=2 AND (DateAdd(Second, 0-0, '20000213 13:9:2') >=
sp.CallDate
OR sp.CallDate IS NULL)
Sending Accounting Ack of id 182 to cefd387c (rtr3-beloit)
Resp Time: 640 Auth: 3/3 -> 6 Acct: 6/0/0 -> 6

radrecv: Request from host cefd387c (rtr3-beloit) code=4, id=183, length=88
NAS-Identifier = 206.253.56.124
NAS-Port = 2
User-Name = "taterboy"
Acct-Status-Type = Alive
Class = "IEAS1\00112\0016"
User-Service = Framed-User
Acct-Session-Id = "00000031"
Framed-Protocol = PPP
Framed-Address = 209.42.65.241
SQL Statement: UPDATE ServerPorts SET
Username='taterboy',AcctStatusType=3,AcctS
essionID='00000031',FramedAddress='209.42.65.241',CallDate='20000213 13:9:2'
FRO
M Servers s, ServerPorts sp WHERE sp.ServerID = s.ServerID AND
COALESCE(sp.IPAd
dress,s.IPAddress)='206.253.56.124' AND sp.Port=2 AND (DateAdd(Second, 0-0,
'200
00213 13:9:2') >= sp.CallDate OR sp.CallDate IS NULL)
Sending Accounting Ack of id 183 to cefd387c (rtr3-beloit)
Resp Time: 625 Auth: 3/3 -> 6 Acct: 7/0/0 -> 7

> > From what I gather,Concurrency Control is set on a per NAS basis and not
> > across the complete authentication system. Any help would be greatly
> > appreciated

> No. Concurrency control is based on the username, not the server. If
> you look at the RadCheckOnline proc, you'll see its just for the name,
> not the user.
>
Super! That's just what I want. Now if I can just get the Concurrency
Control to work... I'm getting to the point, after 3 months, where I will
start to get frustrated and just that there's $5,000 down the tube...

--------------------------------------------------
Thank You
Network Administration Staff
North Central Kansas Community Network

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart