From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] batman-adv debian announcement
Date: Sun, 16 Nov 2008 17:48:31 +0100 [thread overview]
Message-ID: <20081116164831.GA21213@pandem0nium> (raw)
In-Reply-To: <5635aa0d0811160830r5521a8a4he0d5b22665664d7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]
Hey,
yep, bmxd/batman0.3 and batman-adv are both not compatible to each
other.
You should know that batman-adv does not have special gateway support
like the layer 3 batman versions. It can be considered as a big switch
where every node is one virtual hop away. You can therefore configure it
like your home LAN: install DHCP on your router, and that's it. If you
have multiple gateways, you might consider multiple DHCP servers, or
something else ... depending on your scenario. :)
regards,
Simon
On Sun, Nov 16, 2008 at 11:30:06PM +0700, Outback Dingo wrote:
> ok lastly, it seems possible its very similiar config to bmxd which is what
> has been running, though layer 3, im trying to get layer 2 kernel routing
> going
> originally i used batgat but yet it was problematic, so its safe to say i
> could go batman-adv and drop bmxd? as i belive one is not compatible with
> the
> other in the mesh
>
> On Sun, Nov 16, 2008 at 11:26 PM, Marek Lindner <lindner_marek@yahoo.de>wrote:
>
> > On Monday 17 November 2008 00:06:37 Outback Dingo wrote:
> > > any good docs on configuring batman-adv for atheros ?
> >
> > We are writing it but it takes time. :-)
> >
> >
> > Here the short intro:
> >
> > Batman advanced is not aware of the Atheros driver. On every hardware it
> > runs
> > in the same way.
> >
> > Load the module -> modprobe batman-adv-core
> >
> > In /proc/net/batman-adv/ you will find the files to tweak batman. E.g. give
> > it a
> > device to operate on -> echo eth0 > /proc/net/batman-adv/interface
> >
> > deactivate batman-adv -> echo "" > /proc/net/batman-adv/interface
> >
> > The other files in that folder should be self explanatory. If not come back
> > and
> > ask us.
> >
> > Regards,
> > Marek
> >
> > _______________________________________________
> > B.A.T.M.A.N mailing list
> > B.A.T.M.A.N@open-mesh.net
> > https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
> >
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-11-16 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 16:04 [B.A.T.M.A.N.] batman-adv debian announcement Marek Lindner
2008-11-16 16:06 ` Outback Dingo
2008-11-16 16:26 ` Marek Lindner
2008-11-16 16:30 ` Outback Dingo
2008-11-16 16:48 ` Simon Wunderlich [this message]
2008-11-16 17:11 ` Marek Lindner
2008-11-16 17:22 ` Outback Dingo
2008-11-16 17:37 ` Marek Lindner
2008-11-16 20:21 ` Outback Dingo
2008-11-17 2:08 ` Marek Lindner
2008-11-16 16:27 ` Simon Wunderlich
2008-11-16 16:32 ` Outback Dingo
2008-11-16 16:48 ` Marek Lindner
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=20081116164831.GA21213@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.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