Luca Dionisi | 2 Jun 14:35 2014
Picon

0.9.1

I released version 0.9.1
It is to correct a malfunction in the dns-to-andna redirector, that appeared in a openwrt device.
I consequently updated instructions on dyne.org wiki.

--Luca
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
Luca Dionisi | 3 May 17:57 2014
Picon

netsukuku beta

I hereby release the first beta version of netsukuku.

The suite of programs and libraries is composed of 6 packages. The tarballs can
be downloaded from the following links.
 http://download.savannah.gnu.org/releases/netsukuku/tasklet-0.9.tar.gz
 http://download.savannah.gnu.org/releases/netsukuku/zcd-0.9.tar.gz
 http://download.savannah.gnu.org/releases/netsukuku/netsukuku-rpc-0.9.tar.gz
 http://download.savannah.gnu.org/releases/netsukuku/andns-rpc-0.9.tar.gz
 http://download.savannah.gnu.org/releases/netsukuku/ntkresolv-0.9.tar.gz
 http://download.savannah.gnu.org/releases/netsukuku/netsukuku-0.9.tar.gz

Instructions to download, build and install on a ubuntu machine are located here:
 https://lab.dyne.org/Netsukuku_Dev/beta/ubuntu

It is possible to install and run also in a router running OpenWRT.
Instructions are provided that guide you to the compilation and flashing of a
fresh new firmware with the programs and libraries already installed.
 https://lab.dyne.org/Netsukuku_Dev/beta/openwrt

Maybe, a new web site will come up soon.

My next step will be wait for your feedback. Report bugs, request details on
documentation, ask for inclusion of features and the like. All of this please
send to the following mailing list:
 netsukuku-vala-qX2TKyscuCcdnm+yROfE0A@public.gmane.org

The first final version of netsukuku (1.0) will be released on August 1st.
During this time I will add features. When bugs are reported I will try and
fix them and release as soon as possible, e.g. version 0.9.1.

--Luca

_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
a310 p0 | 4 Apr 15:55 2014
Picon

missing link -- RFC Ntk_NDN

Hello.

