search

coova / coova-chilli

CoovaChilli is an open-source software access controller for captive portal hotspots.
Other
514 stars 257 forks source link

Cloud Coova Chilli #517

Open scbmeren opened 4 years ago

scbmeren commented 4 years ago

Hi,

Is there any chance of having Coova Chilli on Cloud? The main propose is to have a central server for authentication, accounting and captive portal. If possible to you have any setup example?

Regards

sjbeskur commented 4 years ago

You can certainly host your authentication portal and radius servers in the cloud. That is how our deployment exists, however, you will still need to run Coova locally and configure it to point to your cloud stack.

scbmeren commented 4 years ago

Thanks for the help.

sjbeskur commented 4 years ago

generic-network topology

scbmeren commented 4 years ago

The uam portal, for user authentication can run in the cloud, or it should be at coova gateway? Assuming i want to have several landing pages, ex: one for lobby hotel, one for the spa and another for the restaurant.

sjbeskur commented 4 years ago

In our deployments all authentication pages are served from the cloud. Only the redirect happens locally. To distinguish between "zones" (lobby, spa, etc) you can pass additional parameters or run separate instances of coova listening on different vlans. This is supported by Coova multi-lan feature.

josealgardataborges commented 3 years ago

We tried to host freeradius/captiveportal on the cloud and just chilli in appliance on customer network. But we now get a CORS error when trying to access the appliance chilli JSON interface (on port 3990) from the captive portal on the cloud.

[CLOUD = www.domainA.com (public ip)] freeradius
captiveportal (with JS)

[APPLIANCE = 10.1.0.1 (private ip)] CoovaChilli 1.6

Is this even possible? Anyone can help us fix this CORS issue?

vdemtcev commented 2 years ago

We tried to host freeradius/captiveportal on the cloud and just chilli in appliance on customer network. But we now get a CORS error when trying to access the appliance chilli JSON interface (on port 3990) from the captive portal on the cloud.

[CLOUD = www.domainA.com (public ip)] freeradius captiveportal (with JS)

[APPLIANCE = 10.1.0.1 (private ip)] CoovaChilli 1.6

Is this even possible? Anyone can help us fix this CORS issue?

Hello!

Can you show error text from browser console?

Maybe your problem the same https://github.com/coova/coova-chilli/issues/531

josealgardataborges commented 2 years ago

Hi @vdemtcev we have fixed the issue. Thanks for the help nevertheless.

raman-nbg commented 2 years ago

@josealgardataborges how did you fix this issue?

raman-nbg commented 2 years ago

@sjbeskur do you think it is possible to run CoovaChilli in the Cloud and then define a VPN that contains the Access Point and Coova Chilli? Virtually this would be the same LAN. Of course, we will need an Access Point that contains a VPN client for this case.

But do you think this is achievable?

josealgardataborges commented 2 years ago

@josealgardataborges how did you fix this issue?

We used the callback to call another javascript function and the error goes away.

dataType: "jsonp", jsonpCallback :"HOTSPOT.statusCallback"

and it just "works"

We tried this, based on what says on this page: https://coova.github.io/CoovaChilli/JSON/ on the "Interface to CoovaChilli" section, it reads:

If a callback parameter (callback=function) is present, then CoovaChilli will wrap the JSON output text in parentheses and prepend it with the callback function. The output will look like a function call with a JSON object passed as parameter. This will allow cross domain access to the JSON feed from JavaScript.