>Rudy Komsic wrote:
>>
>> we are running Quads on Netserver. we are using MPIP for interchassis
>> multilink protocol. to try this out, make sure you dial 1 chassis for
first
>> link then dial the second chassis and establish a connection. You will
notice
>> on the calls online you are connected once and when you hang up, you will
have
>> a port 6000 when you check the time online.
>
>In RadiusNT -x15 debug, you see an Accounting Start Packet for Port 6000
>and not a stop for it? If thas correct, then it definately would be a
>bug.
Actually what happens is this, let's say 2 MPP users connect to the system
both dialing the separate chassis. The first client connects, and his second
channel is connected via USR's MPIP (Multilink PPP Interchassis Protocol).
For the second channel, the authentication request comes from the 2nd chassis
but the accounting start record comes from the first chassis reporting it as
Port 6000. Now when the second person connects to the 2 chassis, the second
channel will report the same and what will occur within Radius is that the
first client's second channel lost connection (but his second channel is still
up) and starts the record for the second client's second channel on port 6000.
This seems like a bug with the MPIP Radius interaction. I am currently
talking with USR on this issue.
>
>> -----Original Message-----
>> From: Lamar Townsend <lamar@shuttle.com>
>> To: radiusnt@iea-software.com <radiusnt@iea-software.com>
>> Date: July 31, 1998 8:40 PM
>> Subject: RE: Multilink PPP with USR Chassis and RadiusNT/Emerald
>>
>> >I have not seen this problem. Are you running Quads or HyperDSPs,
>> >Netserver or HyperARCs? And what version of the code?
>> >
>> >
>> >Lamar Townsend
>> >VP Microgear Computers & Microgear.Net
>> >lamar@microgear.net
>> >
>> >
>> >
>> >
>> >
>> >Hmm... lately we have discovered a small problem with Multilink PPP and
>> >accounting features with connections. When a Client connects under the
>> >Multilink connection, it sometimes report Port 6000. This may be the port
>> >that the VPN connection between chassis where it will conduct the
>> >communications are conducted.
>> >Could this be a bug in the latest USR Chassis code?
>> >
>> >----
>> >Rudy Komsic
>> >President, Network Administrator - Cyberglobe Communications Inc.
>> >4996 Place de la Savane, Suite 200, Montreal, Quebec, H4P 1Z6
>> >Tel: (514)342-3883 Fax: (514)342-5139 E-Mail: rudyk@cyberglobe.net
>> >
>> >
>
>--
>Dale E. Reed Jr. (daler@iea-software.com)
>_________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.iea-software.com