ROBIN -  Open Source Mesh Network Forum Index ROBIN - Open Source Mesh Network
users community forum
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CoovaChilli on OrangeMesh or MeshConnect

 
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> OrangeMesh Dashboard
View previous topic :: View next topic  
Author Message
Ads






Posted: Thu Sep 21, 2017 8:13 pm    Post subject: Ads

Back to top
fronzo
User
User


Joined: 23 Apr 2009
Posts: 19

PostPosted: Thu May 07, 2009 9:33 pm    Post subject: CoovaChilli on OrangeMesh or MeshConnect Reply with quote

Hi everybody,

I was wondering if OrangeMesh or MeshConnect integrate any option to be used to enable ChilliSpot in Robin, in order to redirect users to a captive portal and allowing to identify them against a radius server.

In other words I'm looking for a setting as the "captive portal providers / other radius provider" in the Open Mesh Dashboard.

If such a feature is unavailable within OrangeMesh or MeshConnect, is there any way to enable chilli manually?

Thanks!
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Fri May 08, 2009 4:26 am    Post subject: Reply with quote

I too want to know the answer to this question!

This is all i could find

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
funchip
Moderator
Moderator


Joined: 12 Sep 2008
Posts: 267
Location: Sacramento, California, USA

PostPosted: Sat May 09, 2009 1:07 am    Post subject: Reply with quote

Yes, the feature is available on MeshConnect. To test CoovaChilli setting, go to a demo site
Only registered users can see links on this forum!
Register or Login on forum!



The dashboard has a migration feature that allows you to import your network from open-mesh network easily. So use that function for your convenience...

By the way, to redirect your nodes from open-mesh to the demo dashboard, make sure you turn on the SSL option on the MeshConnect setting, and set the alternative dashboard check-in URL on open-mesh as below
Code:
ssl.perfora.net/wifimesh.trigmax.com/meshconnect


The demo site is for "demo" only, as we are running test and making changes without notice. So please don't use the site as a production service. We expect you to download the package and run the dashboard on your own server.

Let me know if you have any problem.
Back to top
View user's profile Send private message
fronzo
User
User


Joined: 23 Apr 2009
Posts: 19

PostPosted: Sat May 09, 2009 10:16 am    Post subject: Reply with quote

Thanks a lot funchip.

I had already found the latest version of MeshConnect and installed it on a test server. It works great! I still haven't tested the captive portal redirection but I have no doubt it works as expected.

Instead of forwarding to the new dashboard from open-mesh I preferred to update my nodes manually adding the new dashboard on the DFE file. With such a configuration I didn't need to enable SSL on my test server.

The dashboard is really nice. There are only a couple of features that I feel really useful in the Open Mesh dashboard which don't seem to have been implemented in MeshConnect: the graph showing the bandwidht usage over time, the list of the connected users and, above all, the network diagram showing the paths used by the nodes to reach the gateways.

Great work anyway. Keep up with it!

Thanks very much!
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Tue May 12, 2009 9:21 pm    Post subject: Reply with quote

I had some time so I gave this meshconnect a go. The fact it allows coova settings is a huge plus, what I'm having an issue with is every 10 minutes on the dot I'm getting logged out of a chillispot system and thrown back to the splashpage. I'm confident this is an issue with the dashboard because the same routers with the same captive portal settings on Open-Mesh dashboard is not having the issues.

Any thoughts?
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Thu May 14, 2009 6:46 am    Post subject: Reply with quote

Spent alittle more time with it. The meshconnect dashboard is setting something in coova that's causing the inactivity attribute to work incorrect. If I bump up my inactivity value in my billing back end I can up the time it happens. If I delete the entry all together it falls back to the default 10 mins. I guess I have to figure out how to edit the meshconnect php files to setup coova correct.
Back to top
View user's profile Send private message
funchip
Moderator
Moderator


Joined: 12 Sep 2008
Posts: 267
Location: Sacramento, California, USA

PostPosted: Thu May 14, 2009 4:36 pm    Post subject: Reply with quote

Can you SSH to the node and capture two files when the Coova operaton failed?
/etc/update/received.clean
and
etc/update/update.arg

