public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Mesh with access from wifi and lan. Which is the Only True Way?
Date: Wed, 29 Sep 2010 23:40:40 +0200	[thread overview]
Message-ID: <201009292340.41693.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4CA3A534.30102@magwas.rulez.org>

On Wednesday 29 September 2010 22:44:36 Magosányi Árpád wrote:
> I am using OpenWrt Backfire.

Ok.


> One sign that I am using nonstandard setting is that a non-batman node
> will end up in a throw route of the batman nodes. But if it should work
> without firewall, then I will be happy with my current setup.

A throw route is no problem by itself. It only means that the Linux kernel 
will leave the current table to check the next one for a suitable routing 
entry. 

If you are interested in understanding the routing techniques used by batman:
http://www.open-mesh.org/wiki/RoutingVodoo


> What I am seeing is that traffic from local wifi net does not "go down" to the
> tunnels, but goes through the batman nodes untunneled. Maybe I have to set
> up some routes from the local wifi net? For your reference here is the
> network setup again (N is the node number, ip of the node/netmask len):
> backbone batman network: 10.42.0.N/24 (for batman nodes)
> local wifi net: 10.42.N.1/24 (for non-batman users, dhcp served from the
> node in force mode)
> local lan: 10.43.N.1/24 (for wired users, DHCP served from the node)

Does each node announce the "local wifi net" via HNA ? You will need these 
announcements to make the routing towards this addresses work. As soon as 
batmand knows that it is responsible for a certain IP address space it will 
add the appropriate routing entries for you.
Again, we have a document describing the process:
http://www.open-mesh.org/wiki/AnnouncingNetworks


> Páty, Hungary. We are experimenting with participatory democracy, and
> this is one of the side effects:)

Cool! Good luck with your experiments. :-)

Regards,
Marek


  reply	other threads:[~2010-09-29 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 19:08 [B.A.T.M.A.N.] Mesh with access from wifi and lan. Which is the Only True Way? Magosányi Árpád
2010-09-29 10:28 ` Marek Lindner
2010-09-29 19:41   ` Magosányi Árpád
2010-09-29 20:20     ` Marek Lindner
2010-09-29 20:44       ` Magosányi Árpád
2010-09-29 21:40         ` Marek Lindner [this message]
2010-09-30 11:50           ` Magosányi Árpád
2010-09-30 14:15             ` 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=201009292340.41693.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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