grasehotspot / grase-www-portal Goto Github PK

Grase WWW Portal (Main Package)

Makefile 0.13% Shell 0.57% PHP 66.25% CSS 1.93% JavaScript 13.94% C 1.78% Smarty 9.54% Dockerfile 0.06% SCSS 0.23% Twig 5.58%

hotspot portal freeradius captive-portal coovachilli php

grase-www-portal's People

Contributors

Stargazers

Watchers

Forkers

gpboon kazi308 kleisauke bittorf pasichnichenko laudarch alexschomb kralan debjit digideskio ark74 sirjohnpenguin philawyer yayato jbcanas danimaxi rstrich saberleon262

grase-www-portal's Issues

Restrict groups by Time of Day (Trac #33)

Using RADIUS Login-Time and rlm_logintime (http://wiki.freeradius.org/Rlm_logintime) we can restrict accounts to only be able to login during certain times of day.

Migrated from http://trac.grasehotspot.org/ticket/33

{
    "status": "closed", 
    "changetime": "2012-03-09T02:33:17", 
    "description": "Using RADIUS Login-Time and rlm_logintime (http://wiki.freeradius.org/Rlm_logintime) we can restrict accounts to only be able to login during certain times of day.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1331260397618708", 
    "component": "Admin Interface", 
    "summary": "Restrict groups by Time of Day", 
    "priority": "major", 
    "keywords": "time, login", 
    "version": "3.4", 
    "time": "2011-10-17T00:50:12", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

Bandwidth limits manual input (Trac #15)

Currently bandwidth limits are in a drop down box as it helps prevent strange bandwidth limits being input. Give ability to add more limits to this dropdown box easily.

Migrated from http://trac.grasehotspot.org/ticket/15

{
    "status": "new", 
    "changetime": "2011-08-12T04:13:08", 
    "description": "Currently bandwidth limits are in a drop down box as it helps prevent strange bandwidth limits being input. Give ability to add more limits to this dropdown box easily.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1313122388670933", 
    "component": "Admin Interface", 
    "summary": "Bandwidth limits manual input", 
    "priority": "trivial", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-12T04:13:08", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "defect"
}

Export usernames and passwords to excel or other file format (Trac #40)

Ability to export usernames - passwords (per group, per user, etc) in different formats (excel, cvs, txt)

Migrated from http://trac.grasehotspot.org/ticket/40

{
    "status": "accepted", 
    "changetime": "2012-09-03T06:00:54", 
    "description": "Ability to export usernames - passwords (per group, per user, etc) in different formats (excel, cvs, txt)", 
    "reporter": "tomas213 _", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1346652054896073", 
    "component": "Admin Interface", 
    "summary": "Export usernames and passwords to excel or other file format", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-12-01T09:21:14", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "defect"
}

Limit number of simultaneous use users (Trac #3)

Currently you can ether allow or prevent simultaneous use. Add an option to set a number of simultaneous use users permitted. (i.e. allow 2 simultaneous logins for an account)

Migrated from http://trac.grasehotspot.org/ticket/3

{
    "status": "new", 
    "changetime": "2011-08-11T05:18:31", 
    "description": "Currently you can ether allow or prevent simultaneous use. Add an option to set a number of simultaneous use users permitted. (i.e. allow 2 simultaneous logins for an account)", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1313039911234529", 
    "component": "Admin Interface", 
    "summary": "Limit number of simultaneous use users", 
    "priority": "trivial", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-11T05:18:31", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

User expiration after first login (Trac #39)

When the user gets used for the first time a countdown starts which will cause the user to be expired 'x' days form first log-in
This yould be useful for visitors

Migrated from http://trac.grasehotspot.org/ticket/39

{
    "status": "accepted", 
    "changetime": "2012-10-18T00:31:58", 
    "description": "When the user gets used for the first time a countdown starts which will cause the user to be expired 'x' days form first log-in\nThis yould be useful for visitors", 
    "reporter": "Vedran84", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1350520318767444", 
    "component": "Coova Chilli", 
    "summary": "User expiration after first login", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-11-11T17:40:36", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

Move deletion confirm to javascript alert (Trac #19)

Rather than having them type "Yes, I want to delete this user", show a javascript alter box asking for confirmation.

Migrated from http://trac.grasehotspot.org/ticket/19

{
    "status": "closed", 
    "changetime": "2011-08-26T00:00:16", 
    "description": "Rather than having them type \"Yes, I want to delete this user\", show a javascript alter box asking for confirmation.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1314316816004652", 
    "component": "Admin Interface", 
    "summary": "Move deletion confirm to javascript alert", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-25T23:36:08", 
    "milestone": "3.5", 
    "owner": "tim", 
    "type": "defect"
}

Offsite Backups (Trac #7)

Make it easy for each site to configure where offsite backups are sent and how often.

Migrated from http://trac.grasehotspot.org/ticket/7

{
    "status": "new", 
    "changetime": "2012-09-30T15:36:08", 
    "description": "Make it easy for each site to configure where offsite backups are sent and how often.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1349019368506433", 
    "component": "Admin Interface", 
    "summary": "Offsite Backups", 
    "priority": "minor", 
    "keywords": "backups", 
    "version": "3.4", 
    "time": "2011-08-11T05:44:09", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "enhancement"
}

Ability to print a group usernames and passwords any time (Trac #41)

Ability to print a group usernames and passwords any time

Migrated from http://trac.grasehotspot.org/ticket/41

{
    "status": "accepted", 
    "changetime": "2012-02-06T13:47:12", 
    "description": "Ability to print a group usernames and passwords any time", 
    "reporter": "tomas213 _", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1328536032327187", 
    "component": "Admin Interface", 
    "summary": "Ability to print a group usernames and passwords any time", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-12-01T09:23:35", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

5Gb ticket display (Trac #38)

All 5 Gb tickets are shown as being 4 Gb in size on the mini screen.
I imagine that all tickets > 4 Gb would be affected this way.

Note: the status and admin screens reflect the size correctly!

Migrated from http://trac.grasehotspot.org/ticket/38

{
    "status": "accepted", 
    "changetime": "2012-10-04T07:08:02", 
    "description": "All 5 Gb tickets are shown as being 4 Gb in size on the mini screen.\nI imagine that all tickets > 4 Gb would be affected this way.\n\nNote: the status and admin screens reflect the size correctly!", 
    "reporter": "https://me.yahoo.com/a/jFrNJGoip97_RO80rg7fkd5a4n4-#65769", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1349334482750394", 
    "component": "Admin Interface", 
    "summary": "5Gb ticket display", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-11-08T09:42:06", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "defect"
}

Network settings aren't always applied (Trac #45)

Due to MySQL not always running before chilli/dnsmasq, attempting to get the Network Settings (which are stored in MySQL) via the networksettings.dnsmasq.php script will fail and cause odd behaviour.

Need to add error checking to the script return, and make chilli only use the /etc/dnsmasq.d/01-grasehotspot file

Migrated from http://trac.grasehotspot.org/ticket/45

{
    "status": "closed", 
    "changetime": "2012-01-23T22:28:24", 
    "description": "Due to MySQL not always running before chilli/dnsmasq, attempting to get the Network Settings (which are stored in MySQL) via the networksettings.dnsmasq.php script will fail and cause odd behaviour.\n\nNeed to add error checking to the script return, and make chilli only use the /etc/dnsmasq.d/01-grasehotspot file", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1327357704152232", 
    "component": "Other Backend", 
    "summary": "Network settings aren't always applied", 
    "priority": "critical", 
    "keywords": "network settings, chilli, dnsmasq, mysql", 
    "version": "3.6", 
    "time": "2012-01-22T23:46:47", 
    "milestone": "3.7", 
    "owner": "tim", 
    "type": "defect"
}

Ability to upload any image as a logo (Trac #18)

Remove restrictions on logo upload. Don't overwrite the grase logo file, upload and modify css/html to point to new logo.

Migrated from http://trac.grasehotspot.org/ticket/18

{
    "status": "new", 
    "changetime": "2011-09-08T22:26:30", 
    "description": "Remove restrictions on logo upload. Don't overwrite the grase logo file, upload and modify css/html to point to new logo.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1315520790579544", 
    "component": "Admin Interface", 
    "summary": "Ability to upload any image as a logo", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-25T23:34:47", 
    "milestone": "", 
    "owner": "tim", 
    "type": "enhancement"
}

Change network settings from GRASE Interface (Trac #16)

We need to be able to change network settings from the web interface. This needs to include DNS settings, and ip addresses/netmasks.

Migrated from http://trac.grasehotspot.org/ticket/16

{
    "status": "closed", 
    "changetime": "2011-10-10T05:49:41", 
    "description": "We need to be able to change network settings from the web interface. This needs to include DNS settings, and ip addresses/netmasks.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1318225781609439", 
    "component": "Other Backend", 
    "summary": "Change network settings from GRASE Interface", 
    "priority": "major", 
    "keywords": "dns, network, ip address, dnsmasq", 
    "version": "3.4", 
    "time": "2011-08-22T06:04:59", 
    "milestone": "3.6", 
    "owner": "tim", 
    "type": "defect"
}

Activate tickets on first use (Trac #9)

Allow tickets to be created without an expiry, that can be activated on first use at the splash screen or when they login.
Possibly with a runner script for first login, otherwise with an "activate ticket" link for manual activation and maybe password changing and information display?

Migrated from http://trac.grasehotspot.org/ticket/9

{
    "status": "new", 
    "changetime": "2011-08-11T05:49:21", 
    "description": "Allow tickets to be created without an expiry, that can be activated on first use at the splash screen or when they login.\nPossibly with a runner script for first login, otherwise with an \"activate ticket\" link for manual activation and maybe password changing and information display?", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1313041761820625", 
    "component": "Splash Screens", 
    "summary": "Activate tickets on first use", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-11T05:49:21", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "enhancement"
}

Still some mysql_x functions (Trac #48)

Find all mysql_x functions (i.e. mysql_real_escape_string) and migrate to MDBD functions.

Migrated from http://trac.grasehotspot.org/ticket/48

{
    "status": "new", 
    "changetime": "2012-01-24T00:41:53", 
    "description": "Find all mysql_x functions (i.e. mysql_real_escape_string) and migrate to MDBD functions.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1327365713932255", 
    "component": "Admin Interface", 
    "summary": "Still some mysql_x functions", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2012-01-24T00:41:53", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "defect"
}

Antivirus domains in UAMDOMAIN (Trac #29)

Now we can customise uamdomain via the interface, we need to remove the hard coded domains from the config files.

Migrated from http://trac.grasehotspot.org/ticket/29

{
    "status": "closed", 
    "changetime": "2011-10-10T05:44:59", 
    "description": "Now we can customise uamdomain via the interface, we need to remove the hard coded domains from the config files.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1318225499531326", 
    "component": "Coova Chilli", 
    "summary": "Antivirus domains in UAMDOMAIN", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-09-08T20:44:52", 
    "milestone": "3.6", 
    "owner": "tim", 
    "type": "defect"
}

Machine account editing broken (Trac #21)

Machine account's can't be edited, not even comment.

Migrated from http://trac.grasehotspot.org/ticket/21

{
    "status": "closed", 
    "changetime": "2011-09-28T01:55:54", 
    "description": "Machine account's can't be edited, not even comment.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1317174954798895", 
    "component": "Admin Interface", 
    "summary": "Machine account editing broken", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-25T23:58:27", 
    "milestone": "3.5", 
    "owner": "tim", 
    "type": "defect"
}

Investigate UTF8 .vs. latin1 in MySQL (Trac #47)

Currently we store data in latin1 in MySQL. Given that we are an international project, and that templates and such should be using utf8, we need to look at converting everything to utf8, including the database tables

Migrated from http://trac.grasehotspot.org/ticket/47

{
    "status": "new", 
    "changetime": "2013-06-22T13:58:08", 
    "description": "Currently we store data in latin1 in MySQL. Given that we are an international project, and that templates and such should be using utf8, we need to look at converting everything to utf8, including the database tables", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1371909488789986", 
    "component": "Other Backend", 
    "summary": "Investigate UTF8 .vs. latin1 in MySQL", 
    "priority": "major", 
    "keywords": "utf8, mysql", 
    "version": "3.6", 
    "time": "2012-01-24T00:17:43", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "enhancement"
}

Group limits don't work (Trac #36)

Group limits (i.e. max-octets) are being stored in the wrong table (reply instead of check) and so are useless.
It also appears that user check items can't overrule group check items, so user settings will be overridden by group (so document the difference)

Migrated from http://trac.grasehotspot.org/ticket/36

{
    "status": "closed", 
    "changetime": "2011-11-08T01:39:43", 
    "description": "Group limits (i.e. max-octets) are being stored in the wrong table (reply instead of check) and so are useless.\nIt also appears that user check items can't overrule group check items, so user settings will be overridden by group (so document the difference)", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1320716383339841", 
    "component": "Coova Chilli", 
    "summary": "Group limits don't work", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-11-07T22:41:52", 
    "milestone": "3.7", 
    "owner": "tim", 
    "type": "defect"
}

Logs if someone tries to login with wrong password or username (Trac #43)

Are there any logs that can show me if anyone tries to login with a false username or password?
Blocking the user he enters wrong password or username for 3 times for 10 minutes, would be great too.

Here is the link you asked to include about the logs :

http://wiki.freeradius.org/FAQ#How+do+I+log+failed+login+attempts+in+a+SQL+database%3F

Migrated from http://trac.grasehotspot.org/ticket/43

{
    "status": "accepted", 
    "changetime": "2012-06-29T23:29:34", 
    "description": "Are there any logs that can show me if anyone tries to login with a false username or password?\nBlocking the user he enters wrong password or username for 3 times for 10 minutes, would be great too.\n\nHere is the link you asked to include about the logs : \n\nhttp://wiki.freeradius.org/FAQ#How+do+I+log+failed+login+attempts+in+a+SQL+database%3F", 
    "reporter": "tomas213 _", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1341012574487512", 
    "component": "Admin Interface", 
    "summary": "Logs if someone tries to login with wrong password or username", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-12-08T08:58:15", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "enhancement"
}

Splash mode only (Trac #11)

Display Terms and Conditions, require user to click I Agree then allow access.
Ether auto create an account based on mac address and login them in, or look at splash only coova chilli.

Migrated from http://trac.grasehotspot.org/ticket/11

{
    "status": "new", 
    "changetime": "2011-10-01T01:03:54", 
    "description": "Display Terms and Conditions, require user to click I Agree then allow access.\nEther auto create an account based on mac address and login them in, or look at splash only coova chilli.", 
    "reporter": "tim", 
    "cc": "Kalle, O, Korhonen", 
    "resolution": "", 
    "_ts": "1317431034844369", 
    "component": "Splash Screens", 
    "summary": "Splash mode only", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-11T05:54:37", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "enhancement"
}

iOS problems logging in (Trac #1)

iOS devices have problems logging in. It has been difficult to narrow down the cause, as it has been reported to effect iOS 4 devices and not 3, and visa versa.

Possible solution is to code Mobile login screens for all mobile devices that relies less on javascript (and doesn't have popup status windows)

Migrated from http://trac.grasehotspot.org/ticket/1

{
    "status": "accepted", 
    "changetime": "2013-03-18T16:52:18", 
    "description": "iOS devices have problems logging in. It has been difficult to narrow down the cause, as it has been reported to effect iOS 4 devices and not 3, and visa versa.\n\nPossible solution is to code Mobile login screens for all mobile devices that relies less on javascript (and doesn't have popup status windows)", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1363625538896024", 
    "component": "Splash Screens", 
    "summary": "iOS problems logging in", 
    "priority": "major", 
    "keywords": "iOS, login, login form, iPad, iPhone, apple", 
    "version": "3.4", 
    "time": "2011-08-11T05:14:18", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "defect"
}

Make Squid/Dansguardian aware of usernames/groups (Trac #37)

Resurrect the external_acl helpers for resolving ip to username, and username to group, so squid can do filtering (and logging) based on username and group.

Migrated from http://trac.grasehotspot.org/ticket/37

{
    "status": "new", 
    "changetime": "2011-11-08T01:37:48", 
    "description": "Resurrect the external_acl helpers for resolving ip to username, and username to group, so squid can do filtering (and logging) based on username and group.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1320716268033904", 
    "component": "Filtering/Proxy", 
    "summary": "Make Squid/Dansguardian aware of usernames/groups", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-11-08T01:37:48", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

Feature Request : Add real time transfert speed and average speed (Trac #22)

In the monitoring sessions of the admin gui add coloumn with actual speed in k/sec and an average speed like by hour by day ...

Migrated from http://trac.grasehotspot.org/ticket/22

{
    "status": "accepted", 
    "changetime": "2013-01-29T10:38:09", 
    "description": "In the monitoring sessions of the admin gui add coloumn with actual speed in k/sec and an average speed like by hour by day ... ", 
    "reporter": "Evils_1", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1359455889675982", 
    "component": "Admin Interface", 
    "summary": "Feature Request : Add real time transfert speed and average speed", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-26T16:41:32", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

PDF Tickets Settings Page (Trac #49)

Need settings page to customise the PDF printing.
Select label page (i.e. Avery xyz) for predefined labels or input custom settings for you own label layout.
Allow turning on and off different label aspects, like SSID, Group, Expiry etc.

Migrated from http://trac.grasehotspot.org/ticket/49

{
    "status": "new", 
    "changetime": "2012-01-28T00:32:01", 
    "description": "Need settings page to customise the PDF printing.\nSelect label page (i.e. Avery xyz) for predefined labels or input custom settings for you own label layout.\nAllow turning on and off different label aspects, like SSID, Group, Expiry etc.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1327710721493604", 
    "component": "Admin Interface", 
    "summary": "PDF Tickets Settings Page", 
    "priority": "major", 
    "keywords": "pdf", 
    "version": "3.6", 
    "time": "2012-01-28T00:32:01", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

Add timelimits (Trac #30)

Make timelimits and assigned cost (also no cost) configurable: add, change and delete. Currently they are hardcoded, better transfer it to the settings.

Migrated from http://trac.grasehotspot.org/ticket/30

{
    "status": "accepted", 
    "changetime": "2013-04-22T11:59:56", 
    "description": "Make timelimits and assigned cost (also no cost) configurable: add, change and delete. Currently they are hardcoded, better transfer it to the settings.", 
    "reporter": "https://me.yahoo.com/a/jcW92BMmtphxgh1n6Vt6PttrSw--#a9aa2", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1366631996735862", 
    "component": "Admin Interface", 
    "summary": "Add timelimits", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-09-08T21:49:58", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "enhancement"
}

Bandwidth limit per User (Trac #12)

Currently bandwidth limits are per group, need to be able to set this per user.

Migrated from http://trac.grasehotspot.org/ticket/12

{
    "status": "accepted", 
    "changetime": "2012-12-14T04:33:47", 
    "description": "Currently bandwidth limits are per group, need to be able to set this per user.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1355459627147987", 
    "component": "Admin Interface", 
    "summary": "Bandwidth limit per User", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-12T03:40:29", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "defect"
}

Easily unexpire a user (Trac #14)

Show expired users in a universal "Expired" group.
When editing an expired user, have simple button to update user to make them valid again and again apply default expiry for that group. Currently, actions like changing group will update expiry, as will adding time/data limits. Need to be able to update expiry without changing group from A to B and back to A.

Dave said:

Every users that is expired for any reason will go on this group. I give you example of the utility of this group. Imagine grase hotspot used in hotel you create the user based account in the group 2 days because the customer stay 2 days in the hotel when expired it goes in group expired. If the same customer come back 1 month later we only need to move the customer back in the 2 days group and his account work fast without any configuration.

Migrated from http://trac.grasehotspot.org/ticket/14

{
    "status": "closed", 
    "changetime": "2011-09-08T22:11:08", 
    "description": "Show expired users in a universal \"Expired\" group.\nWhen editing an expired user, have simple button to update user to make them valid again and again apply default expiry for that group. Currently, actions like changing group will update expiry, as will adding time/data limits. Need to be able to update expiry without changing group from A to B and back to A.\n\nDave said:\n> Every users that is expired for any reason will go on this group. I give you example of the utility of this group. Imagine grase hotspot used in hotel you create the user based account in the group 2 days because the customer stay 2 days in the hotel when expired it goes in group expired.  If the same customer come back 1 month later we only need to move the customer back in the 2 days group and his account work fast without any configuration.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1315519868862774", 
    "component": "Admin Interface", 
    "summary": "Easily unexpire a user", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-12T03:48:07", 
    "milestone": "3.5", 
    "owner": "tim", 
    "type": "defect"
}

Proper traffic filtering (Trac #8)

Add proper traffic filtering for blocking types of traffic (i.e. bittorrent) and sites (adult sites). A combination of proxy, iptables, dns blacklists will all be used.

Migrated from http://trac.grasehotspot.org/ticket/8

{
    "status": "accepted", 
    "changetime": "2012-02-13T07:26:05", 
    "description": "Add proper traffic filtering for blocking types of traffic (i.e. bittorrent) and sites (adult sites). A combination of proxy, iptables, dns blacklists will all be used.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1329117965249388", 
    "component": "Filtering/Proxy", 
    "summary": "Proper traffic filtering", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-11T05:47:48", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "enhancement"
}

Chilli Status window doesn't show recurring or group limits (Trac #32)

Currently the status window only shows your usage based on the users limits. It needs to take into account group limits, as well as recurring limits (i.e. you have so much left this hour).

Group Month/Data limits are easy and will be in 3.6.1, however recurring limits will be harder

Migrated from http://trac.grasehotspot.org/ticket/32

{
    "status": "new", 
    "changetime": "2011-10-11T21:52:21", 
    "description": "Currently the status window only shows your usage based on the users limits. It needs to take into account group limits, as well as recurring limits (i.e. you have so much left this hour).\n\nGroup Month/Data limits are easy and will be in 3.6.1, however recurring limits will be harder", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1318369941668312", 
    "component": "Splash Screens", 
    "summary": "Chilli Status window doesn't show recurring or group limits", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-10-11T21:52:21", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "defect"
}

Feature Request : Adding PC Name and Mac Address in Monitoring Session. (Trac #27)

You should add pc name and mac address of each computer in monitoring session. When simultinous users is active if 3 users connect to the hotspot with the same login password we cant know who is who. If you add pc name and mac address we will see something like example user robert logged in and pc name would be IPAD-Robert or Iphone or robert-pc so we have idea of whois connected.

Migrated from http://trac.grasehotspot.org/ticket/27

{
    "status": "closed", 
    "changetime": "2011-08-30T00:29:32", 
    "description": "You should add pc name and mac address of each computer in monitoring session. When simultinous users is active if 3 users connect to the hotspot with the same login password we cant know who is who. If you add pc name and mac address we will see something like example user robert logged in and pc name would be IPAD-Robert or Iphone or robert-pc so we have idea of whois connected.", 
    "reporter": "Evils_1", 
    "cc": "", 
    "resolution": "worksforme", 
    "_ts": "1314664172511148", 
    "component": "Admin Interface", 
    "summary": "Feature Request : Adding PC Name and Mac Address in Monitoring Session.", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-29T13:10:13", 
    "milestone": "3.7", 
    "owner": "tim", 
    "type": "enhancement"
}

Translation for Freeradius Reply Messages (Trac #31)

Find a way to get the Radius Reply messages translated. Maybe a translation service that can be accessed via ajax? (Slow?)

Migrated from http://trac.grasehotspot.org/ticket/31

{
    "status": "accepted", 
    "changetime": "2012-03-19T20:50:13", 
    "description": "Find a way to get the Radius Reply messages translated. Maybe a translation service that can be accessed via ajax? (Slow?)", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1332190213597505", 
    "component": "Other Backend", 
    "summary": "Translation for Freeradius Reply Messages", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-10-10T06:52:51", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "defect"
}

Show group properties in user edit/create pages (Trac #25)

When editing or creating a user, we need to know what the groups settings are that will be applied to that user. This needs to be displayed somehow.

Migrated from http://trac.grasehotspot.org/ticket/25

{
    "status": "closed", 
    "changetime": "2011-09-02T02:44:37", 
    "description": "When editing or creating a user, we need to know what the groups settings are that will be applied to that user. This needs to be displayed somehow.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1314931477708678", 
    "component": "Admin Interface", 
    "summary": "Show group properties in user edit/create pages", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-26T23:51:03", 
    "milestone": "3.5", 
    "owner": "tim", 
    "type": "enhancement"
}

Expiration Date needs to be localised? (Trac #46)

Date display needs to be localised

Migrated from http://trac.grasehotspot.org/ticket/46

{
    "status": "new", 
    "changetime": "2012-01-23T23:54:18", 
    "description": "Date display needs to be localised", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1327362858513373", 
    "component": "Admin Interface", 
    "summary": "Expiration Date needs to be localised?", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2012-01-23T23:54:18", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "defect"
}

Updates overwrite template changes (Trac #17)

Need ability for really advanced template changes to not be overwritten on each update.
Maybe have a symlink from the templates directory to a location that the templates actually get used in, and only create the symlink if it (or the directory) doesn't exist. This way you can copy the templates to the working location and they won't be modified?
Or somehow detect changes and refuse to update or backup the changed files?

Migrated from http://trac.grasehotspot.org/ticket/17

{
    "status": "closed", 
    "changetime": "2011-09-09T08:13:45", 
    "description": "Need ability for really advanced template changes to not be overwritten on each update.\nMaybe have a symlink from the templates directory to a location that the templates actually get used in, and only create the symlink if it (or the directory) doesn't exist. This way you can copy the templates to the working location and they won't be modified?\nOr somehow detect changes and refuse to update or backup the changed files?", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "wontfix", 
    "_ts": "1315556025544871", 
    "component": "Packaging", 
    "summary": "Updates overwrite template changes", 
    "priority": "blocker", 
    "keywords": "templates, customisations, updates", 
    "version": "3.4", 
    "time": "2011-08-23T02:15:23", 
    "milestone": "3.5", 
    "owner": "tim", 
    "type": "defect"
}

Make status more understandable (Trac #34)

Current status page was designed for when you just had a timelimit and/or a data limit.
Need to change it to give better feed back of your "plan" (group) and that the things like session-timeout aren't necessarily the plan limits.
I.e. someone on a data limit plan will have a session timeout of many hours, which is actually how long until the account expires. We should probably hide session timeout in this case.
Someone with a recurring data/time limit needs to know that the session limits are for a time period, not the account limit.
Also need to see hard limits, i.e. if they have a recurring limit, as well as a hard limit, they need to know both limits.

Maybe show them bandwidth limits as well?

Migrated from http://trac.grasehotspot.org/ticket/34

{
    "status": "new", 
    "changetime": "2011-10-17T00:53:36", 
    "description": "Current status page was designed for when you just had a timelimit and/or a data limit.\nNeed to change it to give better feed back of your \"plan\" (group) and that the things like session-timeout aren't necessarily the plan limits.\nI.e. someone on a data limit plan will have a session timeout of many hours, which is actually how long until the account expires. We should probably hide session timeout in this case.\nSomeone with a recurring data/time limit needs to know that the session limits are for a time period, not the account limit.\nAlso need to see hard limits, i.e. if they have a recurring limit, as well as a hard limit, they need to know both limits.\n\nMaybe show them bandwidth limits as well?", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1318812816211378", 
    "component": "Splash Screens", 
    "summary": "Make status more understandable", 
    "priority": "major", 
    "keywords": "status", 
    "version": "3.4", 
    "time": "2011-10-17T00:53:36", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "defect"
}

Feature Request : Admin Panel User Checkbox to force Password Change On Login (Trac #35)

Imagine that you create username and password account for someone but you want to force them to change password that you set when they login.

Exemple username robert password test123 on login they get directly to their infos to change password or they cant continue...

Migrated from http://trac.grasehotspot.org/ticket/35

{
    "status": "accepted", 
    "changetime": "2013-01-29T10:46:49", 
    "description": "Imagine that you create username and password account for someone but you want to force them to change password that you set when they login.\n\nExemple username robert password test123 on login they get directly to their infos to change password or they cant continue...", 
    "reporter": "Evils_1", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1359456409919189", 
    "component": "Admin Interface", 
    "summary": "Feature Request : Admin Panel User Checkbox to force Password Change On Login", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-10-21T15:16:42", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "enhancement"
}

Feature Request : Add auto refresh in monitoring session (Trac #23)

Add auto refresh feature that allow us to auto refresh data within 5 secondes 30 60 5 minutes 10 30 etc.

Migrated from http://trac.grasehotspot.org/ticket/23

{
    "status": "closed", 
    "changetime": "2013-01-29T11:24:54", 
    "description": "Add auto refresh feature that allow us to auto refresh data within 5 secondes 30 60 5 minutes 10 30 etc. ", 
    "reporter": "Evils_1", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1359458694456346", 
    "component": "Admin Interface", 
    "summary": "Feature Request : Add auto refresh in monitoring session", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-26T16:44:08", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

Bandwidth Limits (Trac #5)

Limit bandwidth of user accounts both up and down

Migrated from http://trac.grasehotspot.org/ticket/5

{
    "status": "closed", 
    "changetime": "2011-08-11T05:21:27", 
    "description": "Limit bandwidth of user accounts both up and down", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1313040087000319", 
    "component": "Admin Interface", 
    "summary": "Bandwidth Limits", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.0", 
    "time": "2011-08-11T05:20:39", 
    "milestone": "3.4", 
    "owner": "tim", 
    "type": "enhancement"
}

Add new default time and default data limit? (Trac #42)

Ability to add new default time and default data limit from the drop down menus.

I think that adding 2 new text input forms with comma sepearated values like 100,200,500,600 would do the trick of the drop down menu.

Migrated from http://trac.grasehotspot.org/ticket/42

{
    "status": "accepted", 
    "changetime": "2012-01-28T00:30:42", 
    "description": "Ability to add new default time and default data limit from the drop down menus.\n\n\nI think that adding 2 new text input forms with comma sepearated values like 100,200,500,600 would do the trick of the drop down menu.", 
    "reporter": "tomas213 _", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1327710642327342", 
    "component": "Admin Interface", 
    "summary": "Add new default time and default data limit?", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2011-12-04T17:50:52", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "enhancement"
}

Usermin Menus Broken (Trac #50)

Probably due to the changes for admin levels, usermin menus are broken

Migrated from http://trac.grasehotspot.org/ticket/50

{
    "status": "closed", 
    "changetime": "2012-06-28T09:13:05", 
    "description": "Probably due to the changes for admin levels, usermin menus are broken", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1340874785597962", 
    "component": "Admin Interface", 
    "summary": "Usermin Menus Broken", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.7", 
    "time": "2012-01-28T03:55:58", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "defect"
}

Allow time based "specials" (Trac #44)

i.e. Free WiFi day, would assist if we had auto create account via mac to login straight away.

Migrated from http://trac.grasehotspot.org/ticket/44

{
    "status": "new", 
    "changetime": "2012-01-12T01:03:09", 
    "description": "i.e. Free WiFi day, would assist if we had auto create account via mac to login straight away.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1326330189477861", 
    "component": "Admin Interface", 
    "summary": "Allow time based \"specials\"", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.6", 
    "time": "2012-01-12T01:03:09", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "defect"
}

Config option to remove menu at bottom (Trac #20)

Allow configuration of bottom menu (footer)

Migrated from http://trac.grasehotspot.org/ticket/20

{
    "status": "closed", 
    "changetime": "2011-09-09T08:10:00", 
    "description": "Allow configuration of bottom menu (footer)", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1315555800123117", 
    "component": "Admin Interface", 
    "summary": "Config option to remove menu at bottom", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-25T23:37:22", 
    "milestone": "3.5", 
    "owner": "tim", 
    "type": "enhancement"
}

Multiple "Signup" methods. Including SMS

Feature for limiting free access. Requires a mobile number which it sends a SMS token to for logging in. Each login is limited to a predefined limit, or recurring limits (based on group).
Used as a way of "rate" limiting, as you'll need a new phone number for more access.

Migrated from http://trac.grasehotspot.org/ticket/10

{
    "status": "new", 
    "changetime": "2013-01-29T10:40:06", 
    "description": "Feature for limiting free access. Requires a mobile number which it sends a SMS token to for logging in. Each login is limited to a predefined limit, or recurring limits (based on group).\nUsed as a way of \"rate\" limiting, as you'll need a new phone number for more access.", 
    "reporter": "tim", 
    "cc": "[email protected]", 
    "resolution": "", 
    "_ts": "1359456006573356", 
    "component": "Admin Interface", 
    "summary": "SMS Auth Token", 
    "priority": "major", 
    "keywords": "sms, token, auto create", 
    "version": "3.4", 
    "time": "2011-08-11T05:53:34", 
    "milestone": "3.8", 
    "owner": "tim", 
    "type": "enhancement"
}

Ability to customise Portal easily (Trac #13)

Need ability to easily customise portal pages. This needs to be at least editing CSS, enabling/disabling different components (popup status box, ToC, Help page, laptop help) and editing text for each component.

Migrated from http://trac.grasehotspot.org/ticket/13

{
    "status": "closed", 
    "changetime": "2011-09-09T08:11:25", 
    "description": "Need ability to easily customise portal pages. This needs to be at least editing CSS, enabling/disabling different components (popup status box, ToC, Help page, laptop help) and editing text for each component.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1315555885759907", 
    "component": "Splash Screens", 
    "summary": "Ability to customise Portal easily", 
    "priority": "critical", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-12T03:44:43", 
    "milestone": "3.5", 
    "owner": "tim", 
    "type": "defect"
}

Different Admin levels in admin interface (Trac #6)

i.e. "root" users who can do everything. Other "Admins" who can only create new tickets and not change portal settings. etc

Migrated from http://trac.grasehotspot.org/ticket/6

{
    "status": "accepted", 
    "changetime": "2012-01-28T00:26:58", 
    "description": "i.e. \"root\" users who can do everything. Other \"Admins\" who can only create new tickets and not change portal settings. etc", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1327710418373022", 
    "component": "Admin Interface", 
    "summary": "Different Admin levels in admin interface", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-11T05:42:11", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "enhancement"
}

Feature Request : Add table section in monitoring session (Trac #24)

Add table section like in users list to group monitoring session by Day By Month By Year By Week etc. it will be more easy to find information after that. Just imagine 250 sessions by day after 30 days lol try to find something easily :)

Migrated from http://trac.grasehotspot.org/ticket/24

{
    "status": "accepted", 
    "changetime": "2012-12-14T04:18:54", 
    "description": "Add table section like in users list to group monitoring session by Day By Month By Year By Week etc. it will be more easy to find information after that. Just imagine 250 sessions by day after 30 days lol try to find something easily :)", 
    "reporter": "Evils_1", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1355458734285124", 
    "component": "Admin Interface", 
    "summary": "Feature Request : Add table section in monitoring session", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-26T16:45:49", 
    "milestone": "3.9", 
    "owner": "tim", 
    "type": "enhancement"
}

Prevent/Allow Simultaneous Use of an account (Trac #2)

Option to prevent an account from being used from more than 1 computer at a time. (Or allow it)

Migrated from http://trac.grasehotspot.org/ticket/2

{
    "status": "closed", 
    "changetime": "2011-08-11T05:17:01", 
    "description": "Option to prevent an account from being used from more than 1 computer at a time. (Or allow it)", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1313039821171545", 
    "component": "Admin Interface", 
    "summary": "Prevent/Allow Simultaneous Use of an account", 
    "priority": "major", 
    "keywords": "", 
    "version": "3.0", 
    "time": "2011-08-11T05:16:32", 
    "milestone": "3.4", 
    "owner": "tim", 
    "type": "defect"
}

Feature Request : Modify DHCP lease time. (Trac #26)

You need to add option to modify dhcp lease time its really to high we need to choose between some predefined time like 6h 12h 24h 48h 1 week etc.

Look in this example i have 8 users in my hotspot and they are now at ip 188...

[[Image(http://www.abcinformatique.ca/hotspot/hotspot.png)]]

Migrated from http://trac.grasehotspot.org/ticket/26

{
    "status": "closed", 
    "changetime": "2012-01-23T22:38:00", 
    "description": "You need to add option to modify dhcp lease time its really to high we need to choose between some predefined time like 6h 12h 24h 48h 1 week etc. \n\nLook in this example i have 8 users in my hotspot and they are now at ip 188...\n\n[[Image(http://www.abcinformatique.ca/hotspot/hotspot.png)]]", 
    "reporter": "Evils_1", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1327358280817234", 
    "component": "Admin Interface", 
    "summary": "Feature Request : Modify DHCP lease time.", 
    "priority": "minor", 
    "keywords": "", 
    "version": "3.4", 
    "time": "2011-08-29T13:07:32", 
    "milestone": "3.7", 
    "owner": "tim", 
    "type": "enhancement"
}

PDF Tickets (Trac #4)

Create and print PDF tickets. This will allow us to support a variety of printer sizes, and ticket layouts. Need to be able to print single tickets or pages of tickets, and customise what is printed on them.

Migrated from http://trac.grasehotspot.org/ticket/4

{
    "status": "closed", 
    "changetime": "2012-01-28T00:32:43", 
    "description": "Create and print PDF tickets. This will allow us to support a variety of printer sizes, and ticket layouts. Need to be able to print single tickets or pages of tickets, and customise what is printed on them.", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1327710763112484", 
    "component": "Admin Interface", 
    "summary": "PDF Tickets", 
    "priority": "major", 
    "keywords": "tickets, PDF, print", 
    "version": "", 
    "time": "2011-08-11T05:19:43", 
    "milestone": "3.7", 
    "owner": "tim", 
    "type": "enhancement"
}

Ability to disconnect active users (Trac #28)

Coova Chilli provides the ability to disconnect a session via the coaport. We need to make this usable from the web interface.

The following is from the mailing list, maybe we can make it more secure than this? Sudo shouldn't be needed for radclient.

first edit /etc/init.d/chilli to add listen port for disconnect packet by adding the line
DAEMON_ARGS="--coaport 3779"

so the first line would be like this:

! /bin/sh

PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/chilli
NAME=chilli
DESC=chilli
DAEMON_ARGS="--coaport 3779"

add coaport on /etc/chilli/hs.conf or in

TAG COA Port

coaport 3779

restart chilli

Don't forget to add sudo line to allow www-data permission on /etc/sudoers
www-data ALL=NOPASSWD:/bin/echo
www-data ALL=NOPASSWD:/usr/bin/radclient

test it first, try execute this in shellcommand
echo "User-Name=username" | radclient -x 127.0.0.1:3779 disconnect yourradiussecret

username is the username who want you kick out from grase.
yourradiussecret is radius secret, if u did not change it, the deflaut from grase is >hotspotradius

or u can use php sript. (example)
$shell_command='sudo /bin/echo "User-Name='.kevin.'" | /usr/bin/radclient -x 127.0.0.1:3779 >disconnect hotspotradius ';
$output = shell_exec($shell_command);

Migrated from http://trac.grasehotspot.org/ticket/28

{
    "status": "new", 
    "changetime": "2011-08-31T22:41:13", 
    "description": "Coova Chilli provides the ability to disconnect a session via the coaport. We need to make this usable from the web interface.\n\nThe following is from the mailing list, maybe we can make it more secure than this? Sudo shouldn't be needed for radclient.\n\n>1. first edit /etc/init.d/chilli to add listen port for disconnect packet by adding the line\n>DAEMON_ARGS=\"--coaport 3779\"\n>\n>so the first line would be like this:\n>#! /bin/sh\n>PATH=/sbin:/bin:/usr/sbin:/usr/bin\n>DAEMON=/usr/sbin/chilli\n>NAME=chilli\n>DESC=chilli\n>DAEMON_ARGS=\"--coaport 3779\"\n>\n>2. add coaport on /etc/chilli/hs.conf or in\n>\n># TAG COA Port\n>coaport 3779\n>\n>3. restart chilli\n>\n>4. Don't forget to add sudo line to allow www-data permission on /etc/sudoers\n>www-data ALL=NOPASSWD:/bin/echo\n>www-data ALL=NOPASSWD:/usr/bin/radclient\n>\n>\n>5. test it first, try execute this in shellcommand\n>echo \"User-Name=username\" | radclient -x 127.0.0.1:3779 disconnect yourradiussecret\n>\n>username is the username who want you kick out from grase.\n>yourradiussecret is radius secret, if u did not change it, the deflaut from grase is >hotspotradius\n>\n>6. or u can use php sript. (example)\n>$shell_command='sudo /bin/echo \"User-Name='.kevin.'\" | /usr/bin/radclient -x 127.0.0.1:3779 >disconnect hotspotradius ';\n>$output = shell_exec($shell_command);\n>\n>", 
    "reporter": "tim", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1314830473155211", 
    "component": "Admin Interface", 
    "summary": "Ability to disconnect active users", 
    "priority": "major", 
    "keywords": "coaport, disconnect, active, session", 
    "version": "3.4", 
    "time": "2011-08-31T22:39:48", 
    "milestone": "4.0", 
    "owner": "tim", 
    "type": "enhancement"
}

grasehotspot / grase-www-portal Goto Github PK

grase-www-portal's People

Contributors

Stargazers

Watchers

Forkers

grase-www-portal's Issues

! /bin/sh

TAG COA Port

Recommend Projects

Recommend Topics

Recommend Org