Re: (RADIATOR) Service-Types and check items

;' authen_type=PAP service=PPP priv=1 Frank > >I will need to see a more complete trace 4 showing what is happening. > >thanks > >Hugh > >On Fri, 01 Sep 2000, FlintHillsTechnical Support wrote: >> Hello-- >> >> We have tried to implement Handler

Re: (RADIATOR) Service-Types and check items

Hello-- We have tried to implement Handlers which work, sorta! We now can allow any user to connect to our Ascends despite their Service-Type and we can restrict who can telnet to the Cisco. However, when we try to dial into the external NAS that is connected to the Cisco as a normal user it

(RADIATOR) Service-Types and check items

Hello-- We have Ascend NASes and a Cisco router that has other NASes connected to it via L2F tunnels. We are trying to restrict who can telnet to the Cisco router. Previously, we did not have the NASes connected to the Cisco so access was restricted by placing the Cisco in a separate realm po

(RADIATOR) accounting with a cisco 7206

we have started a new ISP service where users dial into to a remote NAS that then authenticates the user across an L2F tunnel through our Cisco 7206. We can authenticate the user and allow access, however in the initial accounting record the Cisco does not seem to pass the ip address it has as

(RADIATOR) assigning ip addresses from a common pool

Hello-- I am looking for some input on a method, if possible, to assign all of my dial up users ip addresses via radiator from one common pool. I have looked at the FramedGroupBaseAddress and the FramedGroup attributes but I am not sure if this is the correct way to approach this. It appears

RE: (RADIATOR) Radiator & MAX TNT

we are using 4000 series ascends and I have not seen those options (I will search the archives, as noted below) either. However you do need to upgrade from 6.1.7 there are some memory bugs in the earlier releases that causes fatal errors. The current version is 7.0.26 and we are using 7.0.22

(RADIATOR) "extra" attributes logged by Ascend to radiator

We are using ascend 4000's and they seem to log a lot of information. Is there any way to cull some of this out? For instance, we are not really concerned with the customer's amount of octets and packets inputed and outputed Frank === Archive at http://www.starport.net/~radiator/ Announc

(RADIATOR) ascend authentication

we are using ascend maxs for dial up accounts and are a little unclear on the type of authentication. We have the choice of RADIUS or RADIUS/LOGOUT. If we want to do accounting, i.e. have a clear idea of when someone dialed in, where they were(which ascend and their port's ip) and when they l

(RADIATOR) ascend disconnect causes

Is their any significance in the different disconnect causes we receive from our Ascends? We receive pppRcvTerminate and remoteEndhungup on a lot of sessions. if anyone knows of reference for these that would be helpful also! thanks Frank === Archive at http://www.thesite.com.au/~radiator/ T

Re: (RADIATOR) multiple sessions

yes -- Original Message -- From: "Danny Whitesel" <[EMAIL PROTECTED]> Date: Wed, 2 Feb 2000 17:43:27 -0500 >Are you referring to multi-link? > > >-Original Message- >From: Flint Support <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>