Yevgeny Kosarzhevsky wrote:
> Alan DeKok wrote:
>> it doesn't work
> ok I am providing the output from radius:
>
> rad_recv: Disconnect-Request packet from host 10.10.10.1 port 36257,
> id=33, length=36
> User-Name = "test"
> NAS-IP-Address = 10.10.10.11
Uh... that's *receiving*
Alan DeKok wrote:
it doesn't work
ok I am providing the output from radius:
rad_recv: Disconnect-Request packet from host 10.10.10.1 port 36257,
id=33, length=36
User-Name = "test"
NAS-IP-Address = 10.10.10.11
server coa {
+- entering group recv-coa {...}
++[ok] returns ok
+-
Yevgeny Kosarzhevsky wrote:
> Ok and how can I send request to NAS to disconnect client? I tried
> raddb/sites-available/coa but cannot make it to send packets to
> appropriate NAS.
See the FAQ for "it doesn't work"
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/
Alan DeKok wrote:
Yevgeny Kosarzhevsky wrote:
How to make radius stop thinking the user is connected (like if no
Acct-Interim-Update messages received in specified time).
Store the sessions in a database, and run a "cron" job to clean up
stale sessions.
Ok and how can I send r
Yevgeny Kosarzhevsky wrote:
> Hi,
>
> I am using pppd on linux nas. The client has connected, then after some
> time freeradius server has disappered on the network because of
> connection issue. The user disconnected when it was still down. Then,
> after freeradius came up the user wasn't able to
Hi,
I am using pppd on linux nas. The client has connected, then after some
time freeradius server has disappered on the network because of
connection issue. The user disconnected when it was still down. Then,
after freeradius came up the user wasn't able to login anymore because
of simultane
6 matches
Mail list logo
