Re: [1.8.1] Captive Portal - timeout settings with vouchers not required?
Niko <[email protected]> Mon, 20 Jan 2014 21:53:18 +1030
| Newsgroups | gmane.comp.security.firewalls.m0n0wall |
|---|---|
| Message-ID | <[email protected]> |
Ah yes, that makes sense, completely forgot about that. Thanks. so far m0n0wall seems to remove expired macs pretty reliably so I think a hard timeout safety net isn't required. Thanks again. On 20/01/2014 4:08 AM, Lee Sharp wrote: > On 01/19/2014 05:10 AM, Niko wrote: >> Hi all, >> >> 1.8.1 running smooth as silk here. Well done to developers and >> contributors. >> >> For those using vouchers with Captive Portal, is there any need to have >> a hard timeout configured? >> >> If I understand it correctly, the voucher system will remove the user >> from the users list at the expiration of the voucher, so theoretically a >> hard timeout will never be reached (unless hard time out is set to less >> than the voucher time limit). However, doing that would override the >> point of the voucher's time limit, so can be ruled out. >> >> Therefore, should the 'hard timeout' be set to blank for voucher >> configurations, or is it best, for example, if the voucher is 60 >> minutes, to set a hard timeout (e.g., 90 minutes) as a safety net? > > Remember that you can have vouchers and users at the same time. In > which case, you may, or may not want a hard timeout. I personally, > never user them and prefer idle timeouts. > > Lee > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > >