[Nodedb-interop] did you know about the meshboard implementation ?

[Ramon Roca]

All the ip provisioning is already automated in our case, avoinding 
users to get addresses for themselves, that's a jey for growing, if not 
peopletrend to take big ranges and on ipv4, you are dead. Instead we do 
provide a small range, and if they grow, of course it expands, therefore 
is much more efficient.

That's not only our experience, I would say that freenetworks.org got 
collapsed also because of that, all the IP ranges got allocated, 
regardless if the IPs were in use or not, and therefore, became useless.

I think that we do mainly are using a 10.138.0.0/15, but other orgs 
joined our network later, and had already their own ranges. What we don 
on the table you have seen is provide the ranges at the zones. The zones 
have hierarchies (province, county, city, village, neighborhood...), and 
when a zone starts to require IP addresses, get those addresses form the 
ranges at the zone level, and if they aren¡t, looks into the zone 
parents etc...

Really, oncve it works automatic, we don't care very much anymore, there 
is no risk of duplicates, so athought the info is in the database, I 
don't think that we do have a report of a summary of all the ranges in 
use, only what you have seen, of course that report can be reworked, but 
again, and that is another example, would be much better to provide an 
XML report for that, so later anyone who wants to develop any report in 
whatever tool of his preference, might simply parse the XML.

Ramon.


172.x.x are used for internall links, etc. We still do manage ranges, 
but there is no need to avoid duplicates..
10.x.x... are the public addresses

Al 09/01/10 17:42, En/na Mitar ha escrit:
> Hi!
>
>    
>> I'm now in Madrid, still having to deal with several legal issues...
>> :(.
>>      
> Hope they are going well ...
>
>    
>> I'm a bit confused on the focus, maybe we need to have a talk on that,
>> or maybe I'm missing something, but I'm getting the impression that we
>> are talking about user interfaces, apps for database management, even
>> firmware/protocol-oriented apps?
>>      
> I think that we are still finding focuses - in plural. For sure one and
> main is common node database schema. Some other I proposed on the wiki.
> If they catch OK, if not, also OK.
>
> And I think it is OK that we exchange also other ideas (not just schema
> and attributes there) about our node database systems. To work on
> collaborative knowledge in this field.
>
>    
>> but to me the key point now is to build an architecture to build the
>> capability to interact between apps by describing an XML schema.
>>      
> I completely agree. This is our primary and most important focus.
>
>    
>> Just by referemce, because this could be incomplet: Although we do
>> export zones in "CNML", and we do manage IP ranges, currently we don't
>> export this attribute, so the schema might have to be enhanced....
>>      
> I am not really sure how to read this. A lot of data. :-)
>
> So if I understand you are using this IP ranges (not completely):
>
>
> 10.139.0.0/16
> 172.25.0.0/16
> 10.228.150.0/24
> 10.228.129.0/24
> 10.228.128.0/17
> 172.16.0.0/14
> 172.20.0.0/14
> 172.24.0.0/14
> 172.28.0.0/14
> 172.16.0.0/12
> 10.35.80.0/21
>
> Is this correct? How often do you change this? Would it be enough just
> to enter this into the wiki? Could you do it?
>
> For now maybe we could just enter things into the wiki manually and then
> later on when we define schema I could make this wiki page dynamic so
> that it would aggregate data automatically from all networks.
>
> (And yes, that list is also just for reference, that is why there is
> also a contact address so that you can get into the contact for more
> precise or current information.)
>
>    
>> I think we should start working on XML/DTD descriptions,
>>      
> Yes, but we should first try to get everybody who wants to participate
> in this. No? Maybe we could try to get somebody from Greece? And others?
>
> Maybe meshboard could describe also their schema on the wiki?
>
> http://interop.wlan-lj.net/
>
>    
>> I have a dream: A Service Oriented Arquitecture and people developing
>> components for that, able to interoperate because able to speach a
>> common language. so instead of relying on isolated/self developed apps
>> installed on a given server, able to take advantage of the could
>> computing  ;)
>>      
> Yes. That is why I also added to the wiki not just schema but also that
> we should work on data aggregation/exchange. Work on this could simply
> mean just agree that everybody would use same RESTful way of doing this,
> for example.
>
>
> Mitar
>