equal
deleted
inserted
replaced
|
1 <html> |
|
2 <head> |
|
3 <title> DTN2 Manual: Flood Router </title> |
|
4 <link rel="stylesheet" type="text/css" href="manual.css" /> |
|
5 </head> |
|
6 <body> |
|
7 <h1>Flood Router |
|
8 </h1> |
|
9 |
|
10 <p> |
|
11 This is the implementation of a flooding based bundle router. |
|
12 |
|
13 <p> |
|
14 In the implementation an internal BundleList is maintaned in which |
|
15 all bundles are kept until their expiration time. This prevents |
|
16 the main daemon logic from opportunistically deleting bundles when |
|
17 they've been transmitted. |
|
18 |
|
19 <p> |
|
20 Whenever a new link arrives, we add a wildcard route to the table. |
|
21 Then when a bundle arrives, we can stick it on the all_bundles list |
|
22 and just call the base class route_bundle function. The core base |
|
23 class logic then makes sure that a copy of the bundle is forwarded |
|
24 exactly once to each neighbor.For more information please see the |
|
25 <a href="configuration.html#route">route</a> command. |
|
26 |
|
27 <p> |
|
28 Note: At present this will forward a bundle back to the node from |
|
29 which it arrived. |
|
30 |
|
31 |
|
32 <p> |
|
33 </body> |
|
34 </html> |
|
35 |