Mon Sep 24, 2007 7:58 pm
Ok, this is what the Radius Server sees when the test account logs in.
rad_recv: Accounting-Request packet from host 64.114.71.1:34381, id=69, length=144
Acct-Status-Type = Start
NAS-Port-Type = Wireless-802.11
Calling-Station-Id = "00:19:7E:70:B0:90"
Called-Station-Id = "server1"
NAS-Port-Id = "ether4"
User-Name = "test"
NAS-Port = 2150629468
Acct-Session-Id = "8030005c"
Framed-IP-Address = 10.10.11.36
Mikrotik-Attr-10 = 0x0a0a0b22
Event-Timestamp = "Sep 24 2007 09:39:16 PDT"
NAS-Identifier = "CP_Telus_MT_BLSS"
NAS-IP-Address = 64.114.*.*
Acct-Delay-Time = 0
rad_lowerpair: User-Name now 'test'
rad_rmspace_pair: User-Name now 'test'
Processing the preacct section of radiusd.conf
modcall: entering group preacct for request 24
rlm_acct_unique: WARNING: Attribute Client-IP-Address was not found in request, unique ID MAY be inconsistent
rlm_acct_unique: Hashing 'NAS-Port = 2150629468,,NAS-IP-Address = 64.114.71.1,Acct-Session-Id = "8030005c",User-Name = "test"'
rlm_acct_unique: Acct-Unique-Session-ID = "c5bff48f5d16e251".
modcall[preacct]: module "acct_unique" returns ok for request 24
modcall: group preacct returns ok for request 24
Processing the accounting section of radiusd.conf
modcall: entering group accounting for request 24
radius_xlat: 'test'
rlm_sql (sql): sql_set_user escaped user --> 'test'
WARNING: Attempt to use unknown xlat function, or non-existent attribute in string %{Connect-Info}
radius_xlat: 'INSERT into radacct (AcctSessionId, AcctUniqueId, UserName, Realm, NASIPAddress, NASPortId, NASPortType, AcctStartTime, AcctStopTime, AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop, AcctInputOctets, AcctOutputOctets, CalledStationId, CallingStationId, AcctTerminateCause, ServiceType, FramedProtocol, FramedIPAddress, AcctStartDelay, AcctStopDelay) values('8030005c', 'c5bff48f5d16e251', 'test', '', '64.114.71.1', '2150629468', 'Wireless-802.11', '2007-09-24 10:49:35', '0', '0', '', '', '', '0', '0', 'server1', '00:19:7E:70:B0:90', '', '', '', '10.10.11.36', '0', '0')'
rlm_sql (sql): Reserving sql socket id: 3
rlm_sql (sql): Released sql socket id: 3
modcall[accounting]: module "sql" returns ok for request 24
modcall: group accounting returns ok for request 24
Sending Accounting-Response of id 69 to 64.114.71.1:34381
Finished request 24
Going to the next request
Waking up in 6 seconds...
--- Walking the entire request list ---
Cleaning up request 23 ID 68 with timestamp 46f7f8af
Cleaning up request 24 ID 69 with timestamp 46f7f8af
Nothing to do. Sleeping until we see a request.
There are two warnings, but the first one doesn't seem to be the issue since all users who log into the system are generating this warning. The second warning though may be the problem, though I have no idea what this warning actually means.
The rate limiting does seem to be working though, the only issue is the MT box keeps resetting the connection of the test account. Bandwidth testing sites can never seem to finish their tests, and when I go to download a driver from nvidia.com I get the error:
Internet Explorer cannot download ...<driver_file_name>
The connection with the server was reset.
Any suggestions?
~Sean