Hi Federico, You might be misunderstanding my tone, as I am certainly not complaining. I have had my nose in the GPL since 1994, and was one of the earliest supporters of Open-Mesh when it was a free and open project very similar in purpose and values to this one. I intensely accept the terms of the GPL, and what your are doing here is a welcome relief from the tyranny of Datto Networking that has stolen all of this public code and made it unusable by all of us early developers. I am ecstatic to have free access to what you have done here, and I feel you are doing the world a great favor by relieving it of the oppression of these wifi portal and network hardware companies that have jacked the consumer cost of Wifi through the roof.
The point of your project is to serve the needs of the users, and get adoption, right? I have already reprogrammed an Open-Mesh from scratch once, and if Loren Wolsiffer at WifiGator can find that code, he has offered to jump onboard also. Even if he doesn't, what you have already done here- the OpenWRT controller- *is* the heavy lifting that is required; the facelift on top of that was already easy to make once, and the creation of a distribution channel for ready-made hardware, as well as support for that configuration- this is my offer for contribution to your project with a number of programmers already on my staff working towards this very end. We were just working on this and adding crypto payment gateway to Cloudtrax before Open-Mesh sold us all out. Now we are here, and are willing to work for you, but we are not doing it as an academic project, we need it to generate revenue from sales to average technical users, we know marketing and sales, and are willing to spend the money to make this happen. So, to clarify, no I am not asking you to write any tutorial, I was only asking you to distribute the templates shown in your YouTube video since it would save everyone a lot of time, and if you would kindly consider taking the time to answer the original question, which is what you mean by "an ipam system for what you need to do is overkill" for auto assigning primary router IP's, we can get to work programming all of these things for OpenWISP. Thank you for your understanding, Stuart On Sat, Nov 10, 2018 at 3:38 PM Federico Capoano <[email protected]> wrote: > Stuart, I don't know if you read this page yet: > http://openwisp.io/docs/general/values.html > > In the goals section it is stated: > > *Create web interfaces that are easy to use even for people who have > limited experience with computer networking concepts (note: we are very far > from reaching this goal as of end of 2017)* > > Bold and red mine. > > we are still far from being able to do that. I know it sounds easy to you, > but it is not. If you think it's easy, go ahead and build it. I will be > happy you have proved me wrong. > > Right now I am focused on building the foundation, the core of OpenWISP. I > offer my help here on this mailing list for free in my free time, > volunteers write documentation for what they are able to do in their free > time. I am sorry we don't have configuration templates with 802.11s and > batman-adv ready for you. There are many people here using OpenWISP that > have probably built something like that and didn't share it nor took the > time to document it. I wish they did that but I can't force them to do it. > > I cannot stop working on my own priorities to build a batman-adv 802.11s > test network and write a tutorial on how to do it because 1. it takes a lot > of time to do properly and 2 that is not my priority at the moment, I hope > you understand that. > > The tones of your mail are inappropriate for an open source community. It > seems that you are writing a letter of complaint to the management board of > a company in which you are a shareholder. This is not a company. We haven't > sold you anything. We are giving away OpenWISP for free of charge under the > GPL3 license which states: > > The requirement to provide Installation Information does not include a > requirement to continue to provide support service, warranty, or updates > for a work that has been modified or installed by the recipient, or for > the User Product in which it has been modified or installed. > > [...] > > This program is distributed in the hope that it will be useful, > but WITHOUT ANY WARRANTY; without even the implied warranty of > MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > GNU General Public License for more details. > > If you want to look it for a commercial point of view, I really think you > should hire some developers who build what you want for you and interact > with us so we can improve the system in a way that allows you to do what > you want. There's no point on complaining on this list or asking us to do > things for you. It's an open source project and people are supposed to > contribute, or pay somebody who does what they want. There's no free lunch > here. > > Best regards > Federico > > On Sat, Nov 10, 2018 at 9:40 AM Stuart Trusty <[email protected]> > wrote: > >> Hi Federico! >> >> You know, every time someone says Santa doesn't exist, an elf gets eaten >> by a reindeer. Santa does exist! You just have to tell him what you want. >> >> So, I look at this, from a commercial perspective, and I see this great >> infrastructure that just needs to sit at a frozen production version and >> have a different, namely very Simple, UI over just a tiny handful of >> variables for the user. >> >> It only will need to manage 802.11s, and we need to standardize on some >> very cheap radios that anyone can use as far as a supported production >> version. I am getting test equipment in from China for both very >> inexpensive units and some wave-2 based radios. Then we need to get a >> nicer looking map to deploy the radios and dump a few stats and be able to >> change a few things like SSID or captive portal page from a simple control >> panel. This is all, really, along with maybe some RADIUS output formatted >> nicely, to get this mainstream. What we have here is like Linux itself, >> and the market wants to do is run an Application. >> >> If this simple config can become the end-deliverable, it is still >> OpenWISP, but maybe v3, something simple for everyone to use, and then >> users can flash whatever radios they want, or they can get the standard >> issue ones. I am ready to make our GPS-based mobile-app map work as a >> control panel for OpenWISP, and I have both an OpenWRT/RADIUS guy, a >> low-level firmware guy, and a group of core programmers ready to take this >> in a direction that we are ready to go out and sell. Maybe we set up a >> server for a cloud-based application of the simple version and people can >> pay a nominal fee to help financing some of this development. I don't >> think you want to carry this world on your shoulders forever for free, do >> you? >> >> I do wish you would give some of the technical details that you keep >> alluding to. Can we get some real templates for your 802.11s client and >> gateway, and batman-adv configs appended to this thread, and maybe a short >> paragraph on the conceptual replacement for ipam for new ip's for newly >> deployed units? Now that would Really be helpful for a lot of people, and >> the whole point here is we don't need everyone re-inventing the wheel. >> Right now it is just too complicated, and maybe it is all in your head and >> that is great, but down here in the trenches, we are not much smarter than >> the 10-year-olds that this needs to serve in these underdeveloped regions >> where this technology needs to land. >> >> Thanks for your consideration, and Ho Ho Ho! >> Stuart >> >> >> >> >> On Friday, November 9, 2018 at 10:25:33 PM UTC+5:30, Federico Capoano >> wrote: >>> >>> Stuart, an ipam system for what you need to do is overkill. >>> >>> I also want to make openwisp able to be used by anyone, (not a 10 years >>> old maybe :-P) and I assure you that if I had the resources to do it I >>> would have already done it .. but hey if it was so easy to build a system >>> so complex that is super easy to use and also free of charge someone else >>> would have probably done it earlier than me. >>> >>> It's cool that you want to join forces but I cannot lie to you and tell >>> you Santa Claus exists, Santa Claus does not exist and this can't be done >>> nor easily nor quickly. If you want to join forces and you have technical >>> people working for you, get them to participate in this community and >>> coordinate with us on specific issues like other contributors have been >>> doing and we'll be able to get some stuff done and improve the system in a >>> way that is useful for you. >>> >>> Federico >>> >>> >>> >>> On Friday, November 9, 2018 at 7:12:11 AM UTC+1, Stuart Trusty wrote: >>>> >>>> Hi Federico, >>>> >>>> I should mention that I have seen >>>> https://github.com/openwisp/django-ipam, >>>> https://github.com/openwisp/openwisp-ipam, and this post -> >>>> https://groups.google.com/forum/#!topic/openwisp/_TIF0bD8NYA ; you >>>> know what I am trying to accomplish- make it so a 10-year old can set this >>>> up- so, this isn't ultimately helpful. I saw your expo Twitter post, and >>>> pulled the PDF, it is very cool, and based on the request therein I am >>>> willing to join forces with you; we have a couple of people working on this >>>> stuff. But I need to turn this into something usable for everyone, and if >>>> you want to help me coordinate the spec to do this *easily*, I am happy to >>>> get it programmed. >>>> >>>> Thank you again, >>>> Stuart >>>> >>>> On Friday, November 9, 2018 at 8:42:07 AM UTC+5:30, Stuart Trusty wrote: >>>>> >>>>> Greetings all, >>>>> >>>>> When we set up a template for something like an 802.11s node, the way >>>>> I see this is that we must fixate it with a single IP like 192.168.1.1, >>>>> but >>>>> this isn't conducive to 802.11s, as each router needs 192.168.1.2, .3, >>>>> etc. >>>>> for it to function properly. >>>>> >>>>> However, the unit can't get on the MAC mesh without knowing its IP in >>>>> the first place, so using dhcpd in this scenario is a puzzle to me. >>>>> >>>>> Is anyone using some dynamic or incremental feature in a template to >>>>> assign IP's on a group of routers, or I am I thinking about going about >>>>> this in the wrong way? Clearly Google Wifi has solved this issue, what is >>>>> the best approach here? >>>>> >>>>> Thank you in advance, >>>>> Stuart >>>>> >>>> -- >> 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. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "OpenWISP" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/openwisp/cMMMEQ2d8eo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > 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.