The files should be updated every 5 minutes.

Dashboard mainly passes the settings to the node. There is a possibility that the settings were passed over incorrectly or incompletely.
Back to top
View user's profile Send private message
lucianoinacio
User
User


Joined: 30 Mar 2009
Posts: 12
Location: Brasil

PostPosted: Fri May 15, 2009 4:15 pm    Post subject: Reply with quote

i use chilli with radius.

to cancel user i do it in radius.
In meshconnect how can i disconnetc the user?? How can i do it in dashboard??
Any table in msql?? any downloaeded file??

Any sugestion??


Luciano Inacio
Back to top
View user's profile Send private message
funchip
Moderator
Moderator


Joined: 12 Sep 2008
Posts: 267
Location: Sacramento, California, USA

PostPosted: Sun May 17, 2009 11:40 pm    Post subject: Reply with quote

On MeshConnect, the client access control is done by the captive portal daemon (nodogsplash, coovachilli, etc). I believe chilli daemon should be the one to block the client's access in your case. Dashboard is doing nothing more than passing the admin setting to the ROBIN firmware, which in turn sets the operation of chilli daemon.

I'm new to the chilli world, too. So I'm also listening... Smile
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri May 22, 2009 6:12 am    Post subject: Reply with quote

I took a look at those files you told me to examine. Everything appears normal but I've spoke with another user that is seeing the same thing. It looks as if coova is restaring. I can't be certain yet but something is for sure wrong when I switch from Open-Mesh to Meshconnect. Everything works just fine with OM, but the moment I switch over it starts to act up. By default my captive portal/free-radius setup has a 10 minute time out for inactivity. I've timed it and almost exactly every 10 minutes I get the splash page/login using Meshconnect even though I'm not inactive. I then went and raised the 10 minute variable for the user in mysql to 20 minutes and I'm certain it went almost 20 minutes.

I need to do further testing, but I'm wondering if Open-Mesh is setting something that MeshConnect is either not changing or not seeing. When the nodes switch from OM to MC, does the entire coova config get altered. I've looked into the code and it appears only certain things are changing. I guess I should do a comparision of OM settings to MC.

Is anyone else actually using MC with a captive portal backend? I'm also trying to bring back the map function since most of the code is still there.
Back to top
View user's profile Send private message
funchip
Moderator
Moderator


Joined: 12 Sep 2008
Posts: 267
Location: Sacramento, California, USA

PostPosted: Fri May 22, 2009 6:38 am    Post subject: Reply with quote

@foxtroop11, frankly, I don't know the answer rigth off my head. Now, if willing, we can do the debugging collaboratively. Can you do the following things for me:
1. Set up a temporary account for me on your radius/UAM server.
2. Show me your setting on both open-mesh and meshconnect dashboards.
3. Allow me to run the test on your radius/UAM server using the temporary account and duplicate the case.

You may want to send me the setting in a private message. I'll do a test and post the finding afterward.
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri May 22, 2009 7:23 am    Post subject: Reply with quote

NP, i'm game for anything. I looked in my PM before looking at this so I owe you more info. I think I see what your saying. I'll create a user for you on my end and tell you the settings for my hotspot stuff.

BRB, getting updates from Open-Mesh now on fresh flashed OMP1.
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri May 22, 2009 9:13 am    Post subject: Reply with quote

Ok, think I see some of the problem.

Here is a portion of the recieved.clean from open-mesh

Code:
#@#config cp_switch
main.which_handler 5
#@#config chilli
agent.service otherchilli
agent.radiusserver1 
agent.radiusserver2
agent.uamserver
agent.uamurl /hotspotlogin.php
agent.uamsecret 
agent.radiussecret 
agent.radiusnasid 
agent.uamurlextras
agent.uamdomain
agent.custom1
agent.custom2
agent.custom3


now is here almost the same portion from meshconnect, I notice this main.which_handler is 6 and not 5. Wonder if that is part of the problem.

