Hi Federico,
A lot of question in the same mail, let's start :
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.
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 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.
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.
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.
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.
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.
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
Warmly
Le jeudi 9 février 2017 18:52:39 UTC+5:30, Federico Capoano a écrit :
>
> Hey Xavier,
>
> On Thursday, February 9, 2017 at 5:07:58 AM UTC+1, Xavier Maysonnave wrote:
>
> [cut]
>
>
>> Right now I've successfully generated and flashed the firmware based on
>> LEDE-17.01 RC with the openwisp-config.
>> As soon as the router will talk to the controller I'll provide some
>> feedback.
>>
>
> Have you encountered a roadblock of some sort? If you successfully
> generated the firmware and flashed it on a router, the router should be
> able to connect to openwisp2 almost straightaway.
>
> I'm quite interrested with your architecture maybe we can open new threads
>> on this forum where one could describe his requirement.
>> I think it could help Federico to address our various needs.
>>
>
> Yes, this information is interesting for all the parties involved if we
> want to create an ecosystem of interoperable tools.
>
> I try to achieve a Freeradius, multi-role system, monitored, vouchers,...
>>
>
> What's a voucher?
>
> Do you use Freeradius as is or do you use some frontend web interface on
> top of it?
>
>
>> Right now I would prefer to have a captive portal at the router level.
>>
>
> That's interesting. Can I ask you what type of captive portal software are
> you using there?
>
--
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.
