Hey Xavier On Friday, February 10, 2017 at 10:41:00 AM UTC+1, Xavier Maysonnave wrote: ...
> 1 - Right now the router do not contact the controller. I got the > following from logread : > Failed to connect to controller during registration: curl exit code 48 who > means as far as I found. > CURLE_UNKNOWN_OPTION (48) > An option passed to libcurl is not recognized/known. Refer to the > appropriate documentation. This is most likely a problem in the program > that uses libcurl. The error buffer might contain more specific information > about which exact option it concerns. > Weird. On the firmwares I'm compiling I get the following CURL version: 7.40.0, what about you? Check this with: curl --version Could you paste the contents of /etc/config/openwisp (removing sensitive data)? Are you compiling from the LEDE RC? I started to study the openwisp-config code and realized some assumptions > like the SSID should LEDE or OpenWrt. I wanted to use my own numbering > system. > I'm not following you very well. > I defined a default configuration at the controller level with the > appropriate MAC address, tested with both OpenWrt and OpenWisp backend, a > bit lost here as my backend is LEDE with OpenWisp. > Use the OpenWrt backend, OpenWisp is for OpenWISP-Firmware 1.3 (I'm adding a note to make this more explicit). > I don't know yet what the purpose of the Configuration key as I defined in > the router the shared secret I use in my ansible-openwisp2 playbook shared > secret who seems to be different. > The shared secret is for auto-registration. Once registered, each device has its own uuid and key. See the "Introduction to OpenWISP2" <https://www.youtube.com/watch?v=MY097Y2cPQ0&index=2&list=PLPueLZei9c8_DEYgC5StOcR5bCAcQVfR8> screencast for more information. > 2 - The system I want to build will manage pre-paid vouchers for visitors > and post-paid for regular users. > Users will have multi-role that way we can manage accounting at various > levels. > Ok, thx for the info. > 3 - Yes I want to use Freeradius, applying the AAA paradigm. I need a web > frontend to manage that as well as a monitoring system. > ok > 4 - I considered pfSense but it seems to me a little bit overkill to use > it only for its captive portal features I would prefer to use coova-chilli > at the router level (OpenVPN rather than PPTP). > pfSense seems also a bit difficult or expensive to be hosted on a VPS. > mm not sure I agree on the expensive claim, but surely it's a different operating system that you need to learn, so if you are used to linux you will want to stick with that. 5 - I evaluated Daloradius and Radiusdesk : > - Daloradius is quite easy to deploy but do not target the scale we want > to reach > - I like the frontend of Radiusdesk > - anyway OpenWisp use python, as scalability in its DNA, the imagenerator > is here to manage multiple targets, it'll will be easier to put in a > versioning system and open the gate for a CI integration. > - right now I'm not sure if Django is the way to go as micro-framework > like flask seems to be more flexible > You quite a lot to choose from. The only suggestion I can give you is to pay attention to stability, ecosystem, community and documentation. Federico -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
