From: Mitar <mmitar@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Mitar <mitar@tnode.com>
Subject: Re: [B.A.T.M.A.N.] Migration to Batman
Date: Thu, 12 Apr 2012 19:19:32 +0200 [thread overview]
Message-ID: <CAKLmikM+jShmbtBq8X9ygAMACpX6tHBwC+HNmzhSc-8HJzMEGw@mail.gmail.com> (raw)
In-Reply-To: <4F86F6BF.60406@jst.sm>
Hi!
On Thu, Apr 12, 2012 at 5:37 PM, Jernej Kos <k@jst.sm> wrote:
> Wouldn't just need something like an announce mechanism so each node
> would add an L3 route to the gateway announcing the said prefix?
One way could be arp proxy. So that border node would pretend to hold
all IPs of subnet behind it and reply with its own MAC address for all
those IPs. Once packets gets there is then routed behind. I have been
playing with this once and it does work.
https://en.wikipedia.org/wiki/Proxy_ARP
> Since from layer 3, the batman mesh looks just like a big LAN, any node
> could simply add a route saying "prefix A via gateway B dev bat0" where
> B is a mesh node known to batman via its L2 identifier, no?
So we would just need some other L3 routing protocol on top of
batman-adv, without any need of knowing the wireless infrastructure,
only to configure dynamically those announcements on all nodes, no? So
that when gateway B appears, that all nodes add its prefix A to their
L3 routing tables?
Mitar
next prev parent reply other threads:[~2012-04-12 17:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 10:26 [B.A.T.M.A.N.] Migration to Batman Mitar
2012-04-12 10:36 ` Gioacchino Mazzurco
2012-04-12 12:00 ` Antonio Quartulli
2012-04-12 15:13 ` Mitar
2012-04-12 15:36 ` Andrew Lunn
2012-04-12 17:12 ` Mitar
2012-04-12 18:12 ` Andrew Lunn
2012-04-12 19:49 ` 3zl Trizonelabs
[not found] ` <CAOaDhSRTgejL5tzAnAx6wBso1sjWn_7bVuT6P1_C1qcVu25McQ@mail.gmail.com>
2012-04-12 15:37 ` Jernej Kos
2012-04-12 17:19 ` Mitar [this message]
2012-04-12 21:08 ` Mitar
2012-04-12 21:15 ` Gioacchino Mazzurco
2012-04-13 5:59 ` Andrew Lunn
2012-04-13 7:58 ` Mitar
2012-04-13 8:15 ` Andrew Lunn
2012-04-13 8:41 ` Mitar
2012-04-13 9:24 ` Andrew Lunn
2012-04-13 13:24 ` Mitar
2012-04-14 2:26 ` Nicolás Echániz
2012-04-14 9:06 ` Mitar
2012-04-16 10:25 ` Mitar
2012-04-16 10:37 ` Marek Lindner
2012-04-16 10:46 ` Mitar
2012-04-16 10:58 ` Marek Lindner
2012-04-16 12:32 ` Mitar
2012-04-16 12:40 ` Antonio Quartulli
2012-04-16 13:59 ` Mitar
2012-04-16 18:28 ` Marek Lindner
2012-04-16 18:30 ` Marek Lindner
2012-04-16 11:03 ` Antonio Quartulli
2012-04-16 12:37 ` Mitar
2012-04-12 17:10 ` Mitar
2012-04-12 22:13 ` Marek Lindner
2012-04-12 17:05 ` Mitar
2012-04-12 22:17 ` Marek Lindner
2012-04-13 6:22 ` Antonio Quartulli
2012-04-13 7:29 ` Mitar
2012-04-13 7:43 ` Andrew Lunn
2012-04-13 7:51 ` Mitar
2012-04-13 8:26 ` Andrew Lunn
2012-04-13 8:35 ` Mitar
2012-04-13 8:52 ` Christian Huldt
2012-04-13 13:32 ` Mitar
2012-04-13 13:50 ` Andrew Lunn
2012-04-13 13:53 ` Mitar
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=CAKLmikM+jShmbtBq8X9ygAMACpX6tHBwC+HNmzhSc-8HJzMEGw@mail.gmail.com \
--to=mmitar@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mitar@tnode.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.