Code:
#@#config cp_switch
main.which_handler 6
#@#config chilli
agent.radiusserver1
agent.radiusserver2
agent.uamserver
agent.uamurl /hotspotlogin.php
agent.uamsecret 
agent.radiussecret 
agent.radiusnasid
agent.uamurlextras
agent.uamdomain
agent.custom1
agent.custom2
agent.custom3
agent.service otherchilli
#bogus2 772827811
Back to top
View user's profile Send private message
funchip
Moderator
Moderator


Joined: 12 Sep 2008
Posts: 267
Location: Sacramento, California, USA

PostPosted: Fri May 22, 2009 6:31 pm    Post subject: Reply with quote

I think @foxtroop11 has nailed down to a key point. Currently, MeshConnect dashboard sets the "cp_switch -> which_handler" field by
5 for CoovaAAA
6 for OtherChill

That could be incorrect. Should the field be set to "5" in both cases, or the value needs to be flipped...

Antonio, can you help?

Thanks!
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri May 22, 2009 7:20 pm    Post subject: Reply with quote

Dont think that's it. I just did further testing and although your dash sends out an alternate number setup it's actually doing the same thing as Open-Mesh. It's something else as I went in and flipped the number and it then made the node use coovaa aaa which actually worked but still did the 10 minute thing and seems to be coova restarting.
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri May 22, 2009 7:36 pm    Post subject: Reply with quote

I don't think anything is wrong with the way meshconnect sets up coova. I think it's something else.


Last edited by foxtroop11 on Fri May 22, 2009 9:55 pm; edited 2 times in total
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri May 22, 2009 9:04 pm    Post subject: Reply with quote

Thought I had it, back to the drawing board.


Last edited by foxtroop11 on Fri May 22, 2009 10:13 pm; edited 3 times in total
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Fri May 22, 2009 9:10 pm    Post subject: Reply with quote

Quote:
Sorry for so many posts. I hope this is helping someone and I'm not the only one with the problem.


Go for your life Wink
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri May 22, 2009 9:44 pm    Post subject: Reply with quote

Once again, thought I had it but it's still doing it.
Back to top
View user's profile Send private message
funchip
Moderator
Moderator


Joined: 12 Sep 2008
Posts: 267
Location: Sacramento, California, USA

PostPosted: Sat May 30, 2009 2:21 am    Post subject: Reply with quote

The latest MeshConnect dashboard has an option to select CoovaAAA and other Chilli. When doing the test, I noticed the same problem as pointed out by @foxtroop11. Basically CoovaAAA would interrupt the browsing and ask for user name/password every 10 minutes or so.

Currently, MeshConnect sets following parameters if CoovaAAA is selected when a node checks in:

cp_switch.main.which_handler = 5
chilli.agent.service = coova_aaa

Plus other parameters that user entered to the dashboard.

@Antonio, is that correct, or anything else needs to be set?

Thanks.
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Sat May 30, 2009 7:09 am    Post subject: Reply with quote

As far as I can tell that is fine. I tried to explain what I think the problem is. It's all in the update system and if I comment out the section in the update file it stops coova from restarting. Watch the log files and you will see that every 10 mins the node pulls down from the server an update, or it thinks there is an update even though nothing changes and then restarts everything. When the node is pointed at open-mesh it doesn't do this.

Now here is the next problem. If I build a firmware using the wiki and alter the /etc/config/general file to point at my server from the get go it doesn't work. I can ssh into the router and run "update" and see that it bombs out. If I change the config file back to checkin.open-mesh.com and run update it runs fine. I'll let it pull in updates and reboot and it shows up on my open-mesh dashboard. I'll then ssh back in and change it back to my server IP and run update. Update will then run with several errors since meshconnect is old maybe?. It atleast runs and then switches to meshconnect, but this makes no sense to me why it won't do it from the get go. I have nothing against open-mesh but in the event the entire web site crashes I don't want all my nodes being run by a system other then my own.
Back to top
View user's profile Send private message
beone
Skilled User
Skilled User


Joined: 12 Apr 2009
Posts: 207

PostPosted: Sat May 30, 2009 8:54 am    Post subject: Reply with quote

