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

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

commit 69a7fa769bd6795fbceef691f7f197efb993540d Author: Marek Lindner mareklindner@neomailbox.ch Date: Mon Jul 27 19:10:45 2009 +0000

doc: batmand/AnnouncingNetworks

69a7fa769bd6795fbceef691f7f197efb993540d batmand/AnnouncingNetworks.textile | 76 +++++++++++++++++++++++++------------- 1 file changed, 51 insertions(+), 25 deletions(-)

diff --git a/batmand/AnnouncingNetworks.textile b/batmand/AnnouncingNetworks.textile index 7780641a..05cf09ed 100644 --- a/batmand/AnnouncingNetworks.textile +++ b/batmand/AnnouncingNetworks.textile @@ -1,36 +1,62 @@ -== Announcing networks ==

-Under certain circumstances it is desirable to make non-batman hosts (such as servers, [[BR]] -subnets, other routing domains or simple notebooks) known to the batman network. Batman [[BR]] -can announce these network addresses (also known as HNA) which tells every other batman [[BR]] -node to send the data for this network segment back to the announcing host (assuming [[BR]] +h2. Announcing networks + + +Under certain circumstances it is desirable to make non-batman hosts (such as servers, + +subnets, other routing domains or simple notebooks) known to the batman network. Batman + +can announce these network addresses (also known as HNA) which tells every other batman + +node to send the data for this network segment back to the announcing host (assuming + this host knows how to reach the destination).

-All following examples can also be applied as startup parameters. For the sake of simplicity [[BR]] -we assume there is a running batman daemon on the system that we can connect to.[[BR]] +All following examples can also be applied as startup parameters. For the sake of simplicity + +we assume there is a running batman daemon on the system that we can connect to. + + +Adding the announcement for e.g. the local network: + +batmand -c -a 192.168.1.0/24 + + +Adding multiple announcements in one go: + +batmand -c -a 192.168.1.0/24 -a 192.168.100.123/32 + + +Revoking an announcement: + +batmand -c -A 192.168.1.0/24 + + +Revoking multiple announcements in one go: + +batmand -c -A 192.168.1.0/24 -A 192.168.100.123/32 + + +It is worth noting that globally announced networks always give precendece to locally + +announced networks. + + ++Important+: The above examples explain how the batman nodes can find the path + +towards the non-batman network but you also have to ensure that the non-batman network + +knows the path back. This can be accomplished by setting the routes manually,

-Adding the announcement for e.g. the local network: [[BR]] -batmand -c -a 192.168.1.0/24 [[BR]] +masquerading, routing protocols, etc.

-Adding multiple announcements in one go: [[BR]] -batmand -c -a 192.168.1.0/24 -a 192.168.100.123/32 [[BR]]

-Revoking an announcement: [[BR]] -batmand -c -A 192.168.1.0/24 [[BR]] +Batman 0.3.2 (and later versions) allow multiple nodes to announce the same network

-Revoking multiple announcements in one go: [[BR]] -batmand -c -A 192.168.1.0/24 -A 192.168.100.123/32 [[BR]] +segment. You may have one non-batman network but several entry points to it. All border

-It is worth noting that globally announced networks always give precendece to locally [[BR]] -announced networks. [[BR]] +nodes can announce the same network. Receiving batman nodes choose their entry point

-__Important__: The above examples explain how the batman nodes can find the path [[BR]] -towards the non-batman network but you also have to ensure that the non-batman network[[BR]] -knows the path back. This can be accomplished by setting the routes manually, [[BR]] -masquerading, routing protocols, etc. [[BR]] +based on the best TQ value available.

-Batman 0.3.2 (and later versions) allow multiple nodes to announce the same network [[BR]] -segment. You may have one non-batman network but several entry points to it. All border[[BR]] -nodes can announce the same network. Receiving batman nodes choose their entry point [[BR]] -based on the best TQ value available. [[BR]]