From: Panayot Daskalov <panayot.daskalov@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Connecting non-batman nodes to a mesh network
Date: Sun, 20 Nov 2011 23:51:41 +0200 [thread overview]
Message-ID: <4EC9766D.9000302@gmail.com> (raw)
In-Reply-To: <20111120211558.GA11262@autistici.org>
Hi Antonio,
thanks for the prompt reply!
The devices have either RTL8188SU or RTL8188CUS chipsets from Realtek.
Drivers can be found here -
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8188SU
<http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8188SU>
May be they are mac80211 compatible, but I am not sure. Can you give me
an example of creating a virtual interface so I can try?
Thanks.
Best regards,
Panayot
On 11/20/2011 11:16 PM, Antonio Quartulli wrote:
> On dom, nov 20, 2011 at 10:49:16 +0200, Panayot Daskalov wrote:
>>> Hi All,
>>>
>>> I want to ask for your advice about a batman problem I am facing. I have
>>> a mesh network of custom build embedded Linux devices. The devices have
>>> only network one interface and this is the Wi-Fi that is used by batman.
>>> So far the mesh is running OK, but at some point I need to be able to
>>> connect with a laptop (non-Linux) to the network and access some of the
>>> devices via its IP address. I tried simply connecting to the adhoc
>>> network and setting a static IP to my laptop. I have managed to do that,
>>> but I can't access the nodes from the mesh.
>>>
>>> I read the instruction for mixing with non-batman devices by bridging
>>> the bat0 interface with the "non-batman" interface, but as far as I
>>> understand that applies to systems with at least 2 network interfaces
>>> e.g one for batman nodes and one for the non-batman. So my question is -
>>> can I mix non-batman and batman nodes when I have only one network
>>> interface on the batman nodes? If yes, then how?
> Hi Panayot,
>
> you are right: you need two "interfaces" in order to let clients connect
> to the mesh. However (if you want to use wifi interfaces only) you can
> also create "virtual interaces" using the same "real interface". This
> feature is available depending on the wifi driver you are using. If you are
> using madwifi or one of the new mac80211 drivers (not all support it),
> this technique should be feasiable without introducing many problems :)
>
> For instance, what driver are you using?
>
> Cheers,
>
next prev parent reply other threads:[~2011-11-20 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 20:49 [B.A.T.M.A.N.] Connecting non-batman nodes to a mesh network Panayot Daskalov
[not found] ` <20111120210326.GA3080@ritirata.org>
2011-11-20 21:16 ` Antonio Quartulli
2011-11-20 21:51 ` Panayot Daskalov [this message]
2011-11-21 7:02 ` Marek Lindner
2011-11-24 9:47 ` Panayot Daskalov
2011-11-24 11:53 ` Marek Lindner
2011-11-24 12:25 ` Panayot Daskalov
2011-11-24 13:02 ` 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=4EC9766D.9000302@gmail.com \
--to=panayot.daskalov@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