[RADIATOR] Radiator Version 4.13 released

[Hartmaier Alexander]

On 2014-05-05 13:53, Heikki Vatiainen wrote:
> On 05/02/2014 03:24 PM, Hartmaier Alexander wrote:
>
>> I've configured the outer PEAP Handler with EAPTLS_MaxFragmentSize 1350
>> and removed the value 1250 (1300 which we use for wired dot1x seems to
>> be too large) from the inner TLS handler which makes it fail the same
>> way as when configuring 1300.
>> Is the other value too large or how is the inner size calculated?
> The inner size simply uses the outer fragment size minus 40 bytes. It
> appears this number is not large enough for all cases then.
>
> The correct number in your case is something between 1250 and 1300 when
> you have outer fragment size 1350? That is, when you have 1350 as outer
> fragment size, 1250 works but 1300 does not.
So what you're saying is that 1350 for the outer results in an inner
calcuated one of 1310 bytes which is too large?

Which fragment size should be configured, the outer or the inner one?
If the inner is calculated from the outer I shouldn't configure the
inner one but simply reduce the outer one until it works?

The value is the number of bytes the EAP messages are split into and
transmitted via the EAP-Message radius attribute, correct?
So the number is depended on how much bytes all other radius attributes
consume from the MTU which should be 1500 for both wired and wireless in
our case?


>
> Thanks,
> Heikki
>
BR Alex


*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien
Handelsgericht Wien, FN 79340b
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
Notice: This e-mail contains information that is confidential and may be privileged.
If you are not the intended recipient, please notify the sender and then
delete this e-mail immediately.
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*