Well, it is not adding new fields but putting some data in the data fields of those messages that allow to do that, e.g., put a certain value in the EAP Type Data field:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Code | Identifier | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Type-Data ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Enrique de la Hoz wrote:Huh? Why would you ever do that?
> We are trying to develop a module to make possible to add extra
> information to EAP Messages.
The EAP protocol is well defined. Adding "extra" information to it is
like adding "extra" data to IP packets. It will be ignored... at best.
What are you trying to do, and why?
> We are employing rlm_perlo module. Up to
> now, we have been able to add new EAP-Message attributes to the RADIUS
> response packets but we cannot figure out how to modify the current
> EAP-Message already addedd. It is assumed (from RFC 3579) that multiple
> EAP Message attributes will be concatenated to form a single EAP Packet
> but the thing is that we do not receive the added information in our
> supplicant.
>
> Two questions arise:
> 1) Is it possible to modify EAP-Message attributes from perl modules?
> 2) If not, should we go through a per EAP-athentication method C source
> code modification?
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html