2016-08-22 - Re: [GRASE-Hotspot] Re: Monitoring performance - troubleshooting
Header Data
From: Timothy White <ti***8@gmail.com>
Message Hash: 2ddc3780c0d4e29771739a191d488c158dffeeb63e8cf0434e9b259cf726a627
Message ID: <CAESLx0Jmw8w=9qm3M9YrF+4kU2pA8wisPVcUtmN8jdY4+He83w@mail.gmail.com>
Reply To: <34e4f690-f9e7-4d09-9759-36e07d894a78@grasehotspot.org>
UTC Datetime: 2016-08-22 16:25:06 UTC
Raw Date: Tue, 23 Aug 2016 09:25:06 +1000
Raw message
Hi Glyn
Your description of Free access for 1 hour, then the account expires an
hour later and they can log back in, doesn't match what you want. An
expired account means they are locked out, no log back in. It's finished.
It sounds like what you actually want is them to be able to use 1 hour ever
2 hours?
If you want a free account to be able to log back in in the future, you
can't use default time/data limits, or expiry, as these will apply to the
account for it's lifetime (which isn't until it expires, it's until it's
deleted). What you need to be looking at is recurring data/time limits, and
bandwidth limits.
To give you an example, at a cafe that's running the hotspot, they give
their clients 30 minutes a day. We also use a bandwidth limit to throttle
their speed. However, we don't set a data limit, as with the bandwidth
limit, and the time limit per day, we are already effectively giving them a
data limit (bandwidth x 30 minutes = total data per day they can use).
Unfortunately, for your use case, there currently isn't a recurring
timelimit that fits your need. IIRC, the limits are per hour, per day, per
month (maybe per week?). The best way with these existing limits would be
to give them 30 minutes each hour. Alternatively, be generous and give them
say 3 hours a day. I can't see too many people who would come to the pub in
the morning, use 3 hours, and come back that afternoon and want more.
Something like
[image: Inline image 1]
Regarding the performance issues. Unfortunately I don't use a Raspberry Pi
or similar with more than 1 or 2 WiFi connections. Make sure you do some
tests with iperf to see what bandwidth you can actually push through it. Do
tests both from the pi to a destination on the internet, and from a WiFi
client to the Pi.
Regards
Tim
On Mon, Aug 22, 2016 at 10:21 PM, Glyn <bo***1@gmail.com> wrote:
> The screenshot is wrong. It was set for an expiry of "2 hours" but no
> accounts got expired because I believe it should have been "+2 hours".
>
> The idea is free access is for 1 hour, accout expires an hour later and
> they can log back in. Once I have the performance issues bottomed out this
> can be made more generous....
>
> --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gr***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at https://groups.google.com/a/
> grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit https://groups.google.com/a/
> grasehotspot.org/d/msgid/grase-hotspot/34e4f690-f9e7-
> 4d09-9759-36e07d894a78%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/34e4f690-f9e7-4d09-9759-36e07d894a78%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>
Thread
- Return to August 2016
- Return to October 2016
-
Return to December 2016
- Return to “Glyn <bo***1@gmail.com>”
- Return to “wegejo <jo***r@jwer.de>”
- Return to “Hotspotuser <jo***s@algardata.pt>”
-
Return to “Timothy White <ti***8@gmail.com>”
- 2016-08-22 (Mon, 22 Aug 2016 05:01:03 -0700) - Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>
- 2016-08-22 (Mon, 22 Aug 2016 05:21:34 -0700) - Re: Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>
- 2016-08-22 (Tue, 23 Aug 2016 09:25:06 +1000) - Re: [GRASE-Hotspot] Re: Monitoring performance - troubleshooting - Timothy White <ti***8@gmail.com>
- 2016-08-26 (Fri, 26 Aug 2016 12:04:58 -0700) - Re: Monitoring performance - troubleshooting - wegejo <jo***r@jwer.de>
- 2016-08-29 (Mon, 29 Aug 2016 01:35:50 -0700) - Re: Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>
- 2016-08-26 (Fri, 26 Aug 2016 02:35:55 -0700) - Re: Monitoring performance - troubleshooting - Hotspotuser <jo***s@algardata.pt>
- 2016-08-26 (Fri, 26 Aug 2016 11:16:42 -0700) - Re: Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>
- 2016-10-28 (Fri, 28 Oct 2016 05:44:02 -0700) - Re: Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>
- 2016-10-30 (Sun, 30 Oct 2016 17:32:11 +1000) - Re: [GRASE-Hotspot] Re: Monitoring performance - troubleshooting - Timothy White <ti***8@gmail.com>
- 2016-10-30 (Sun, 30 Oct 2016 06:49:50 -0700) - Re: [GRASE-Hotspot] Re: Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>
- 2016-10-30 (Sun, 30 Oct 2016 17:32:11 +1000) - Re: [GRASE-Hotspot] Re: Monitoring performance - troubleshooting - Timothy White <ti***8@gmail.com>
- 2016-12-08 (Thu, 08 Dec 2016 05:52:58 -0800) - Re: Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>
- 2016-12-09 (Sat, 10 Dec 2016 07:07:25 +1000) - Re: [GRASE-Hotspot] Re: Monitoring performance - troubleshooting - Timothy White <ti***8@gmail.com>
- 2016-08-22 (Mon, 22 Aug 2016 05:21:34 -0700) - Re: Monitoring performance - troubleshooting - Glyn <bo***1@gmail.com>