Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
R
re6stnet
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
zhifan huang
re6stnet
Commits
6b0076d2
Commit
6b0076d2
authored
Jul 24, 2012
by
Ulysse Beaugnon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
TODO update
parent
849e2929
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
13 deletions
+14
-13
TODO
TODO
+14
-13
No files found.
TODO
View file @
6b0076d2
To be done
:
Bugs
:
The address of the client is declared while it should only be the address
The address of the client is declared while it should only be the address
of the server
of the server
Upgrade the logging function in order to be able to log message like
To be done :
"Refreshing peers DB ... done", or add log messages to specify that an
action advertised by a previous log message has been completed
use the server as a bootstrap node -> switch peer discovery to be done
use the server as a bootstrap node -> switch peer discovery to be done
by vifibnet directly ?
by vifibnet directly ?
Use an algorithm to choose which connections to keep and/or establish
Use an algorithm to choose which connections to keep and/or establish
instead of pure randomness
instead of pure randomness
|-> number of routes / tunnel
number of routes / tunnel
|-> favorise most used roads ?
favorise most used roads
Handle LAN internally in order not to have catastrophic results ....
the first thing to do is to include the LAN iface on the intarfaces
given to babel => pb : someone who has a lan acces to our network can
provide false informations. Needs of signature
If it is not sufficient, we could use avahi (dm-dns for linux)
Replace comments at the beginning of functions with docstrings & give all
Replace comments at the beginning of functions with docstrings & give all
fn docstrings
fn docstrings
Use a timeout for the server peersDB so we can flag unreachable peers and
Upgrade the logging function in order to be able to log message like
remove the peers whose certificate is no longer valid
"Refreshing peers DB ... done", or add log messages to specify that an
action advertised by a previous log message has been completed
Handle LAN internally in order not to have catastrophic results ....
( avahi could be used )
To be discussed:
To be discussed:
U : Babel seems to be very long to establish the routes : maybe we should
U : Babel seems to be very long to establish the routes : maybe we should
...
@@ -47,7 +48,7 @@ To be discussed:
...
@@ -47,7 +48,7 @@ To be discussed:
Btw, is there a doc ( pdf, image, file ) resuming Raphael's stats
Btw, is there a doc ( pdf, image, file ) resuming Raphael's stats
on nexedi's server downtime ? it could be useful for the internship
on nexedi's server downtime ? it could be useful for the internship
rapport
rapport
==>
It takes babel between 3 times and 4 times the hello interval to
G :
It takes babel between 3 times and 4 times the hello interval to
reestablish connection, if a direct link is cut
reestablish connection, if a direct link is cut
U : So we have to reduce the hello interval. 2min to detect a dead link is
U : So we have to reduce the hello interval. 2min to detect a dead link is
far too much.
far too much.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment