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

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: d8d9724f8739df7665f0f44cdbc3271335e994c4379739936010a711caf12e1b
Message ID: <CAESLx0+5vPyrB7HQKu-bcaaiG_HH4RspcS4U=r6RPaYzXjWoFw@mail.gmail.com>
Reply To: <1317899892.58166.YahooMailNeo@web161406.mail.bf1.yahoo.com>
UTC Datetime: 2011-10-06 19:19:53 UTC
Raw Date: Fri, 07 Oct 2011 12:19:53 +1000

Raw message 

Very odd. While getting those values, what is the contents of
/etc/chilli/local.conf ?
Also, I released a new chilli version yesterday that /SHOULD/ fix both
the error message in syslog, and the default timeout. It'll probably
overwrite your /etc/chilli/config but then try setting default timeout
in the web interface to 0 and see what happens. (And remove all the
rad(group)reply options you've added for timeout to see what happens).

Thanks

Also, I don't mind if the fix is messy, I can look at the best way to
add it. I'm working on a plugin system atm so it might be possible to
have it as an add in.

Tim

On Thu, Oct 6, 2011 at 9:18 PM, tim storey <ts***s@yahoo.com> wrote:
> I am now using 0 as the idle timeout value.
> /var/log/syslog is filled with the following:
> - coova-chilli[#####]: net.c: 114: 13 (Permission denied)
> ioctl(SIOCSIFFLAGS) failed
> This repeats 2 or 3 times per second, every second.
> The response to the chilli_query command is:
> User 0
>  MAC:                   xx-xx-xx-xx-xx-xx
>  IP Address:            10.1.0.248
>  Session ID:            4e8d878e00000024
>  Username:              customerticketxxx
>  Duration / Max:        942/30539424
>  Idle / Max:            0/21600
>  Input Octets / Max:    34475198/0
>  Output Octets / Max:    2342991/0
>  Max Total Octets:      488777164
>  Using swapoctets:      0
>  % / Max Up Bandwidth:  0%/1024000
>  % / Max Down Bandwidth: 18%/1024000
>  Original URL:          http://www.google.com/search
> User 1
>  MAC:                    xx-xx-xx-xx-xx-xx
>  IP Address:            10.1.0.236
>  Session ID:            4e8d65c30000000a
>  Username:              adminticketxxx
>  Duration / Max:        9600/27092082
>  Idle / Max:            23/600
>  Input Octets / Max:    3708308/0
>  Output Octets / Max:    1061530/0
>  Max Total Octets:      0
>  Using swapoctets:      0
>  % / Max Up Bandwidth:  0%/0
>  % / Max Down Bandwidth: 0%/0
>  Original URL:          http://www.google.co.za/
> I snipped out the other users for simplicity's sake. The idle clearly shows
> as being 21600 or 600, even though I have just changed it from 14400 (4
> hours) to 0.
> 21600 is the value I originally set via radgroupreply with the attribute of
> "Idle-Timeout"
> The ticket inheriting the default value of 600 was not listed in
> radgroupreply.
> (I had to remove the first and last curly brackets to make the command work
> for me via sh.)
> My solution for now will be to simply set 0 as the override value in
> radgroupreply and that should permanently fix it for me.
> Thanks for all your effort in resolving this.
> Let me know what to do about the /var/log/syslog/ error message.
> Regards,
> Tim S
> PS I haven't forgotten about the billing add-on I promised you, I'm just
> trying to clean it up a little as it was a very quick fix...
>
> ________________________________
> From: Timothy White <ti***8@gmail.com>
> To: GRASE Hotspot General Discussions <gr***t@lists.sourceforge.net>
> Sent: Wednesday, October 5, 2011 10:13 AM
> Subject: Re: [GRASE-Hotspot] Some Questions
>
> On Wed, Oct 5, 2011 at 5:59 PM, tim storey <ts***s@yahoo.com> wrote:
>> 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?
>
> Nether of these SHOULD effect it. I've finally got my test hardware
> running again, so I'll look at testing it. What value are you setting
> in the web interface for the timeout? And have a look in the logs
> (/var/log/syslog) for any chilli error mesages.
>
> Also, run the following command with a user logged in (run it on the
> server) and show me the output. (You may need to run it as root, or
> with sudo)
>
> Thanks
>
> Tim
> p.s. It appears that setting an idle timeout of 0 should give you
> unlimited, so no timeout
>
> chilli_query list | awk '{
>           ($5 == 1) {
>             print "User " i++
>             print " MAC:                    " $1
>             print " IP Address:            " $2
>             print " Session ID:            " $4
>             print " Username:              " $6
>             print " Duration / Max:        " $7
>             print " Idle / Max:            " $8
>             print " Input Octets / Max:    " $9
>             print " Output Octets / Max:    " $10
>             print " Max Total Octets:      " $11
>             print " Using swapoctets:      " $12
>             print " % / Max Up Bandwidth:  " $13
>             print " % / Max Down Bandwidth: " $14
>             print " Original URL:          " $15
>           }
>         }'
>
> ------------------------------------------------------------------------------
> 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 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
>
>

Thread