> > Let's suppose that you want to limit access for some users calling on a
> > hunt group of 15 lines, and give another sort of access for users
> > calling a different number. having IP-port match it is extremely easy to
> > accomplish this....
>
> Excuse my ignorance, but what does the IP have to do with that?
> The phone line connects to the modem, which connects to the PORT.
> Therefore, the PORT is what you want to manage access of, NOT the IP.
> In your scenario, what about static IPs? Starts to fall short. :(
I was talking about routing a certain pool of modems to the Internet via
one connection, and the other one via another connection. Easily to do
with our CISCO holding our Internet links if we can assing a fixed IP
address per port. And don't tell me about filters and etc., CISCO is
working with IP addresses....
> I would think that adding the check of IP is more of a uneeded
> check, than anything useful, since you still have to check the
> NAS/Port combo as well.
I am not sure what you mean here. I am referring as restricting or
imposing different rules if the user xyz calls on one pool or another,
but both on the same PortMaster. And I am not interested in Portmaster
filter facilities, because they don't apply - I want to make this
decision on other systems, which are two or three networks away - if xyz
called a certain number, then he have this kind of access, if he called
the other number then this kind of access. And on that systems I am able
to process this by IP. And having a strict IP-port map is the only way it
works...
Best regards,
Cristian Gafton
-- -------------------------------------------------------------------- Cristian Gafton gafton@sorosis.ro Computers & Communications Center Network Administrator 35 Moara de Foc St., Iasi 6600, ROMANIA Tel: +40-32-252938 http://www.cccis.ro Fax: +40-32-252933 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ UNIX is user friendly. It's just selective about who its friends are.