I have read the news on the homepage ( http://netsukuku.freaknet.org ).
I could not understand the first point which I am quoting here:

  <<

        1. CCNx prototype of NDN protocol: http://www.ccnx.org/
          comment: the project is a bit hyped-style ("we are the world"),
          but there is a good international effort on it, could be good as
          a way to have Ntk engaged in a larger context.

  >>

I found the "RFC"  https://lab.dyne.org/Ntk_NDN .

It is very insightful and by reading it I understood what was meant by
"CCNx prototype

of NDN protocol".

Please, to make the message clearer to the readers, the sentence should

contain a link to  https://lab.dyne.org/Ntk_NDN  rather than www.ccnx.org .

Cheers.

P.S.  the link  -- http://lists.dyne.org/mailman/listinfo/netsukuku --
 on https://github.com/Netsukuku/netsukuku and on
http://netsukuku.freaknet.org/?pag=contacts should be changed to  --
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku -- as
the former link points to a 404 NOT FOUND page, while the latter works
fine.
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku

Luca Dionisi | 4 Apr 10:17 2014
Picon

ANDNS protocol

Netsukuku (the Vala port) now has a server implementation of the ANDNS
protocol [0]. It runs inside the ntkd daemon.

There is the library libntkresolv. This implements the client part of
ANDNS protocol. This library (and the tools below) can be used also by
a computer that is not running the ntkd daemon, that is, a computer
that is not part of the netsukuku network. Only requirement is that
you have a route to reach a node that is part of it.

There is a tool named ntk-resolv that depends on libntkresolv. The
user can use it to query the ANDNA distributed database.

There is the library libnss_andna. This is a module, again dependent
on libntkresolv, that the GNU Name Service Switch (part of the GNU C
library) can use as a mean to resolv a computer name. This means that
a program calling gethostbyname (or the newer getaddrinfo) is able to
resolv names of the ANDNA domain (as long as it runs on a GNU system).

Still missing is a wrapper acting as a DNS server that transforms a
DNS request into a ANDNS one and pass it to a ANDNS server. And then
passes back the answers.

So, the packages forming the suite are now:
 tasklet [1]
    lightweight cooperative multithread system.
 zcd [2]
    zero configuration dispatchers: framework for remote procedure calls.
 netsukuku-rpc [3]
    model for the rpc; the messages that the daemon exchanges with
other nodes forming the netsukuku.
 andns-rpc [4]
    model for the rpc; the ANDNS protocol is based on it.
 ntkresolv [5]
    client part of ANDNS protocol; tools.
 netsukuku [6]
    the daemon.

I will, as time permits, prepare packages for openwrt and update the
instructions [7].

[0] http://netsukuku.freaknet.org/index.php?pag=documentation&file=main_documentation/ntk_rfc/Ntk_andna_and_dns
[1] bzr://bzr.savannah.nongnu.org/netsukuku/tasklet
[2] bzr://bzr.savannah.nongnu.org/netsukuku/rpc
[3] bzr://bzr.savannah.nongnu.org/netsukuku/rpcntk
[4] bzr://bzr.savannah.nongnu.org/netsukuku/andns-rpc
[5] bzr://bzr.savannah.nongnu.org/netsukuku/ntkresolv
[6] bzr://bzr.savannah.nongnu.org/netsukuku/ntkd
[7] https://lab.dyne.org/Netsukuku_Dev/vala/flashing_notes4
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku

Luca Dionisi | 5 Mar 10:03 2014
Picon

Status Report

The porting of Netsukuku to Vala has been completed.

Almost! The DNS wrapper is still missing. It is a piece of code that
listens to standard DNS queries and forward them to the ANDNA system.
But there are tools that can query directly ANDNA.

Also, the Internet Sharing is still missing. Consider also that in the
python implementation this feature was rough and poorly tested yet.

So, yes, I consider the porting really complete.

Obviously the code has to be tested, debugged, fixed, tested again, etc etc.

The daemon is misbehaving in a number of ways.
There are a number of testsuites here and there for various parts of
the operations but they are not exhaustive at all. So it was really
expected.

I will inform the list next time when the daemon will behave correctly
under a great number of scenarioes.
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku

Luca Dionisi | 4 Mar 23:10 2014
Picon

Status report

The porting of Netsukuku to Vala has been completed.

Almost! The DNS wrapper is still missing. It is a piece of code that
listens to standard DNS queries and forward them to the ANDNA system.
But there are tools that can query directly ANDNA.

Also, the Internet Sharing is still missing. Consider also that in the
python implementation this feature was rough and poorly tested yet.

So, yes, I consider the porting really complete.

Obviously the code has to be tested, debugged, fixed, tested again, etc etc.

The daemon is misbehaving in a number of ways.
There are a number of testsuites here and there for various parts of
the operations but they are not exhaustive at all. So it was really
expected.

I will inform the list next time when the daemon will behave correctly
under a great number of scenarioes.

Finally I want also to introduce a tool that I made to help the
debugging by providing a visual representation of alot of the status
information that can be queried to the nodes.
Attached is a sequence of images that shows the tool in action. It
monitors a node, reports its neighbors, its routing knowledges, the
coordinators of gnodes, border nodes, andna records, etc etc.

--Luca
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
Luca Dionisi | 20 Feb 17:33 2014
Picon

Participation rewards

Netsukuku: Participation rewards

A new feature of Netsukuku will allow the participants to give a
reward in money to the owners of the nodes that permit them to reach
their favourites contacts and services.
This is on a completely voluntary basis. The network remains free of
charge for everybody.

There are many projects today that have the goal of building a
self-sustaining network where participants are incentivised to improve
the network. The key point in all of them is to reward not just the
provider of a service, but the owner of the nodes that make it
possible in the first place the connection between client and server.
Many of the proposed payment schemes try to reproduce how the bitcoin
transactions work, but with a new digital crypto-currency.

Netsukuku will take no effort to create a new currency, and not even
be tied to the best payment solution that we could find. It will just
make it possible for a node owner to reward the right people. More
precisely, the owners of the nodes that are in a precise instant
connecting him to his favourite friends.

Netsukuku will not, of course, expose their identity, but only a
payment address that is at their disposition.

The actual payment processor can be anything that has the required
properties. There can be at the same time more than one.

A first implementation of this will use Bitcoins, the real thing. With
most probability it will use Coinbase services, because it is good for
us to have a practical way of enabling micro-payments with no fees and
with low delay confirmations.

At the moment I figured out 2 types of payment procedures. One is
initiated by the client at his will. One is required by a service
provider.

Client-initiated procedure
====
A node owner, say A, uses frequently a certain service hosted on the
node of another participant, say B. Or she speaks with B owner via a
VoIP application that contacts directly the node B.
Supposedly, A might be willing to donate, every now and then, some
money to the nodes that make her communications possible. Because she
wants them to keep on running their nodes and possibly improve their
links.
Node A will send a particular message to node B; this will trace the
nodes that make up the best route right now, and obtain from them a
Bitcoin address (or other payment address, but for now we refer to
this). Node B responds to A with the list of addresses and A can make
the payment.
Obviously A can make this donation whenever she likes and for the
amount she likes. A good strategy for A would be to make frequent
micro-donations during the very same hours when she uses the most the
service that she cares.

Service-required procedure
====
The owner of node S (S=server) provides a service to his customers. He
wants to get paid for this service based on the volume of trafic that
is used.
S might be willing to share (a part of) his income with the nodes that
form the link from his server to his customer. Because he wants to
incentivise them to stay and new nodes to arise for him to be
reachable by a broader mass of potential customers. Hence, S
advertises that he is providing a service through this channel with
this feature.
A client C sends a particular message to S; this will trace the nodes
that make up the best route right now, and obtain from them a Bitcoin
address. Node S will append its own Bitcoin address and respond to A
with the list of addresses and the amount of payments that he has to
do to each of the addresses per unit of trafic. Furthermore, the nodes
that form the link will be notified of the IP address of C and S and
the amount that they are going to receive per unit of trafic. These
hops might then verify every now and then the payments and (if they
want) temporarily block the trafic on this flow if they don't receive
the payment.
A consideration: C could "cheat" and not make the payment to the hops,
because he thinks that they will not check. But for sure he will not
be able to cheat S, because he will verify, of course, and deny the
service. So S, if he really wants to reward and incentivise the hops,
could ask for a slight bigger price for his service and then take care
on his own to donate back to the bitcoin addresses that he receives
with the message from the client C.

What has been briefly exposed until now is plausibly feasible with any
payment processor that possesses some properties.
Now let's take the assumption that the Bitcoin network is used.
Here are some considerations about the problems that arise with this choice.

First, not all the nodes are required to participate to the service.
But only those who participate can be rewarded or initiate a payment.

When a node participate to the service, the only requirement is to be
configured with a Bitcoin address where he can receive payments. It is
advised to generate a new valid address for each payment, if the node
is able to do it; but it is not mandatory.

If a node wants to be able to check the payments then he needs to get
connected to the bitcoin network. Or at least to get connected from
time to time to the Internet and use some host which provides
informations, such as blockchain.info. This requirement is not
particularly hard to satisfy. For example it's enough if the owner of
the node has got also a computer which is connected to both the
netsukuku network and to the Internet.

If a node has trouble to get to the Internet but wants to participate
he can do. It will not be able to check the payments, so it shall
never block the trafic. Nevertheless it will probably receive
payments, because when the network is highly dynamic it's hard for the
client to know in advance which hops will verify the payments and
which ones will not.

A node that wants to pay (or donate) could do this by having a bitcoin
client and having access to the Internet. Anyway this requires big
computational and memory resources. Further, it would be prohibitive
to send micropayments because of the fees built into the bitcoin
network.
There is a better alternative if the payment address of the sender and
the receiver are both accounts of Coinbase service. In this case
micropayments with low delay and no fees are possible. Furthermore the
client just need to use the API of that service and this can be done
with very low computing resources.

--Luca
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku

Ricardo Lanziano | 15 Feb 16:36 2014
Picon

Ntk clone on the works?

Hello all,

I found this the other day: http://www.openlibernet.org/paper/open-libernet.pdf
and it looked exactly like ntk + NTK PIP and just wanted to let people know
in this mailing list.

Best regards.

--

-- 
Ricardo Lanziano
To iterate is human, to recurse, divine.
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku

ACCEHN3ATOP | 26 Nov 19:59 2013
Picon

Re: good news


As far as I understand for applications Netsukuku looks like big LAN... 
So BitTorrent, BitTorrent Sync and other distributed protocols can 
transparently run over Netsukuku

26.11.2013 13:26, Francesco Cat пишет:
> This is EXTREMELY interesting.
>
> I lost track of development like long ago, so I'm asking a few questions
> that might be generally interesting for lots of people:
> -what can be run over netsukuku right now? Anything like IRC/any kind of
> messenger?
> -what is the status of "netsukuku over internet" for connecting far away
> nodes?
>
>
> 2013/11/25 Luca Dionisi <luca.dionisi <at> gmail.com>
>
>> [DISCLAIMER: only for devs or brave testers]
>>
>> - Now, having netsukuku installed in your router is really quick. You are
>>     just 13 copy/paste away!
>>
>> - ... WHAT !!?!?
>>
>> - Check it out for yourself:
>>     https://lab.dyne.org/Netsukuku_Dev/vala/flashing_notes4
>>
>>
>> _______________________________________________
>> Netsukuku mailing list
>> Netsukuku <at> lists.dyne.org
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
>>
>>
>
>
>
> _______________________________________________
> Netsukuku mailing list
> Netsukuku <at> lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
>
_______________________________________________
Netsukuku mailing list
Netsukuku <at> lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
Luca Dionisi | 25 Nov 23:36 2013
Picon

good news

[DISCLAIMER: only for devs or brave testers]

- Now, having netsukuku installed in your router is really quick. You are
   just 13 copy/paste away!

- ... WHAT !!?!?

- Check it out for yourself:
   https://lab.dyne.org/Netsukuku_Dev/vala/flashing_notes4

_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
Stefano Cudini | 14 Oct 20:26 2013
Picon

webRTC

hi!

I recently I am most looking about applications possible through the new WebRTC (http://webrtc.org), especially for p2p data exchange between browsers...

I wandered if anyone has ever thought of doing a javascript porting of netsukuku.
I think this would give the possibility to create a p2p network to exchange data in an anonymous browser level network.

What do you think?

thanks and regards
z4k
_______________________________________________
Netsukuku mailing list
Netsukuku@...
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku

Gmane