1

(5 replies, posted in Documentation)

YFi Hotspot Manager Beta-4

Hi All,

Just an update on YFi Hotspot Manager

Beta-4 is out today!
Lots of new features and improvements:

https://sourceforge.net/apps/trac/hotcakes/wiki/yfi_roadmap

Cheers

2

(5 replies, posted in Documentation)

YFi Hotspot Manager Beta-3

Hi All,

Just an update on YFi Hotspot Manager

Beta-3 has been released and includes the following improvements:

1.) Multiple language support
2.) Stats
3.) An alternative JSON log-in page for CoovaChilli which indicates the usage and stats, supporting multiple languages.
4.) Accounting and Billing

Regards

3

(5 replies, posted in Documentation)

Hi All,

Its been a while....

YFi Hotspot Manager Beta-1 (the new incarnation of Hotcakes Hotspot Manager) is now available for public consumption.

A total rewrite which uses the latest buzzword technologies.

Now you can.....
1.) Create Vouchers and export them to PDF or CSV.
2.) Vouchers has an expiry date, only start to count-down upon first log in.
3.) Batch voucher creation
4.) Realm creation - Access providers gets assigned to one or more realms.
5.) Permanent users who you can supply extra caps (Data or Time)
6.) Notify them about events EG Maintain work on the Week-end
7.) Notify them on their usage.
8.) Permanent users has their own log-in page to view their usage.
9.) Geared for large or small deployments

and GPL as before smile

You can grab Beta-1 here:

http://sourceforge.net/projects/hotcakes/

Cheers

4

(1 replies, posted in Chillispot Configuration)

Yes it is.

--coaport port
    UDP port to listen to for accepting radius disconnect requests.

--coanoipcheck
    If this option is given no check is performed on the source IP address of radius disconnect requests. Otherwise it is checked that radius disconnect requests originate from radiusserver1 or radiusserver2.

The standard port is --coaport 3799

You then send chillispot a POD message

http://wiki.freeradius.org/Packet_of_Disconnect


I've written a small perl script which you can pass arguments as to who and where to disconnect:

----
#!/usr/bin/perl

# print debug output? (0=no, 1=yes)
my $debug = 0;

use strict;

#my $username = "steve";
my ($rad_ip,$rad_secret,$username,$port) = @ARGV;


if ($rad_ip && $rad_secret && $username && $port ){

    system("echo \"User-Name = $username\" | radclient $rad_ip:$port 40 $rad_secret");
    exit;
}else{

    print "--------------------------------------------------\n";
    print "----Usage radpod <NAS Device's IP> <Shared Secret> <User To Disconnect> <Port NAS Device listens on for PoD Packest>---\n";
    print "--------------------------------------------------\n";

}

---

You are welcome to use it smile

5

(3 replies, posted in Radius Configuration)

Hi Paul

You can try this:

Be sure to define a 'Check Attribute' of 'Session-Timeout' when you make use of rlm_sqlcounter.
EG
Session-Timeout     :=    1200

you can then define a counter like this in the modules:

sqlcounter noresetcounter {
                counter-name = Session-Timeout
                check-name = Session-Timeout
                reply-name = Session-Timeout
                sqlmod-inst = sql
                key = User-Name
                reset = never
                query = "SELECT SUM(AcctSessionTime) FROM radacct WHERE UserName='%{%k}'"

}

Include it in the 'authorize {      }' section
EG 'noresetcounter'


rlm_sqlcounter will then take the check value defined and subtract the value of the SQL statement's result.

The newer versions of rlm_sqlcounter also lets you define the reply attribute, which can be handy to give users a data 'cap'.
It did prove to be buggy though on large values.

If you are lazy you could just grab a copy of Hotcakes, It already has these counters pre-defined and works 'out of the box'  smile

6

(5 replies, posted in Documentation)

Hi All,

Many thanks for bringing this site back.

Those who are looking for a Hotspot management solution are just in time for the new Beta-5.

Lots of new features, documentation included, and GPL naturally smile

New with this release
1.)Multi user levels (Admin, Cashier, Client)
2.)Client's own personal page.
3.)Realms

There needs to be a Check attribute 'Simultaneous-Use :=1' specified somewhere in your LDAP entry for the user.

Then in the radiusd.conf file is a section 'session'. You can either use a file ('radutmp') or a sql DB to do the checking (sql).

If you use the sql DB you have to specify the query in the sql's config file.
Are you only using LDAP and no 'hybrid' setup with a SQL db for accounting?

As far a I could determine is LDAP only used for authentication.