- This topic has 5 replies, 2 voices, and was last updated 12 years, 6 months ago by
stevehars.
Help Configure Coova-Chilli On Freebsd To Hotspotsystem
-
Anonymous December 6, 2013 at 12:23 pm
Hi guys, i’m new on this hotspot world and i need some help. Let’s go.
I follow this article “http://www.hotspotsystem.com/hotspot_help/kb/articles/36-can-i-use-the-system-on-a-unix-like-computer-operating-system-linux-freebsd-etc” to set my FreeBsd machine.
My topology is: (See attached file)
The coova-chilli starts with one error: “unknow=nm downlink protocol” , but it goes ahead.
Then, one interface tun0 is created with the fist ip of the network that i configure on chillli.conf.
The clients can connect to my Wireless Network and receive an ip of this network. They can ping to each other and to interface tun0, but they can not ping to internet, even to ip address or domain.
The dns set by the dhcp of coova-chilli on the clienst is 127.0.0.1 and search key.chillispot.info.
On the control panel of hotspotsystem.com the status of my location apears as “Never Seen” , what make me belive that is not auth on radius server.
I dont’t know what to do now.
Can you please help solve this ?
Thank You.
Hello,
There are a few things to put together with coovachilli on linux.
Can you ping anything on the internet from the linux based machine?
If yes, then you don’t get proper routing.
The interface of the hotspot (not tun0, but its physical carrier) should have an ACCEPT, ACCEPT, REJECT firewall rule(input, output, forward) forwarding rule in the firewall file. It also has to have a proper zone section defined in the firewall file.
Like this:
config ‘zone’
option ‘name’ ‘eth3’ (e.g.)
option ‘input’ ‘ACCEPT’
option ‘output’ ‘ACCEPT’
option ‘forward’ ‘REJECT’
option masq ‘1’ (you probably need this to have NAT from this interface towards the gateway interface)
config ‘forwarding’
option ‘src’ ‘eth3’
option ‘dest’ ‘wan’ (gateway / internet source)
Let us know if this clears up the picture.
Best Regards,
Steve Hars,
Hotspotsystem.com
Anonymous December 6, 2013 at 6:41 pmHI Steve Hars, thank you for your answer.
At this moment, i do not activate firewall on this machine. It is connected directly to the internet router, so, i can ping anywhere from it. So the default gateway is my internet router.
The problem is that from the client i can’t ping anywhere except tun interface and others clients.
I can’t certificate if the chilli is autenticating with radius server of hotspot system.
Here is my chilli.conf file:
include /usr/local/etc/chilli/main.conf
include /usr/local/etc/chilli/hs.conf
include /usr/local/etc/chilli/local.conf
ipup=/usr/local/etc/chilli/up.sh
ipdown=/usr/local/etc/chilli/down.sh
radiusserver1 radius.hotspotsystem.com
radiusserver2 radius2.hotspotsystem.com
radiussecret hotsys123
dhcpif rl0
net 192.168.1.0/24
uamserver https://customer.hotspotsystem.com/customer/hotspotlogin.php
dns1 8.8.8.8
dns2 8.8.8.8
uamsecret hotsys123
uamanydns
radiusnasid ID_NUMBER
uamhomepage https://customer.hotspotsystem.com/customer/index.php?operator=ID&location=NUMBER
coaport 3799
coanoipcheck
domain key.chillispot.info
uamallowed 194.149.46.0/24,198.241.128.0/17,66.211.128.0/17,216.113.128.0/17
uamallowed 70.42.128.0/17,128.242.125.0/24,216.52.17.0/24
uamallowed 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
uamallowed 88.221.136.146,195.228.254.149,195.228.254.152,203.211.140.157,203.211.150.204
uamallowed http://www.worldpay.com,secure.worldpay.com,live.adyen.com
uamallowed http://www.hotspotsystem.com,customer.hotspotsystem.com,tech.hotspotsystem.com
uamallowed a1.hotspotsystem.com,a2.hotspotsystem.com,a3.hotspotsystem.com,a4.hotspotsystem.com,a5.hotspotsystem.com,a6.hotspotsystem.com
uamallowed a7.hotspotsystem.com,a8.hotspotsystem.com,a9.hotspotsystem.com,a10.hotspotsystem.com,a11.hotspotsystem.com,a12.hotspotsystem.com
uamallowed a13.hotspotsystem.com,a14.hotspotsystem.com,a15.hotspotsystem.com,a16.hotspotsystem.com,a17.hotspotsystem.com,a18.hotspotsystem.com,a19.hotspotsystem.com,a20.hotspots
ystem.com
interval 300
And here is the “defaults” file:
HS_WANIF=re0
HS_LANIF=rl0
HS_NETWORK=192.168.1.0
HS_NETMASK=255.255.255.0
HS_UAMLISTEN=192.168.1.1
HS_UAMPORT=3990
HS_DYNIP=192.168.1
HS_DYNIP_MASK=255.255.255.0
# HS_STATIP=
# HS_STATIP_MASK=255.255.255.0
HS_DNS_DOMAIN=key.chillispot.info
HS_DNS1=8.8.8.8
HS_DNS2=8.8.8.8
HS_NASID=neomapt1
HS_UAMSECRET=”hotsys123″
HS_RADIUS=radius.hotspotsystem.com
HS_RADIUS2=radius2.hotspotsystem.com
HS_RADSECRET=hotsys123
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 http://www.paypal.com http://www.paypalobjects.com live.adyen.com http://www.worldp
ay.com select.worldpay.com secure.ims.worldpay.com http://www.rbsworldpay.com secure.wp3.rbsworldpay.com http://www.directebanking.com betalen.rabobank.nl ideal.ing.nl internetbankieren.fries
landbank.nl ideal.abnamro.nl ideal.snsreaal.nl ideal.triodos-onlinebanking.nl http://www.hotspotsystem.com customer.hotspotsystem.com tech.hotspotsystem.com a1.hotspotsystem.com a2.hot
spotsystem.com a3.hotspotsystem.com a4.hotspotsystem.com a5.hotspotsystem.com a6.hotspotsystem.com a7.hotspotsystem.com a8.hotspotsystem.com a9.hotspotsystem.com a10.hotspotsyst
em.com a11.hotspotsystem.com a12.hotspotsystem.com a13.hotspotsystem.com a14.hotspotsystem.com a15.hotspotsystem.com a16.hotspotsystem.com a17.hotspotsystem.com a18.hotspotsyste
m.com a19.hotspotsystem.com a20.hotspotsystem.com
HS_UAMDOMAINS=”paypal.com paypalobjects.com worldpay.com rbsworldpay.com adyen.com hotspotsystem.com”
HS_UAMSERVER=hotspotsystem.com
HS_UAMFORMAT=https://custumer.hotspotsystem.com/custumer/hotspotlogin.php
HS_UAMHOMEPAGE=
HS_RADCONF=off
HS_MODE=wireless
HS_TYPE=chillispot
HS_WWWDIR=/usr/local/etc/chilli/www
HS_WWWBIN=/usr/local/etc/chilli/wwwsh
HS_PROVIDER=Hotspotsystem
HS_PROVIDER_LINK=http://www.hotspotsystem.com/
HS_LOC_NAME=”NeoSPOT”
Please, i’ll appriciate your help.
Thank You.
P.S: sorry bad english.
Hello,
A few things to clear.
First off, please do not modify the hotspot subnet of 192.168.182.0 unless you have specific problems.
Second, the WAN and LAN side of the hotspot router/computer cannot be in the same subnet, for networking standard reasons.
The following syntax is not OK: ‘HS_DYNIP=192.168.1’ in the default.conf file.
You cannot avoid NAT, otherwise coovachilli simply won’t work. So you have to enable it, by setting up two different subnets(and masquerading) on the two sides of the coovachilli processing network ‘node’.
Let me know how it goes.
Best Regards,
Steve Hars,
Hotspotsystem.com
Anonymous December 12, 2013 at 7:49 pmHello,
A few things to clear.
First off, please do not modify the hotspot subnet of 192.168.182.0 unless you have specific problems.
Second, the WAN and LAN side of the hotspot router/computer cannot be in the same subnet, for networking standard reasons.
The following syntax is not OK: ‘HS_DYNIP=192.168.1’ in the default.conf file.
You cannot avoid NAT, otherwise coovachilli simply won’t work. So you have to enable it, by setting up two different subnets(and masquerading) on the two sides of the coovachilli processing network ‘node’.
Let me know how it goes.
Best Regards,
Steve Hars,
Hotspotsystem.com
Hi Steve,
Thank’s for your support. So i need to configure this machine as a gateway, with NAT and firewall, right ?
Back the subnet of hotspot to 192.168.182.0, and correct HS_DYNIP=192.168.1 (This is on the default file, i do not change it. How is the correct ?)
Thank you.
Hello,
Yes you need NAT, firewall is not necessary.
You can get info on how Coovachilli should be configured from here:
http://coova.org/CoovaChilli
You must be logged in to reply to this topic.