2011-10-05 - Re: [GRASE-Hotspot] Some Questions

Header Data

From: tim storey <ts***s@yahoo.com>
Message Hash: 3d86af97a99ac1b675e00f4057cdb909c8e552dfe6bc6526caee3a2571c33d96
Message ID: <1317801574.97228.YahooMailNeo@web161421.mail.bf1.yahoo.com>
Reply To: <4E866059.3040700@gmail.com>
UTC Datetime: 2011-10-05 00:59:34 UTC
Raw Date: Wed, 05 Oct 2011 00:59:34 -0700

Raw message 

Hi Tim

I have tried from both the web interface and the config file, but it doesn't work for me either way. (Unless I leave an open browser session running surreptitiously ;)
I imagine my setup is different to most Grase operators in that I have it sitting in a VirtualBox VM and I installed it from a Live Ubuntu 11.04 disk as I do not have the server version...
Could any of these two somehow relate to my ish?

Regards,
Tim S.


________________________________
From: Tim White <ti***8@gmail.com>
To: GRASE Hotspot General Discussions <gr***t@lists.sourceforge.net>
Sent: Saturday, October 1, 2011 2:35 AM
Subject: Re: [GRASE-Hotspot] Some Questions


Hi Tim.

As I said in my previous email, Idle Timeout is set in the Coova
    Config page in the radmin interface. All settings in there override
    the ones in /etc/chilli so you'll need to change the "Default Idle
    Timeout" from 600 to what ever you want it in the web interface.

Hope that makes sense.

Tim

On 30/09/11 8:31 PM, tim storey wrote: 
I updated it directly in /etc/chilli/defaults and set it to 14400 (4 hours), but even after a reboot my clients are still timing out after 10 minutes.
>My work-around is to leave an open browser session running minimized on the desktop. That seems to fool coova/radius into thinking there is an active connection.
>
>
>On 29/09/11 02:23, tim white wrote:
>
>
>Idle timeout should already be in the Coova Config page as "Default Session Idle Timeout" which is set to 600 seconds (10 minutes). Can someone confirm if this isn't currently working correctly?
>
>Thanks
>
>Tim
>
>On 28/09/11 00:17, tim storey wrote: 
>
>>
>>
>>
>>1) Idle-Timeout
>>The idle timeout of active connections is very low (5 minutes?). I added the Idle-Timeout attribute to radgroupcheck, but it made no difference.
>>Is there another way to do this?
>>
>>
>
>------------------------------------------------------------------------------
>All the data continuously generated in your IT
            infrastructure contains a
>definitive record of customers, application performance,
            security
>threats, fraudulent activity and more. Splunk takes this
            data and makes
>sense of it. Business sense. IT sense. Common sense.
>http://p.sf.net/sfu/splunk-d2dcopy1
>_______________________________________________
>Grase-hotspot mailing list
>Gr***t@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
>
>
>
>
>------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
>
>
>_______________________________________________
Grase-hotspot mailing list Gr***t@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/grase-hotspot 

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Grase-hotspot mailing list
Gr***t@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grase-hotspot

Thread