Hey,

we also have precompiled binaries for x86: http://downloads.open-mesh.net/batman/stable/binaries/i386/ http://downloads.open-mesh.net/batman/development/binaries/i386/

another option is to compile/linu batmand with the -static flag on your x86 (i386) desktop and just copy it, as Sven explained. Unfortunately you won't get an ipkg package with this, but it should run. ;)

best regards Simon

On Wed, Jan 21, 2009 at 02:36:03PM +0100, Sven Eckelmann wrote:

Hi, On Wednesday 21 January 2009 13:54:44 Kartik Muralidharan wrote:

...

I have a couple of embedded devices (x86) running the latest version of OpenWRT. I would like to know if I could compile and run batman on these nodes and if so how.

There is a howto written by Wesley at http://downloads.open-mesh.net/batman/misc/batmand_howto.pdf

This should describe the process of building and the first steps quite good. You can compile the batmand binary by using a gcc with i386 as target plattform. This should be the case for every standard gcc on non-amd64 i368 distributions. Afterwards you can copy it to your embedded device and use it. I am not up to date with the current development in trunk of openwrt but I think they don't provide packages for gcc yet. So it will not be possible (unless you installed gcc by hand) to compile it on your device running openwrt. This is the really quick and dirty method but you can also create ipkgs with the standard openwrt build environment with the build scripts from https://svn.openwrt.org/openwrt/packages/net/batman/

I would recommend that you use a current snapshot of the batman sources from trunk because they contain a bunch of fixes since the last release (0.3). You can obtain them by running svn export http://downloads.open-mesh.net/svn/batman/trunk/batman/

Best regards, Sven

Hi,

Is what Philip is compiling batman/robin on the x86 of any interest currently currently known as "Robix" This is fully documented I believe http://robin.forumup.it/viewforum.php?f=12&mforum=robin

Regards,

Ian

-----Original Message----- From: b.a.t.m.a.n-bounces@open-mesh.net [mailto:b.a.t.m.a.n-bounces@open-mesh.net] On Behalf Of Sven Eckelmann Sent: 21 January 2009 13:36 To: b.a.t.m.a.n@open-mesh.net Subject: Re: [B.A.T.M.A.N.] Install Batman

Hi, On Wednesday 21 January 2009 13:54:44 Kartik Muralidharan wrote:

I have a couple of embedded devices (x86) running the latest version of OpenWRT. I would like to know if I could compile and run batman on these nodes and if so how.

There is a howto written by Wesley at http://downloads.open-mesh.net/batman/misc/batmand_howto.pdf

This should describe the process of building and the first steps quite good.

You can compile the batmand binary by using a gcc with i386 as target plattform. This should be the case for every standard gcc on non-amd64 i368 distributions. Afterwards you can copy it to your embedded device and use it. I am not up to date with the current development in trunk of openwrt but I think they don't provide packages for gcc yet. So it will not be possible (unless you installed gcc by hand) to compile it on your device running openwrt. This is the really quick and dirty method but you can also create ipkgs with

the standard openwrt build environment with the build scripts from https://svn.openwrt.org/openwrt/packages/net/batman/

I would recommend that you use a current snapshot of the batman sources from

trunk because they contain a bunch of fixes since the last release (0.3). You can obtain them by running svn export http://downloads.open-mesh.net/svn/batman/trunk/batman/

Best regards, Sven

Thanks Sven/Simon.

I was able to compile and checking 'file batmand' gave me the output mentioned below.

But running ./batmand ath0 gives me an error.

What configuration do I need to do on the wireless interface on the device?

Thanks Kartik

-----Original Message----- From: Sven Eckelmann [mailto:sven.eckelmann@gmx.de] Sent: Wednesday, January 21, 2009 11:21 PM To: b.a.t.m.a.n@open-mesh.net Cc: Simon Wunderlich; Kartik Muralidharan Subject: Re: [B.A.T.M.A.N.] Install Batman

Hi On Wednesday 21 January 2009 15:38:14 Simon Wunderlich wrote:

another option is to compile/linu batmand with the -static flag on

your

x86 (i386) desktop

Thx, forgot that one. You should be able to link it statically by using the current version from trunk and running LDFLAGS="-s -static" /usr/bin/make

You can check it with `file batmand`. It should print something like batmand: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.6.8, stripped

best regards, Sven

On Friday 23 January 2009 10:30:26 Kartik Muralidharan wrote:

I was able to compile and checking 'file batmand' gave me the output mentioned below.

But running ./batmand ath0 gives me an error.

What error? Is it a dynamic linker error? Does `./batmand` gives the same error? Does `dmesg|tail` gives more information about that problem?

What configuration do I need to do on the wireless interface on the device?

Their are many configurations possible, but I will try to explain a common one: - Get the device in adhoc mode (for example create a vap in adhoc mode with madwifis wlanconfig) - set the essid - set the cellid - set the channel/frequency - start the device - set a unique ip to the device

$ wlanconfig ath0 create wlandev wifi0 wlanmode adhoc $ iwconfig ath0 essid testnet $ iwconfig ath0 ap 02:00:de:ad:be:ef $ iwconfig ath0 channel 10 $ ifconfig ath0 $IP $ ip a add $IP brd $BRDCAST dev ath0 $ ip link set ath0 up

I hope that I didn't forgot anything.

Regards, Sven