Most Liked Content

Please be sure to read our knowledgebase first before starting a new topic, there are several articles there that should answer a lots of your questions.

Click here to go to knowledgebase.

We like that you gave us ideas so we know what is important for our operators. As we are developing our very own, unique solution (unlike others who resell a global product usually) we can continuously add new features to our system.

Free Trial was a long awaited and requested feature.


What's the purpose?

• You can offer an unlimited free access in a Pay-Per-Use location with low bandwidth limits. Other users can pay for faster packages.
• You can offer a limited free package (for example 10 minutes test drive, or 100 MB free access). After the access expires, users have to pay.

For more information please read our knowledgebase article.

Another thing you could check is the internet connectivity. If there's any form of hiccup or d/c on your unit it would cause the chilli service to stop running. or if it's on boot it wont complete booting.

The class A address you listed is something that would be supplied by the isp NOC up here meaning you have to register the connection. I doubt your with telus though.

I did a search for the IP range and that must be a local address as there is no shown info for any isp having that bock of ip's. It's really starting to look more as if there is an issue with the internet connection itself.

I've had a couple issues now including one of them being me ordering the wrong product. I'm fairly sure they were laughing at me while addressing this as i would... (Another note to read before you click) I ordered the extra currency while a little too tired and not realizing this was not the tickets and the extra currency was useless in Canada. The staff worked with me to make this right and we're fast, courteous and more then willing to listen to me complain about something that was my own fault while rectifying the situation.

You do not see this level of customer service from many companies before. Too many people outsource their support to third party private companies that really don't care if your issue gets resolved or not. As HotSpotSystem manages their own support, you see that attention that should be there when dealing with a customer service representative. I've got nothing bad to say about the setup or the amazing staff here, even when the issue was cause by my own stupidity; they we're more then willing to help as they could.

It depends on the firmware. In ddwrt you can change it under Wireless-basic settings-wireless network name (SSID).

For HotspotWrt you can use these instructions: http://hotspotsystem...=1218-DLZV-3307

You can also set up Coova/HotspotWRT/ DDWRTfirmwares to accept commands remotely, then you can change the SSID from the control center. See this article on the topic: http://hotspotsystem...=5216-YGHX-8291

I find the support desk respond very quickly to any queries, technical or otherwise. When I first setup the system all my queries were answered fast.

System is stable, radius seems stable, very few issues from users - in fact we have had no user problems in 3 months of operation.

great system - looking forward to it earning good revenue over the busy tourist season here in Cape Town.

Here is an interesting map about the locations where our system is being used as of today.



Note: only those locations are visible which has a valid address in our database (so some of them are not on the map).

Auto correcting rules

Hi,

To setup CoovaChilli on OpenWRT
(edited from a question about this subject)

There is no automatic config script for OpenWRT past White Russian, but as "any linux with CoovaChilli" is listed as supported, it should work. This does mean one must set all the Coova parameters self. I collected the parameters from the CoovaAP automatic setup script combined with the Coova man pages.

I assume you have OpenWRT already installed on your box, and know how to get to its command line, and know how to activate its wireless. If not, please go to the OpenWRT "first logon" page (search Google). Please note the instructions below assume all command line, no Web-Gui is used or needed.

Step 1: Install Coova:

opkg update
opkg install coova-chilli

Step 2: edit file /etc/chilli/default

The first 3 parameters are very important. You should know your HotSpotSystems location and name parameters. The interfaces you need to check your device. The other parameters should be correct, but review anyway. The names of the wan and lan interfaces are retrieved, but if you want to be usre you could hardcode them. Check yourself with the "ifconfig | grep inet -B1" command.

# You *MUST* edit/validate these parameters
HS_LOC_ID="1"
HS_LOC_NAME="xxxxxxxxxxx"
HS_NASID="xxxxxxxxxx"
 
# You may edit these parameters
HS_WANIF=`uci -P/var/state get network.wan.ifname`
HS_LANIF=`uci -P/var/state get network.lan.ifname`
HS_DNS1=8.8.8.8
HS_DNS2=8.8.4.4
#HS_MACALLOWLOCAL=on
#HS_MACALLOW="XX-XX-XX-XX-XX-XX,XX-XX-XX-XX-XX-XX"
 
