Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit cecc11c270bb48a42cfe6f0efe2a172738a7ec33 Author: Marek Lindner mareklindner@neomailbox.ch Date: Wed Nov 12 13:10:28 2008 +0000

doc: batmand/RoutingVodoo

cecc11c270bb48a42cfe6f0efe2a172738a7ec33 batmand/RoutingVodoo.textile | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/batmand/RoutingVodoo.textile b/batmand/RoutingVodoo.textile index fe209cf1..843b82f8 100644 --- a/batmand/RoutingVodoo.textile +++ b/batmand/RoutingVodoo.textile @@ -67,13 +67,13 @@ The last rule is similar to the first rule but the kernel will jump to our "unre

'''What is the purpose of all this ?'''

- 1. Batman can clearly seperate hosts from announced networks. With a simple lookup you can see whether a node is announced or runs batman. - 2. It allows you and batman to easily delete all batman related table entries because the batman tables are well known and distinct. - 3. All batman activity is hidden in the background and does not mess with your manual configuration. You can still manipulate the default table without disturbing batman. - 4. It makes batman more interoperable with other routing protocols. This is very useful for testing scenarios where you want to test two (or more) routing protocols at the same time. - 5. With the unreachable rule we can make batman "faster". Whenever you want to access a node within your network which does not exist, your packets will end in the default route. You never will get an answer until your programm reaches a timeout. The unreachable rule changes this: If the packets destination is in your mesh network and no route exists, the kernel will immediately drop the packet and inform the programm which sent it. - 6. The policy routing "protects" your default route from other nodes. Batman will setup rules around the "tunnel" routing table which make sure that only non-batman interfaces and local traffic can end in the tunnel default route. You can choose your gateway as you like while this decission does not affect others in the network. - 7. The policy routing can be used for many more things, e.g. protecting against announced networks which have the same IP range as your internal network. Without policy routing it happens that you can't reach your internal network anymore because someone else announces the same IP range and your router sends the traffic there. However, this can't be done automatically by batman as the network configurations are too different. Firmware maintainers can tightly integrate batman into their distribution and add this feature. + * Batman can clearly seperate hosts from announced networks. With a simple lookup you can see whether a node is announced or runs batman. + * It allows you and batman to easily delete all batman related table entries because the batman tables are well known and distinct. + * All batman activity is hidden in the background and does not mess with your manual configuration. You can still manipulate the default table without disturbing batman. + * It makes batman more interoperable with other routing protocols. This is very useful for testing scenarios where you want to test two (or more) routing protocols at the same time. + * With the unreachable rule we can make batman "faster". Whenever you want to access a node within your network which does not exist, your packets will end in the default route. You never will get an answer until your programm reaches a timeout. The unreachable rule changes this: If the packets destination is in your mesh network and no route exists, the kernel will immediately drop the packet and inform the programm which sent it. + * The policy routing "protects" your default route from other nodes. Batman will setup rules around the "tunnel" routing table which make sure that only non-batman interfaces and local traffic can end in the tunnel default route. You can choose your gateway as you like while this decission does not affect others in the network. + * The policy routing can be used for many more things, e.g. protecting against announced networks which have the same IP range as your internal network. Without policy routing it happens that you can't reach your internal network anymore because someone else announces the same IP range and your router sends the traffic there. However, this can't be done automatically by batman as the network configurations are too different. Firmware maintainers can tightly integrate batman into their distribution and add this feature.

-If you want to influence batmans routing policy use the --policy-routing-script option to provide a custom executable. If this option is used batman will send it routing decissions to stdin of that executable instead of manipulation the routing table directly. Now, this executable can alter the rules and routing table entries by manipulating the routing by itself. You can see http://downloads.open-mesh.org/batman/useful-scripts-and-tools/policy_routin... to get a routing script sample. You wont need this option / script unless you want to do something fancy. \ No newline at end of file +If you want to influence batmans routing policy use the --policy-routing-script option to provide a custom executable. If this option is used batman will send it routing decissions to stdin of that executable instead of manipulation the routing table directly. Now, this executable can alter the rules and routing table entries by manipulating the routing by itself. You can see [http://downloads.open-mesh.org/batman/useful-scripts-and-tools/policy_routin... policy_routing_script.sh] to get a routing script sample. You wont need this option / script unless you want to do something fancy. \ No newline at end of file