All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.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: Thu, 12 Feb 2009 21:05:11 +0100	[thread overview]
Message-ID: <20090212200511.GA19551@pandem0nium> (raw)
In-Reply-To: <49945DAC.2010907@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2518 bytes --]

Hello Tim,

unfortunately i have no experience with WiMAX, but as far as i know:

 * WiMAX is not license-free like WiFi (means you need to BUY a license,
   at least in germany)
 * where is the technical advantage of WiMAX over WiFi? 
   Sure, the advertisements say "50 km or 108 MBit/s", but they don't say 
   "both at the same time". 
   You can reach this with WiFi as well (with the right antennas and setup).

So my question is: Where do you see the advantages in WiMAX over WiFi?

I don't know if there is some mesh technology available (as in
implemented) for WiMAX (as far as i know 802.16d?) or if there are 
adhoc-like modes available to let routing protocols like BATMAN work.

If you know more about WiMAX meshing i'd be very interested to hear. :)

best regards
	Simon


On Thu, Feb 12, 2009 at 11:34:36AM -0600, Tim LePes wrote:
> 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

> begin:vcard
> fn:Tim LePes
> n:LePes;Timothy
> adr;dom:;;2852 Lera Jones Drive;Antioch;Tennessee;37013
> email;internet:luvdownbabylon@gmail.com
> tel;home:(615) 361-4175
> tel;cell:(615) 594-3846
> x-mozilla-html:TRUE
> url:https://alembic.dyndns.org
> version:2.1
> end:vcard
> 




> _______________________________________________
> 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


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-02-12 20:05 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 [this message]
2009-02-12 20:26   ` Outback Dingo
2009-02-16  8:25 ` Tobias Gieseke
2009-02-16  8:48   ` Tobias Gieseke

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=20090212200511.GA19551@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.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 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.