),
bhalchandra sawant
[EMAIL PROTECTED] wrote:
Hi,
In clients.conf there is 127.0.0.1.
I give below clients.conf file --
client 127.0.0.1 {
secret = omeya
shortname = spacecable
nastype = other # localhost isn't
usually a
NAS
Hi Jason,
Yes, I had made mistake in $INCLUDE
${confdir}/clients.conf. It was commented.
Now Freeradius started accepting requests.
Thanks,
-bs sawant
--- Jason Frisvold [EMAIL PROTECTED] wrote:
On Wed, 1 Dec 2004 02:44:23 -0800 (PST), bhalchandra
sawant
[EMAIL PROTECTED] wrote:
Hi
:14 -0800 (PST),
bhalchandra sawant
[EMAIL PROTECTED] wrote:
Hi,
The debug log from server side is as below:
rad_recv: Access-Request packet from host
127.0.0.1:1137, id=67, length=56
Ignoring request from unknown client
127.0.0.1:1137
Looks like 127.0.0.1 is not in the clients.conf
= omeya
shortname = spacecable
nastype = other
}
-Mohammed.
Mohammed H. Petiwala
Senior Staff Engineer
iDEN-WLAN, Motorola Inc.
--- bhalchandra sawant [EMAIL PROTECTED] wrote:
Hello,
I am configuring Freeradius with Mysql. I think I
:
bhalchandra sawant [EMAIL PROTECTED] wrote:
I am configuring Freeradius with Mysql. I think I
have configured correctly, as I am not getting any
error message in debugging mode. The result is as
below :
No, it isn't. You've shown the debug log from the
server starting
up
Hello,
I am configuring Freeradius with Mysql. I think I
have configured correctly, as I am not getting any
error message in debugging mode. The result is as
below :
[EMAIL PROTECTED] root]# radiusd -X
Starting - reading configuration files ...
reread_config: reading radiusd.conf
Config:
6 matches
Mail list logo