HI Federico:
thanks for the procedure, will give it a try.

about the driver, I too dont have much info, as the driver code comes as a 
bin package, except the scripts to configure them. This is somewhat similar 
to madwifi, with additional custom config variables. I too couldnt find 
much info about it in google. I was assuming you would be aware of this :-)

thanks
Kumar

On Sunday, 2 April 2017 14:56:51 UTC+5:30, Federico Capoano wrote:
>
> Hi Kumar,
>
> You should fork netjsonconfig <https://github.com/openwisp/netjsonconfig> 
> on github, then edit this section: 
> https://github.com/openwisp/netjsonconfig/blob/master/netjsonconfig/backends/openwrt/schema.py#L120-L126
> Commit the result and push it on your fork, then proceed by installing 
> manually your fork in your instance, with:
>
> cd /opt/openwisp2
> source env/bin/activate
> pip install 
> https://github.com/<your-github-user>/netjsonconfig/tarball/master
>
> We could also allow the ansible role (ansible-openwisp2 
> <https://github.com/openwisp/ansible-openwisp2>) to install the 
> development versions of the base libraries and modules from different 
> sources so you could avoid to do this step maually, but I don't have time 
> to add this feature right now (although I will keep it in mind for the near 
> future).
>
> Bytheway, I didn't know this driver. I tried looking on google right now 
> but couldn't find much, do you have any useful link of examples of use of 
> this driver with OpenWRT or LEDE that I can take read?
>
> Federico
>
> On Sun, Apr 2, 2017 at 8:46 AM jdroid <[email protected] <javascript:>> 
> wrote:
>
>> HI:
>> With the latest checked out ansible openwisp2  package, I am able to hack 
>> the organisation to assign different configuration templates to different 
>> models of AP/Routers.
>>
>> Moving on to adding radio and interface details on a configuration 
>> template, I run into another issue. In a new template for configuration, I 
>> add new radio section and in the radio section the driver field pull down 
>> menu, I didn't find the "qcawifi" value which is required for new QCA based 
>> wlan driver. I could add this enum option in the 
>> netjsonconfig/backend/openwrt/schema.py , but on retsrating the openwisp 
>> package, I don't see the value getting listed in template radio section 
>> pull down menu.
>>
>> So if I add or modify contents in 
>> netjsonconfig/backend/openwrt/schema.py, what is the procedure I should 
>> follow to see these modified values. I am working on ansible checkout code.
>>
>> Any help is appreciated,
>>
>> thanks
>> Kumar
>>
>> On Friday, 31 March 2017 19:46:23 UTC+5:30, Federico Capoano wrote:
>>
>>> On Fri, Mar 31, 2017 at 3:47 PM jdroid <[email protected]> wrote:
>>>
>>>> btw.. do you have plans to support openwrt image upgrade (firmware 
>>>> upgrade) to these registered openwrt devices.
>>>>
>>>
>>> Yes but I don't know when I will be able to pull that off.
>>>
>>> Hopefully before the end of 2017 but it depends on how many contributors 
>>> we can onboard.
>>> The more contributors we get and the more they will help me with less 
>>> complicated tasks, the more I can focus on big features like that.
>>>
>>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.

Reply via email to