(RADIATOR) Fall-Through entries with AuthEMERALD???

[Robert G. Fisher]

I'm in the process of switching from Cistron to Radiator
using AuthEMERALD to authenticate against my database 
which is maintained by Platypus 3.0.

One issue that I'm running into that I have yet to understand
how to resolve is the case of fall-through entries for the
user.

Currently I have entries like:

user	Auth-Type=System, NAS-IP-Address=x.x.x.x
	Framed-IP-Address = 1.2.3.4,
	Fall-Through = 1

user	Auth-Type=System, NAS-IP-Address=y.y.y.y
	Framed-IP-Address = 5.6.7.8,
	Fall-Through = 1

DEFAULT	Auth-Type=System, Hint = PPP
	Service-Type = Framed-User,
	Framed-Protocol = PPP,
	Framed-Compression = Van-Jacobson-TCP-IP,
	Framed-IP-Netmask = 255.255.255.255,
	...
	Fall-Through = 0


The reason for assigning two static IPs is I have some
equipment that needed a way of tracking the user no
matter where they logged in and not all equipment is
within the same subnet range.  Also, I have customers
that will connect to one piece of equipment from their
office and expect a static IP while there -- which requires
a connection to a specific NAS on our side, but also
wish to be able to connect to any of our NAS or any
device doing proxy auth against our radius server and
be assigned an IP that would work on that NAS.

-- 
Robert G. Fisher                  Sitestar.net, Inc. 
Senior System Engineer            (540) 666-9533 x 116
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.