# You best leave these as they are (for HotSporSystems)
HS_TYPE="chillispot"
HS_LAN_ACCESS="allow"
HS_MODE="wireless"
 
HS_UAMPORT=3990			# HotSpot UAM Port (on subscriber network)
HS_UAMUIPORT=4990		  # HotSpot UAM "UI" Port (on subscriber network, for embedded portal)
 
HS_NETWORK=192.168.182.0
HS_NETMASK=255.255.255.0
HS_UAMLISTEN=192.168.182.1
HS_DNS_DOMAIN=key.chillispot.info
HS_DYNIP=192.168.182.0
HS_DYNIP_MASK=255.255.255.0
HS_RADIUS=radius.hotspotsystem.com
HS_RADIUS2=radius2.hotspotsystem.com
 
HS_UAMHOMEPAGE=""
HS_UAMFORMAT="https://customer.hotspotsystem.com/customer/hotspotlogin.php"
HS_PROVIDER="HotSpotSystem"
HS_PROVIDER_LINK="http://www.hotspotsystem.com/"
HS_RADCONF="off"
HS_UAMSERVER="hotspotsystem.com"
HS_UAMSECRET="hotsys123"
HS_RADSECRET="hotsys123"
HS_UAMSERVER="customer.hotspotsystem.com"
HS_AAA="radius"
 
HS_UAMALLOW="194.149.46.0/24 198.241.128.0/17 66.211.128.0/17 216.113.128.0/17 70.42.128.0/17 \
			 128.242.125.0/24 216.52.17.0/24 62.249.232.74 155.136.68.77 155.136.66.34 \
			 66.4.128.0/17 66.211.128.0/17 66.235.128.0/17 88.221.136.146 195.228.254.149 \
			 195.228.254.152 203.211.140.157 203.211.150.204 \
			 www.paypal.com www.paypalobjects.com live.adyen.com \
			 www.worldpay.com select.worldpay.com secure.ims.worldpay.com \
			 www.rbsworldpay.com secure.wp3.rbsworldpay.com www.directebanking.com \
			 betalen.rabobank.nl ideal.ing.nl internetbankieren.frieslandbank.nl \
			 ideal.abnamro.nl ideal.snsreaal.nl ideal.triodos-onlinebanking.nl \
			 www.hotspotsystem.com customer.hotspotsystem.com tech.hotspotsystem.com \
			 a1.hotspotsystem.com a2.hotspotsystem.com a3.hotspotsystem.com a4.hotspotsystem.com \
			 a5.hotspotsystem.com a6.hotspotsystem.com a7.hotspotsystem.com a8.hotspotsystem.com \
			 a9.hotspotsystem.com a10.hotspotsystem.com a11.hotspotsystem.com a12.hotspotsystem.com \
			 a13.hotspotsystem.com a14.hotspotsystem.com a15.hotspotsystem.com a16.hotspotsystem.com \
			 a17.hotspotsystem.com a18.hotspotsystem.com a19.hotspotsystem.com a20.hotspotsystem.com"
HS_UAMDOMAINS="paypal.com paypalobjects.com worldpay.com rbsworldpay.com adyen.com hotspotsystem.com"

Step 3: init.d startup script

For some reason (which I consider a package error) the coova package does not come with init.d script. I found a /etc/init.d/chilli script for startup/shutdown, but slighty modified it. The original auto-renamed the wireless SSID name, but that was taken out. See the original here, and what I used below. It worked on both Broadcom WRT54GS and Atheros WR740N and WR941ND.

Put this in /etc/init.d/chilli and do a chmod a+x /etc/init.d/chilli to make it executeable.

#!/bin/sh /etc/rc.common
# - init script for chilli -
 
START=60
STOP=60
 
NAME=chilli
RUN_D=/var/run
CMDSOCK=$RUN_D/$NAME.sock
PIDFILE=$RUN_D/$NAME.pid
 
