unresponsive / radiusd - X versus rc.radius start
- To: freeradius-users@lists.freeradius.org
- Subject: unresponsive / radiusd - X versus rc.radius start
- From: WI Cricket <west.indian.cricket@gmail.com>
- Date: Thu, 01 Jun 2006 16:00:22 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:disposition-notification-to:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=JN+F3aVNzX4ATx4RRHfeqxzq/DEiwtmhc5YQx29S4wHYPoBFkzRb4Rv38pLbBb9wqFP8Un9hGmS75HUwg6QityAamZen5o16cCodjORhuW/0ALc58EtsFPl2irgvw+P+c5OkYGpd/92A1U3s+Se60Un4sudMnzw/o0Y0pKdt4oE=
- Reply-to: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
- User-agent: Thunderbird 1.5.0.2 (Windows/20060308)
Hello,
I just joined the list. This is my first post. I tried to review the
archives for something similar but I am not sure if I did find a way
around it. First, is there a difference running FreeRadius using:
rc.radiusd start versus radiusd -X
Here is my set-up. I have two winXP supplicants using TLS for
authentication and one W2K using TTLS-MS-CHAPv2. My FreeRadius is
running on SuSE Linux 10 and my NAS is Linksys WRT54GS running 4.71 +
HyperWRT + Thibor15c (this make not make any difference)
Anyway, what is happening is that all the supplicants seem to work well
using radiusd -X, however the freeRadius server seems unresponsive after
a few hours of running it with rc.radiusd start.
Please let me know if anyone sees an immediate issue with my setup or I
can provide more information if need. I am running 1.1.2 of FreeRadius.
Thank you all for your support and this great software.
This archive was generated by a fusion of
Pipermail (Mailman edition) and
MHonArc.