From owner-freebsd-isp Thu Nov 20 13:39:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA10204 for isp-outgoing; Thu, 20 Nov 1997 13:39:47 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA10199 for ; Thu, 20 Nov 1997 13:39:43 -0800 (PST) (envelope-from tomthai@future.net) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.6/8.8.6) with SMTP id PAA09007; Thu, 20 Nov 1997 15:37:07 -0600 (CST) Date: Thu, 20 Nov 1997 15:37:06 -0600 (CST) From: "Tom T. Thai" To: linuxisp@friendly.jeffnet.org, freebsd-isp@FreeBSD.ORG Subject: radiusclient users? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk could I get a show of hands to see who uses radiusclient (by Lars), patched ppp2.2.0f (by Godec, and Map)? I'm writing documentation for it and have lots of questions. There currently seems to be lots of patches and login.radius around, and I want to pull them all together. I think this would be very helpful for everyone who uses radiusclient. I'm aware of portslave also, but I think radiusclient is more modular so I am leaning toward radiusclient. Here one interesting thing I just found out when I was playing around with mgetty+autoppp, radiusclient, and pppd-radius: Assume auto ppp detection is in progress and mgetty passes the call to pppd-radius. Even though pppd-radius doesn't actually need login.radius, login.radius should still exit in the path for pppd-radius to authenticate the user. Here is a would be FAQ: Assume you are running RADIUS2.0.1 and the user profile uses Framed-IP-Address = 255.255.255.254 or Framed-IP-Address = 255.255.255.255, how do you tell pppd-radius to assign the proper IP? In the first case, radiusclient or pppd-radius have to pick an available IP from an assigned IP pool just like the Portmasters or use the port IP from /etc/ppp/options.ttyR0 or so. In the second case, radiusclient/pppd-radius should use the "user" picked IP. Currently radiusclient/pppd-radius doesn't support that directly, but I suppose you could parse the parameter using login.radius (but not with the current radiusd-ppp, unless it's thru ip-up, etc.) Also, some of you probably do some kind of filtering and such... So let's see a show of hand that is willing to help. I'll post my work in progress at http://www.future.net/~tomthai/radius. .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087