Note the recent thread where this was discussed. Trumpet has a well known
bug and it sometimes reuses an old IP from a previous session, or some IP
the user has set. During PPP negotiation, which you can see with debug
flags, it lies and agress to the one the PM assigns - but them uses the other
one anyway. This is a clear violation of the protocol on their part.
>Normally trumpet would come back with MY IP ADDRESS IS, but in this case,
>depending on which time you tried, it either DID NOT, or it would come
>back with a different address that wasn't 56.
Sounds just like the bug. Bad news - nothing you can do from your end, the
user has to clear the IP out of Trumpet. Sounds like they have 2.0b, 2.1f
supposedly fixed this.
>in. It would start to assign the IP address, gripe about an "unknown
>request type 61" send an ACK and then repeat a couple of steps before
Which means you never updated the dictionary file to handle the latest
ComOS as per the release notes. The PM is sending a new field in the
packets and RADIUS has no idea what it is until the dictionary is updated
and the daemon restarted.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566