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

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

commit 7a01b045afe313e5644a264588641453e51abb98 Author: Marek Lindner mareklindner@neomailbox.ch Date: Mon Jun 21 12:17:52 2010 +0000

doc: open-mesh/FAQ

7a01b045afe313e5644a264588641453e51abb98 open-mesh/FAQ.textile | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-)

diff --git a/open-mesh/FAQ.textile b/open-mesh/FAQ.textile index 16141474..f336ab92 100644 --- a/open-mesh/FAQ.textile +++ b/open-mesh/FAQ.textile @@ -1,4 +1,10 @@ -== If you are missing a question/answer (quite likely) please use the B.A.T.M.A.N. mailing list to trigger us. == + += FAQ = + +{{{ +#!div style="width: 46em; text-align: justify" + +If you are missing a question/answer (quite likely) please use the [wiki:MailingList B.A.T.M.A.N. mailing list] or [wiki:IRC IRC channel] to trigger us.

'''Does B.A.T.M.A.N. have simulator (NS2, Omnet++, etc) support?'''

@@ -46,15 +52,21 @@ A solution to that problem is the usage of the Linux kernel option "BINDTODEVICE

First, install netcat on your device. On a OpenWRT based distro you can try this (packet version may vary):

-$ ipkg install http://www.linuxops.net/ipkg/netcat_0.7.1_mipsel.ipk +{{{ +ipkg install http://www.linuxops.net/ipkg/netcat_0.7.1_mipsel.ipk +}}}

Then start batmand and pipe the output into netcat:

-$ batmand -d 4 <your_interfaces> | nc -l -p <any_unused_port> +{{{ +batmand -d 4 <your_interfaces> | nc -l -p <any_unused_port> +}}}

Finally start the netcat client on your logging server and save the output:

-$ nc <IP_of_your_device> <your_unused_port_from_step_2> > batman.log +{{{ +nc <IP_of_your_device> <your_unused_port_from_step_2> > batman.log +}}}

If you use a firewall, NAT or any other problematic network setup you can swap the netcat server position. Beware: Your netcat server has to be started before you start your netcat client.

@@ -75,3 +87,6 @@ Tip: Use key based access to authenticate your login request on your machines to

The batman daemon maintains a tunnel connection to every "batman internet client". Every packet that goes to the internet or comes back has to go through this tunnel. As it is a user space tunnel a lot of copying between user space and kernel land is necessary. Depending on the number of clients and the CPU power available this might be a bottleneck. The batgat kernel module tries to overcome this limitation. Once loaded the batman daemon will detect its presence automatically on startup. The daemon will activate the kernel module to let it handle the tunneling, hence avoiding the expensive copy operations. There is no difference between the daemon tunneling and the kernel tunneling other than that. + +}}} +