option_cb() { [ -n "$2" ] && echo "HS_$(echo $1|tr 'a-z' 'A-Z')=\"$2\"" | sed 's/\$/\\\$/g'; }
config_load hotspot > /etc/chilli/config
 
. /etc/chilli/functions
 
start() {
	case ${hs_type:-$HS_TYPE} in
		*chilli*)
			;;
		*)
			echo "Not running hotspot"
			exit
			;;
	esac
 
	HS_DNS_DOMAIN=${HS_DNS_DOMAIN:-cap.coova.org}
	HS_DNS1=${HS_DNS1:-$HS_UAMLISTEN}
	HS_DNS2=${HS_DNS2:-$HS_NASIP}
	HS_NASID=${HS_NASID:-$HS_NASMAC}
	HS_MACAUTHMODE=${HS_MACAUTHMODE:-local}
	HS_USELOCALUSERS=${HS_USELOCALUSERS:-off}
	HS_PROXY_TYPE=${HS_PROXY_TYPE:-none}
	HS_RADCONF_URL=${HS_RADCONF_URL:-http://ap.coova.org/config/tos.conf}
	HS_CFRAME_URL=${HS_CFRAME_URL:-http://coova.org/cframe/default/}
	HS_CFRAME_SZ=${HS_CFRAME_SZ:-100}
	HS_DEFSESSIONTIMEOUT=${HS_DEFSESSIONTIMEOUT:-0}
	HS_DEFIDLETIMEOUT=${HS_DEFIDLETIMEOUT:-0}
	HS_DEFINTERIMINTERVAL=${HS_DEFINTERIMINTERVAL:-300}
	HS_LAN_ACCESS=${HS_LAN_ACCESS:-deny}
	HS_CFRAME_POS=${HS_CFRAME_POS:-top}
	HS_PROVIDER=${HS_PROVIDER:-Coova}
	HS_PROVIDER_LINK=${HS_PROVIDER_LINK:-http://coova.org/}
	HS_LOC_NAME=${HS_LOC_NAME:-My HotSpot}
	HS_LOC_NETWORK=${HS_LOC_NETWORK:-Coova}
	HS_OPENIDAUTH=${HS_OPENIDAUTH:-off}
	HS_ANYIP=${HS_ANYIP:-off}
 
	[ -z "$HS_LANIF" ] && {
		[ -e /tmp/device.hotspot ] && { stop }
		echo $HS_LANIF > /tmp/device.hotspot
	}
	writeconfig
	radiusconfig
	[ -d $RUN_D ] || mkdir -p $RUN_D
	/sbin/insmod tun >&- 2>&-
	/usr/sbin/chilli
}
 
stop() {
	[ -f $PIDFILE ] && kill $(cat $PIDFILE)
	rm -f $PIDFILE $LKFILE $CMDSOCK 2>/dev/null
	rm /tmp/device.hotspot
}

Step 4: Optional WAN maintenance access

To ensure you can always get to the box using SSH and/or WEB (if you installed a Web GUI, which is not default in OpenWRT) you optionally can also put these lines into the /etc/firewall.user file.

# Always allow these ports on WAN interface for router admin as well
 
iptables -I zone_wan -p tcp --dport 443 -j ACCEPT;
iptables -I zone_wan -p tcp --dport 80 -j ACCEPT;
iptables -I zone_wan -p tcp --dport 22 -j ACCEPT;

Step 5: start and test

Now you can start coova and test if it works. After starting coova, if you are on it's lan side, you will probably loose connection, as you are not inside the hotspot and need to sign into the hotspot. Thats why you may have needed above wan side firewall lines, so you can get in from that side.

/etc/init.d/chilli start

if chilli does not run, check the following files that it should have generated:

/etc/chilli/hs.conf
/etc/chilli/main.conf
/var/run/chilli.tun0.sh

Also, you may want to run chilli in interactive debug to see if there are any hints: chilli -fd

Step 6: Finalize

If it does run, you can optionally set the hotspot to autostart on reboot.

/etc/init.d/chilli enable

and optionally, if you want to save valuable memory, disable these processes from autostarting:

/etc/init.d/dnsmasq disable
/etc/init.d/uhttpd disable

Good luck. If you used this guide to get coova to work on OpenWRT, drop in a note below.

like other brasiers and that way it would work with a hotspot.

LOL. Either you have some auto-spelling-correct-problems, or your mind was someplace else....

After we change our operator to Hotspotsystem, it has been easier for our costumers and easier for us.

recommending Hotspotsystem from all our hearts.

And if you are thinking visit Greenland please do not hesitate to contack us.


Best regards

Sulisartut Højskoliat
3920 Qaqortoq
Greenland
e-mail: sulisartut@sulisartut.gl

Busy setting up a Hotspot Splash, sharing a limited ADSL with Campground users for free, so fairly distributing bandwidth, especially upload is important.

However, I find that the upload is not at all adhering to the location defaults. I have set 128/64 (as ultralow experiment), but a speedtest is showing 0.11Mb/0.79Mb. When setting 256/128, the speedtest shows 0.23Mb/0.79Mb. So upload is always roughly the max of my entire ADSL.

It seems download is adhering to limits, upload is not. And I am far more worried about upload, seeing how we have only 1Mb of it and I am predicting a lot of skype-video usage. I am checking with my ISP to see if they cannot change to Annex-M, but SDSL or VDSL is not an option here in the rural area's, so it would be nice if the upload could be limited as per location defaults.

Device: DD-WRT V24 preSP2 build 15778
TP-Link WR941ND 400Mhz atheros 32MB, CPU not heavily impacted during this test.

We have used HotspotSystem for 3 years. We earlier used a different system, which was controlled by a computer to be always online.
We are free with this system that always works perfectly and does not need physical monitoring.
We run 2 hotspots and have been exceptionally pleased.

Regards
Tunø Hotspot (tunspot.dk) Denmark

All i can say is wow! I have been using Hotspot System for the last 3 years and thus far I the service have been outstanding.

With ZERO downtime and a fast network, these guys are just about the only true providers in their class.

Thanks Hotspot System!

Nice, how did you utilize hotspot system in this setup?

perfect !!!
with HotspotWRT firmware it's all ok.
Thank you......

now works with all types of devices......

I suggest to use HotspotWRT firmware at this point, as this might be a bug in dd-wrt. Please let me know the results.

http://www.hotspotsy...hotspotwrt.html

What problems are you experiencing, what happens after an iPhone connects to the hotspot?

What hardware and firmware are you using?

Hey Prospective customers, if you're looking for first class support from a first class team, look no further. The team support here will reply promptly and want you to succeed because the bottom line is to provide your customers with great service and fill your pocket with money! They have done their homework with just about every router to offer for your router to ensure success. I couldn't be any happier!

I too had purchased Antamedia to run my network and that was a mistake. Software never worked properly and the payment processor would always fail and customer support was horrible. I even called them and they rudely hung up on me so I figured it was time to look elsewhere. I wish I would have used HSS to start and saved myself a couple bottles of headache meds. I have never seen support with any of the software like I have with HSS. I appreciate the help to get my network up and running so smoothly. Thanks again HSS and my pockets keep getting fat and my customers love the service I provide for them.

DD2 HotSpot

The products and support offered by HSS are 5 Star. Roland, Oliver, and Marko have all contributed to making my WiFi service an unbelievable success. I started a WiFi service and knew nothing about WISP. I now have a managed network that produces a substantial monthly income. The crew at HSS tolerated my non-stop questions and concerns and were very patient with me. I was such a novice I had to label my equipment "Modem", "Switch", "Router", etc, as I did not know one component from the next. Less than one year later I have a central station supporting 11 outlying tower based access points. I operate Ubiquiti equipment using a 5ghz distribution system. HSS handles all my billing and user management.
I had to learn the hard way and had started my system using antamedia software. Following mediocre profits and non-stop problems I switched to HSS and have been very satisfied since.
See my posting under Case Studies for the specifics.
Bottom Line: If you want profitability then use HSS.
Good Luck
Smokin J HotSpot