(RADIATOR) RADIATOR Generates Vendor-Specific attributes when proxying RADIUS

[James Wiegand]

Hello,

I am seeing a situation where a request comes in and is forwarded off by an
Authby RADIUS clause, and the outgoing packet has Vendor-Specific
attributes not present in the incoming packet.  My customers are asking me
what these are and it is not obvious where they are coming from and how to
interpret them.

One thing I do notice is that the incoming request has the attribute/value
of Ascend-Handle-IPX: Handle-IPX-Server  when this happens. It this a
feature?  Are there other conditions when the proxied RADIUS request is
re-written implicitly?

Thanks,

Jim Wiegand, BSEE, MSE
Fiberlink Communications
215 793 6554


The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.


===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.