When a peer advertised several addresses, a node trying to create a tunnel to
it never tried any other address than the first one.

Before, we wrongly assumed OpenVPN would try all addresses before aborting
(--ping-exit). New code reexecutes OpenVPN until all addresses are tried
and update the peer db to reorder addresses if the first one failed.

The previous broadcast model is replaced by a query-response one.
During normal operation, the cache of peers is not used anymore to select
peers to connect to. It now only used for bootstrapping and avoid querying
an already known address.

using the same socket for sending and listenning

A peer now advertise itself more at the begining to be as present in the local db of other peers than the average

Currently, a peer broadcast its address to evrybody but this should change

solve a bug in an SQL request

    When the bootpeer was blacklisted, it was still inserted in the peers table
    When 0 tunnels had to be made, re6stnet asked for 0 unsed peers, recieved an empty list and thought he had to ask new peers to the server

remove some unecessary info when connecting to the server

A lot of bug fix

Removing of the bandwidth calculation

When 2 tunnels are estabilshed between the same 2 peers, one of them is deleted

Remove the refresh-rate option

Added new simulation results.

Added exception catching in db, and modified utils.log so tht it can be used with anything ( and not only a string )

Added some logs, added blacklist in db, added lan discovery through babel + automatic blacklisting of node routed through the LAN