> if (request->parent != NULL)
> reply = request->parent->reply;
> else
> reply = request->reply;
This is the key bit. If the request has a parent, then we update request->parent->reply, otherwise request->reply directly. Otherwise the attributes will be trapped inside the tunnelled EAP context (and it's not possible to surface them by tweaking the configuration, because there's no real support for fragmenting attributes across multiple AVPs).
If this doesn't make sense now, it will very shortly :-)
-- Luke
|