"Stefan Auweiler" <[EMAIL PROTECTED]> wrote:
> I'd like to extend the 'Status Server' Reply Message with the admins =
> contact
> information
> Does anybody has an advice or a readme?
Source code modifications. See 'src/main/radiusd.c'
All,
I'd like to extend the 'Status Server' Reply Message with the admins contact
information
Does anybody has an advice or a readme?
My environment:
SuSe 8.1, FreeRADIUS 0.8.1
Test with NTRadPing
Thanks
Stefan
-
List info/subscribe/unsubscribe? See http://www.free
"Miquel van Smoorenburg" <[EMAIL PROTECTED]> wrote:
> Some clients use periodic status-server pinging to see if the
> server is up.
http://www.freeradius.org/rfc/rfc2865.html#Keep-Alives
They're bad.
> That is useful with a server that has both local users and
In article <[EMAIL PROTECTED]>,
Alan DeKok <[EMAIL PROTECTED]> wrote:
> FreeRADIUS doesn't do Status-Server messages. I've never seen a
>good reason for them.
Some clients use periodic status-server pinging to see if the
server is up.
That is useful with a server t
Thanks for the reply Alan.
> I'm not *opposed* to adding Status-Server support to FreeRADIUS, but
> I am opposed to adding functionality unless there's a real need for it.
>
Is there a straight forward way that I can add Status-Server support into
FreeRadius 0.7.1 to see
tests and under much load. However, after several hours of
> perfect operation, all of our freeradius servers now receive the
> following from our Access Router Cards:
> rad_recv: Status-Server packet from host 216.176.146.2:1645, id=252,
> length=20 Ignoring request from client 216.17
Router
Cards:
rad_recv: Status-Server packet from host 216.176.146.2:1645, id=252, length=20
Ignoring request from client 216.176.146.2:1645 with unknown code 12
Which then the accounting data shows UserName "unauthenticated" attempting to
authenticate which I believe is some sort of ge
alarm by doing a periodic check.
That's about the only reason I can think of for using
Status-Server.
> I agree that that a ping is not the best way but we are looking for a
> way to check the status of the Server from the Client perspective though
> SNMP should be used i
il Yu" <[EMAIL PROTECTED]> wrote:
> THanks for your response, but there is no information on the
> Status-Server.
Exactly. Its use is implementation-dependent.
> What I would like is something to indicate what the status of the
> server is (from the RADIUS client perspective).
"Gil Yu" <[EMAIL PROTECTED]> wrote:
> THanks for your response, but there is no information on the
> Status-Server.
Exactly. Its use is implementation-dependent.
> What I would like is something to indicate what the status of the
> server is (from the RADIUS cli
Hi Alan,
THanks for your response, but there is no information on the
Status-Server. What
I would like is something to indicate what the status
of the server is (from the
RADIUS client perspective).
Any suggestions?
..Gil
Alan DeKok wrote:
Gil Yu" <[EMAIL PROTECTED]> w
Gil Yu" <[EMAIL PROTECTED]> wrote:
See: http://www.freeradius.org/rfc/attributes.html
>Does anybody know how the Status-Server RADIUS type is used?
http://www.freeradius.org/rfc/rfc2865.html
Section 3.
>Is it used as a "keepalive" for the RA
Hi,
Does anybody know how the Status-Server RADIUS type
is used?
Is it used as a "keepalive" for the RADIUS server?
In addition, is there documentation on what the contents
of the
RADIUS PDU should be sent by the RADIUS client
and what
should be received from the RAD
Hi Mike,
Yes, you were right. I need to reply to code 12d with code 2d.
I have modified radiusd.c to handle the Status-Server request.
I'm not really good in C but this is the "diff" on the code:
root@atlas:/home/ftp/compile/freeradius-0.3/src/main > diff radiusd.c radiusd.
In article <[EMAIL PROTECTED]>,
Carlos Velasco <[EMAIL PROTECTED]> wrote:
>Hi Mike,
>
>No, the problem is that the Radius Server (Freeradius) does not support
>code 12d Requests.
I know. So I made the remark that adding support for it is easy,
and I demonstrated that Cistron Radius already has th
>>"Carlos Velasco" <[EMAIL PROTECTED]> wrote:
>>> We have a problem with 3Com TotalControl 1000 and NMC accounting.
>>> It seems that the NMC send a code 12d packet (Status-Server request) as=
>>> seen in the RFC, but the FreeRadius is not replyi
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
>"Carlos Velasco" <[EMAIL PROTECTED]> wrote:
>> We have a problem with 3Com TotalControl 1000 and NMC accounting.
>> It seems that the NMC send a code 12d packet (Status-Server request) as=
>
"Carlos Velasco" <[EMAIL PROTECTED]> wrote:
> We have a problem with NMC accounting in TotalControl 1000.
> It seems that the NMC uses Status-Server packets by design.
Then it's broken.
There is *no* way of knowing what each NAS wants when it sends a
Status-Serve
Hi Alan,
We have a problem with NMC accounting in TotalControl 1000.
It seems that the NMC uses Status-Server packets by design.
I saw that Freeradius supported "alive" packets and I thought it was this.
I have seen this in the dictionary:
VALUE Packet-Type Sta
"Carlos Velasco" <[EMAIL PROTECTED]> wrote:
> We have a problem with 3Com TotalControl 1000 and NMC accounting.
> It seems that the NMC send a code 12d packet (Status-Server request) as=
> seen in the RFC, but the FreeRadius is not replying to this packet.
It doe
Hello,
We have a problem with 3Com TotalControl 1000 and NMC accounting.
It seems that the NMC send a code 12d packet (Status-Server request) as seen in the
RFC, but the FreeRadius is not replying to this packet.
I have these messages in the radius.log
Wed Nov 28 13:08:12 2001 : Error
21 matches
Mail list logo
