Hello Kai -
On Thu, 11 Nov 1999, Kai Schlichting wrote:
>
> Now a question to the sophisticated part of the audience:
> how does the Port-Limit apply in a multi-chassis situation ?
> My guess is: Radiator keeps track of it internally when it
> sees the reply-item, but does the terminal server care ?
> Does it care when an MPP connection is attempted, with one
> session coming into a different chassis ?
Very good point - and one of the reasons why we hesitate in deciding how to
handle Simultaneous-Use and Multi-Link PPP. If Radiator is to do this properly,
the concepts of NAS and SessionDatabase need to be revisited.
I am only familiar with how Cisco implements multi-link/multi-chassis PPP, and
that is through one of the NAS's acting as the "bundle manager", in other
words, each individual PPP stream can terminate on any NAS, but each PPP
stream is carried over L2F (or whatever equivalent) to one designated NAS that
actually handles the MPPP and the IP side of the connection.
In Radiator we are considering implementing a similar "virtual NAS" in
software, where we can mirror this sort of environment.
All of this begs the fundamental question, of course, of what *exactly* does
Simultaneous-Use mean in an MPPP context? And also as you have pointed out -
what does Port-Limit mean in a multi-chassis environment?
As you can see, it is not quite as straightforward as one could hope.....
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
