While this may sound odd, I'm situated with a number of NAS's with
unknown/changing IPs (DHCP, PPPoE, etc). It doesn't appear possible to
allow any client to connect; does a wildcard like DEFAULT work in
clients.conf?
--
Matt Peterson
-
List info/subscribe/unsubscribe? See
On Tuesday 03 December 2002 19:42, Matt Peterson wrote:
While this may sound odd, I'm situated with a number of NAS's with
unknown/changing IPs (DHCP, PPPoE, etc). It doesn't appear possible to
allow any client to connect; does a wildcard like DEFAULT work in
clients.conf?
Did you read
On Tue, Dec 03, 2002 at 08:51:38PM -0500, Kevin Bonner wrote:
Did you read clients.conf? It has examples on how you can do this. You can
use 0.0.0.0/0, but if you know the address range of IP's which they will
always come from, I would suggest using that instead.
Yes, the clients.conf in
Matt Peterson [EMAIL PROTECTED] wrote:
Yes, the clients.conf in the 0.8 release doesn't include this example,
nor does the latest version in CVS. However, client 0.0.0.0/0 errors
out..
/usr/local/etc/raddb/radiusd.conf[3]: Invalid value '0' for IP network
mask.
Yes. It's a VERY bad
On Tue, Dec 03, 2002 at 10:51:44PM -0500, Alan DeKok wrote:
Yes. It's a VERY bad idea to allow any machine on the Internet to
send packets to your radius server.
I totally agree, which is why a firewall exists in front of the RADIUS
server. Maybe a hack using DynDNS is possible, however
