Hi,
Who can help me to resolve this problem?detail as
following:
Log:
** Received from 10.0.0.10 port 1812
Code: Access-RequestIdentifier:
174Authentic:
@o260189i00189i00223f166165Attributes:
User-Name = "anonymous"
cisco-avpair = "ssid=Test"
NAS-IP-Address =
Hi all,
I think this only happens when a call does not connect but I've
noticed something strange with regards to call duration. I think this
is illustrated well in this output listing from our accounting database:
ACCT_SESSION_TIME
-
4
1054176189
We had a similar situation with accounting data from a 3Com Total Control
chassis. What we noticed was that these abnormally large numbers occurred
when the disconnect cause was 0 or 1 and calls that ended normally had a
disconnect cause of 2. In this case it was due to a call setup failure and
The catch is that a PreAuthHook is not the place to do authentication.
Instead of using a PreAuthHook you could use a PostAuthHook to call the
AuthBy LDAP based on the results of whatever your authentication system
returns. There is an example of calling an AuthBy from a PostAuthHook in
Is there an rc.d file (start/stop) for Radiator?
Bret
--
~~~
Bret Jordan Dean's Office
Computer Administrator College of Engineering
801.585.3765 University of Utah
[EMAIL PROTECTED]
Dear Bret,
Which model of Proxim in-door/out-door access points can be to use?
Thanks,
Balgaa
We use Proxim for internal and external hot spot
access running 802.1x
for authentication all backended off of Radiator..
Proxim also had a
more hotel style authentication for their 'hot spot'
My experience involves Radiator 3.5 and Cisco AP 340 and 350, so
something could be different.
I've not been able to supply different SSIDs as reply attribute, but
they work as check attributes.
If you can supply this info to your users, then you can check the right
association SSID-user or
