How would you handle routing with a common IP pool across several NASs?
/Ingvar
> -----Original Message-----
> From: FlintHillsTechnical Support [mailto:[EMAIL PROTECTED]]
> Sent: den 19 augusti 2000 02:48
> To: [EMAIL PROTECTED]
> Subject: (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 that using
> FramedGroupBaseAddress in each client definition that the
> base address would have to be unique for each client? In
> other words you cannot do this--
>
> <Client 64.39.200.42>
> Secret
> DefaultRealm dialup.company.com
> NasType Ascend
> # This is the base address for Framed-Group = 0
> FramedGroupBaseAddress 64.39.201.1
> </Client>
>
> <Client 64.39.200.43>
> Secret
> DefaultRealm dialup.company.com
> NasType Ascend
> # This is the base address for Framed-Group = 0
> FramedGroupBaseAddress 64.39.201.1
> </Client>
>
> since it uses the port number on the NAS to determine the ip address?
>
> Instead, would it be more proper to use <AuthBy DYNADDRESS>
> and can I use it in conjunction with my <AuthBy DBFILE> statement?
>
> <Realm dialup.company.com>
> RewriteUsername tr/A-Z/a-z/
> RewriteUsername s/\@dialup\.company\.com//
> <AuthBy DBFILE>
> DefaultSimultaneousUse 1
> Filename %D/users
> </AuthBy>
> Also, can I assume that <AuthBy DYNADDRESS> will work with an
> Ascend NAS?
>
> Any help on this would be appreciated!!
>
> Frank
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
