public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Luca Pretto <luca.pretto@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Batman-adv and routed subnets
Date: Fri, 3 Aug 2012 11:40:43 +0200	[thread overview]
Message-ID: <B6EC8CB5-DDE0-4708-B89E-FADE58F33026@gmail.com> (raw)
In-Reply-To: <2670997.NDZah7qDiQ@bentobox>

Thanks for your answer Sven.

So, I've obviously misunderstood the part "mixing non-B.A.T.M.A.N. systems with batman-adv" [&]
I admit: the fact that batman-adv operates al L2 really confuses me a lot!
I'm a DIY nerd with no background training, so it's quite difficult to me.. But I won't give up! ;D

So, do you think that I should try to setup OSPF on every node, to keep the thing as-much-auto-scaling-as-possible?

But in that case I suspect I won't be able to use the "Gateway support" functions. Is it correct? [%]

Have a nice day,
Luca

[&] http://www.open-mesh.org/projects/batman-adv/wiki/Quick-start-guide
[%] http://www.open-mesh.org/projects/batman-adv/wiki/Gateways

Il giorno 03/ago/2012, alle ore 11:22, Sven Eckelmann ha scritto:

> First thing: batman-adv doesn't route (as in l3 routing). batman-adv creates a 
> distributed switch on l2 (so, batman-adv does path finding). Therefore, 
> batman-adv doesn't care about the l3 stuff.
> 
> And the stuff you've mentioned above is l3 stuff. So out of scope for batman-
> adv. Either you create static routes, use proxy arp or use another software 
> that distributes the l3 routes.
> 
> Kind regards,
> 	Sven


  reply	other threads:[~2012-08-03  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03  9:08 [B.A.T.M.A.N.] Batman-adv and routed subnets Luca Pretto
2012-08-03  9:22 ` Sven Eckelmann
2012-08-03  9:40   ` Luca Pretto [this message]
2012-08-03 10:01     ` Sven Eckelmann
2012-08-12 16:30     ` Simon Wunderlich

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=B6EC8CB5-DDE0-4708-B89E-FADE58F33026@gmail.com \
    --to=luca.pretto@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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