David C. Troy [EMAIL PROTECTED] wrote:
OK, this seems like the right overall direction, but one question -- in
the 'huntgroups' documentation, it looks like a Huntgroup is defined
exclusively by the use of the NAS-IP-Address and NAS-Port-ID attributes.
The huntgroups are defined by whatever
David C. Troy [EMAIL PROTECTED] wrote:
Actually I should clarify. If I understand you correctly, I would need to
put in an entry for each client NAS box, rather than just each client
PROXY box.
No, no, no, no.
I don't know all the NAS IP's and they could change.
Exactly.
Can I do
Actually I should clarify. If I understand you correctly, I would need to
put in an entry for each client NAS box, rather than just each client
PROXY box.
No, no, no, no.
I don't know all the NAS IP's and they could change.
Exactly.
Can I do this based on the Proxy IP only?
All:
I have the following situation --
1) Provider A uses PAP and doesn't want Ascend-Data-Filters
2) Provider B uses PAP and DOES want Ascend-Data-Filters
3) Provider C uses CHAP and doen't want Ascend-Data-Filters
4) They all want to use ports 1645/1646
Everything is authenticated from
David C. Troy [EMAIL PROTECTED] wrote:
I have the following situation --
1) Provider A uses PAP and doesn't want Ascend-Data-Filters
2) Provider B uses PAP and DOES want Ascend-Data-Filters
3) Provider C uses CHAP and doen't want Ascend-Data-Filters
4) They all want to use ports
Alan -- Thanks for the help. One further bit of clarification --
the Providers A, B, C each have about 10-20 proxy boxes. I would prefer
to define them as classes of proxies rather than have to set up individual
profiles in the 'users' file.
Is there any reasonable way to do this, or am I