foxtroop11 wrote:
As far as I can tell that is fine. I tried to explain what I think the problem is. It's all in the update system and if I comment out the section in the update file it stops coova from restarting. Watch the log files and you will see that every 10 mins the node pulls down from the server an update, or it thinks there is an update even though nothing changes and then restarts everything. When the node is pointed at open-mesh it doesn't do this.

Now here is the next problem. If I build a firmware using the wiki and alter the /etc/config/general file to point at my server from the get go it doesn't work. I can ssh into the router and run "update" and see that it bombs out. If I change the config file back to checkin.open-mesh.com and run update it runs fine. I'll let it pull in updates and reboot and it shows up on my open-mesh dashboard. I'll then ssh back in and change it back to my server IP and run update. Update will then run with several errors since meshconnect is old maybe?. It atleast runs and then switches to meshconnect, but this makes no sense to me why it won't do it from the get go. I have nothing against open-mesh but in the event the entire web site crashes I don't want all my nodes being run by a system other then my own.



Maybe we should ask for the most recent source code of the open-mesh dashboard, giving us the ability to compare it with Meshconnect? Smile
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Sat May 30, 2009 10:08 am    Post subject: Reply with quote

Quote:
Maybe we should ask for the most recent source code of the open-mesh dashboard, giving us the ability to compare it with Meshconnect? Smile


I did read a similar post a long time ago on the same topic

From memory the code was closed and that status wasn't going to change?

From memory there we some reasons given for this!
Back to top
View user's profile Send private message
rugby
User
User


Joined: 26 Jun 2009
Posts: 41

PostPosted: Tue Jun 30, 2009 11:35 am    Post subject: Any solution to this issue Reply with quote

Hi

I'm experiencing the same issue with Chilli restarting every 10 minutes. Has anyone managed to solve the problem yet?

What is curious is that it only happens every other "checkin" to meshconnect, in the logread output the unit seems to think that the "root" password has been changed and therefore needs updating causing chilli to restart, the root hasn't been changed and the update is simply resetting it to the same password.

Any thoughts would be appreciated.

Thanks
Back to top
View user's profile Send private message
Linzi
User
User


Joined: 29 Jan 2009
Posts: 8

PostPosted: Fri Jul 03, 2009 5:03 pm    Post subject: Reply with quote

fronzo wrote:
Thanks a lot funchip.

I had already found the latest version of MeshConnect and installed it on a test server. It works great! I still haven't tested the captive portal redirection but I have no doubt it works as expected.

Instead of forwarding to the new dashboard from open-mesh I preferred to update my nodes manually adding the new dashboard on the DFE file. With such a configuration I didn't need to enable SSL on my test server.

The dashboard is really nice. There are only a couple of features that I feel really useful in the Open Mesh dashboard which don't seem to have been implemented in MeshConnect: the graph showing the bandwidht usage over time, the list of the connected users and, above all, the network diagram showing the paths used by the nodes to reach the gateways.

Great work anyway. Keep up with it!

Thanks very much!

the captive portal redirection sounds interesting, where I can download the latest version to test out?
thanks.
Back to top
View user's profile Send private message
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri Jul 03, 2009 5:26 pm    Post subject: Reply with quote

This should be it,

Only registered users can see links on this forum!
Register or Login on forum!



I'm testing something else at the moment since it was giving me problems. Let me know if you need help.
Back to top
View user's profile Send private message
Linzi
User
User


Joined: 29 Jan 2009
Posts: 8

PostPosted: Wed Jul 08, 2009 3:01 pm    Post subject: Reply with quote

foxtroop11 wrote:
This should be it,

Only registered users can see links on this forum!
Register or Login on forum!



I'm testing something else at the moment since it was giving me problems. Let me know if you need help.

got it, thanks.
good luck with the new stuff you are testing.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> OrangeMesh Dashboard All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
c d
e



Powered by phpBB © 2001, 2005 phpBB Group

Abuse - Report Abuse - TOS & Privacy.
Powered by forumup.it free forum, create your free forum! Created by Hyarbor & Qooqoa
Confirmed

Page generation time: 0.142