Inactivity time / 24hr per-IP addr time limit
Hi,
I have set the inactivity time to 15 min and 24hr per-IP addr to 120 minutes and I don´t get that to work.
After 120 minutes I can still connect but only for 15 minutes until I have to reload the page.
Does the 15 min inactivity override the 120 minutes per IP connection?
I thought that when being connected from my IP-addr I should not be able to connect for 24hr. (Is this from midnight to midnight or is it counting 24 hr from when I connect?)
What am I doing wrong?
73 de SA6BQZ Gunnar

Comments
The limits do not apply to connections made from the local network. That is, from computers on the same local network as the Kiwi (e.g. both have local IP addresses of 192.168.1.xxx).
If you have a Kiwi-2 try the serial number-based link, e.g. 2xxxx.proxy.kiwisdr.com. Because even from your local network the Kiwi considers this a connection "originating from" the Internet (because it is coming from the proxy server). Hence subject to the limits.
Hi,
This is only from external networks I notice this
. I know that connecting from my local network it will not work.
I can send you a pm with the address to my SDR now set to 15/120 and see if you get the same "issue".
//Gunnar
Btw, if you would like to test I can change the settings to 5/10
//Gunnar
Also send admin password so I can check log messages to see what might be wrong: support@kiwisdr.com
Thanks
Pm on its way :-)
//Gunnar
Well, I don't see anything wrong.
The inactivity timeout does not override the 24 hr limit. If I set the limits to 2 & 10 minutes respectively then "xx:xx act" is shown in the user tab until connected for more than 8 minutes. Then "xx:xx 24hr" is shown indicating the 24 hr limit is now the limiting factor.
After I get kicked because of exceeding the 24 hr limit (10 min) I get the password override panel, as expected. But no amount of reloading gets around that. Now if somehow your IP address changed to an entirely new one then yes you would start a new 24 hr timer. Like if you were using a cellphone and your IP was being changing quickly for some reason by your provider. How exactly were you making connections from outside your local network?
You Kiwi was using DDNS and not the proxy service so that didn't have anything to do with the problem. The other possibility, but unlikely, is that you reloaded across the once daily reset of the 24 hr IP address table flush which occurs at the same time the automatic software update does. About 01:25 UTC in the case of your Kiwi.
Hi John,
Thanks a million for your help. I will do some testing and get back to you next week.
Why this is so important to work is because I have connections from xxxxxx being connected for 15 to 20hr.
Maybe one of the reasons of this problem was that I did clear the user list!!? Is it from there the IP addresses are logged for setting the time?
Are you still connected as admin?
Thank you again and have a nice day down under or on the other side of the Atlantic.
//Gunnar
Sorry -- now disconnected from admin page.
The admin user tab doesn't affect the timeout mechanisms.
Have been testing and it works 100%
Time out after 15 min and kicked out after exceeding the 24 hr limit.
Two questions:
73 de SA6BQZ Gunnar
All well understood.
The only thing that I think should not be ignored when using the pw is the time limit. Many users connects and does something else, lunch, coffee..., and forgets to disconnect then timeout would be perfect :-)
But the entire point of giving a password is to not be timed out under any circumstances. This requirement mostly came from people wanting to do long-term recording on a fixed frequency. And were given an exemption password by the Kiwi owner/admin to do so.