[Adam <adam@xxxxxxxxxxxx>]

I had been wondering what the way ethereal handles higher
layers.

for example from rfc2869 (http://www.ietf.org/rfc/rfc2869.txt)
pg 32, 5.13.  EAP-Message,it says:

 String
      The String field contains EAP packets, as defined in [3].  If
      multiple EAP-Message attributes are present in a packet their
      values should be concatenated; this allows EAP packets longer than
      253 octets to be passed by RADIUS.

So it basically says that multiple Attribute-Value Pairs of EAP-Message
type in the same packet should be considered ONE EAP-Message.

But then we are dealing with virtual representation of data, not
the factual/physical layout of the packet.



On the very similar token. Once we go one level up, and go to EAP message
of type 0xd (13). That is the EAP/TLS glue layer, it in turn again specify
that the TLS/SSL packet might be fragmented using EAP/TLS glue layer and
span multiple packets.

so current "issues" would be:
	- multiple EAP-messages in radius packet need to be consolidated
	- EAP/TLS glue layer support is not there.
	- multiple EAP/TLS packets needs to be consolidated if needed.

and once this is done the packet-tls.c layer could be called on top of
that?

adam,
who beings to think he's looking at wrong place to view complete TLS
packet.

-- 
Adam
http://www.eax.com	The Supreme Headquarters of the 32 bit registers