No subject

So if you have a 60 min lease then it would be renewed every 30 mins.<br>
I&#39;m not sure of the exact state machine of most devices but I do know
from logs that most laptop&#39;s try to renew an existing (or previous) ip
address. I don&#39;t know what embedded devices (such as iphones etc) do.<b=
r></div></blockquote><div><br>Reallocation and renewal are different types =
of requests in a dhcp lease lifecycle. A renewal request would not require =
macauth processing, whereas - like initial allocation - a reallocation does=
 and should.<br>

=A0</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8=
ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div bgc=
olor=3D"#ffffff" text=3D"#000000">
What is the network topoligy, is coova-chilli running on an access
point
(such as with openwrt) or have you got a server with 1 or more AP&#39;s /
devices connected via a switch?<br></div></blockquote><div><br>Chilli on a =
Ubuntu server (VM&#39;d) with 94 AP&#39;s (DHCP forwarding active) across m=
any switches.<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-lef=
t: 1ex;">

<div bgcolor=3D"#ffffff" text=3D"#000000">
As for re-authing a session if that would be implemented I know I would
prefer it to be a configurable option (or at worse a compile time
option). Having EVERY DHCP request turn into a radius request could
cause a significant volume of traffic.<br clear=3D"all"></div></blockquote>=
</div><br>The reauth should only need to be additionally added to the reall=
ocation dhcp lease request, which would be a small percentage of total dhcp=
 requests.<br>

<br>-- <br>Cheers,<br>Jason<br>

--0016e68eeeddf074b80485553657--