From: Tobias Gieseke <gieseke@irt.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.] WiMAX
Date: Mon, 16 Feb 2009 09:48:47 +0100 [thread overview]
Message-ID: <4999286F.30403@irt.de> (raw)
In-Reply-To: <49992315.4090106@irt.de>
Tobias Gieseke:
> Hi,
>
> we have some WiMax Cards but they are all PCMCIA. I may test them with
> Batman but I guess there will be serious driver problems in Linux. The
> cards where shipped with Windows drivers only and even those got some
> problems in the end. I agree with the others, that mesh in an WiMax
> system does not make sense (yet). WiMax is build for "infrastucture
> mode" the base station has the mayor task and is able to controll the
> clients in transmitting power, modulation etc. espacially in mobile
> Wimax (802.16e). The only case where mesh could come in is the
> communication between the Base stations, but that would be discrete
> links, so you don't really need a mesh. But I think you considerd this
> and you have an own concept for mesh in WiMax. Perhpas you could
> explain that to me (and the others)?
> I don't know anything about an adhoc mode for WiMax either.
>
> Kind regards,
>
> Tobi
Dang! Sorry Tim, I should have read your post "B.A.T.M.A.N Digest,
Vol26, Issue 7" before answering. Thanks for the detailed information
about your project. sounds interessting. Keep working on it ;-)
Regards,
Tobi
>
> Tim LePes:
>> Has anyone been playing with BATMAN on WiMAX hardware? I have a project
>> that I had to back burner for a while and I am getting ready to start
>> active work again. I am looking to see if I can find a mini PCI WiMAX
>> card that I can use in a Mesh AP, where WiMAX will be used for the
>> backbone and both WiFi and 10/100 Ethernet for clients to connect to the
>> AP. The idea is for drop-and-go network coverage in disaster areas or
>> other places where you want to get connectivity up in a hurry. I have a
>> dev board and am finally able to get some parts to help me work on it
>> again. Power supply, PCI to MiniPCI adapter, PoE hardware,
>> enclosure.. and of course a WiMAX card. I am also shopping for a
>> WiFi card too, so
>> recommendations there would be welcome. Though to be fair I haven't
>> been googling on that much yet, the WiMAX backhaul is my main concern at
>> the moment. Doing the WiFi AP part should be relatively easy as it is a
>> mature technology w/r/t parts and drivers availability. Any advice? So
>> far it seems that Intel has the greatest presence in my googling for
>> WiMAX on Linux.
>>
>>
>> Thanks so much!
>>
>> Tim LePes
>> _______________________________________________
>> B.A.T.M.A.N mailing list
>> B.A.T.M.A.N@open-mesh.net
>> https://lists.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://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
>
prev parent reply other threads:[~2009-02-16 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 17:34 [B.A.T.M.A.N.] WiMAX Tim LePes
2009-02-12 20:05 ` Simon Wunderlich
2009-02-12 20:26 ` Outback Dingo
2009-02-16 8:25 ` Tobias Gieseke
2009-02-16 8:48 ` Tobias Gieseke [this message]
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=4999286F.30403@irt.de \
--to=gieseke@irt.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