From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] Help in batman advanced configuration
Date: Sat, 24 Jan 2009 09:42:07 +0100 [thread overview]
Message-ID: <200901240942.07893.lindner_marek@yahoo.de> (raw)
In-Reply-To: <238a15490901231630s7d460687x6a95238f7308998a@mail.gmail.com>
Hi,
> OPENMESH 2 - configuration
> ==========================
>
> 1. I stop the routing daemons. It has ath0, ath1, ath2 interfaces.
> I again bridge these interfaces (br0 - ath0, ath1, ath2
>
> I try getting an IP for this node usign the same method of running
> udhcpc but i am unable to
> So I dont have an IP - but i dont worry about it now.
You wont get an IP address on distant hosts (more than 1 hop) unless you have
batman running. The adhoc network will not relay your message.
B.A.T.M.A.N. advanced is a kind of bridging tool on its own. You should load
the module and add the batman interfaces (in your case ath0). After configuring
batman you will have a new interface called "bat0" which you can add to your
bridge setup (br0 - ath1, ath2, bat0). Run udhcp on top of br0 now.
> Associate a client
> ==================
>
> I now try to associate a client to open mesh 2. Its IP request gets
> forwarded to the wired network and it receives an IP
> (192.168.50.6)
>
> However i can't batping to it from either openmesh 2 or openmesh 1
> Is something missing in my configuration?
You can't run the battools (e.g. batping) from a client that does not run
batman advanced. The battools connect to the running batman to inject their
ping requests. Batman will recognize these special packets and treat them
accordingly.
Regards,
Marek
next prev parent reply other threads:[~2009-01-24 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 0:30 [B.A.T.M.A.N.] Help in batman advanced configuration Gargi Purohit
2009-01-24 8:42 ` Marek Lindner [this message]
2009-01-26 17:34 ` Gargi Purohit
2009-01-26 19:41 ` Marek Lindner
2009-01-26 20:28 ` Gargi Purohit
2009-01-26 21:24 ` Simon Wunderlich
2009-01-27 1:41 ` Gargi Purohit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200901240942.07893.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox