public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: elektra <onelektra@gmx.net>
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.] Who can help with BATMAN-ADV integration into ROBIN-FW?
Date: Wed, 23 Apr 2008 03:19:35 +0200	[thread overview]
Message-ID: <480E8EA7.2040804@gmx.net> (raw)
In-Reply-To: <bccbc6690804221407r662b4f03r313170fcf742d52f@mail.gmail.com>

Hi -

I can't recommend using a variety of different wireless hardware with 
different chipsets, drivers, firmware in a network - yet. And I don't 
know any USB stick that I would recommend. If someone reading this list 
has a working recommendation still available for purchase, please add a 
comment.

What we usually do is: Get a router supported by Freifunk/OpenWRT with 
Broadcom/Atheros SoC inside, reflash it with Freifunk Firmware and 
connect it to your notebook. Or: If you have Atheros in your notebook or 
PC  with a self compiled recent Madwifi, fine. Otherwise replace the 
build-in card with something Atheros-based (you may have to modify your 
notebooks BIOS if you use IBM/Lenovo/HP, in order that the machine 
accepts the card), or insert a additional cardbus/express card with 
Atheros chipset, given that you still have a cardbus/express interface 
in your notebook. The Madwifi driver shipped with your favorite Linux 
distro may not work properly, so get it from madwifi.org and compile it 
against the Linux kernel that you are running.

With Atheros you can fix the IBSSID in order to overcome those notorious 
issues with cell-splitting, I also managed to perform this with IPW3945. 
Also OpenWRT/Freifunk does allow this with Broadcom hardware, too.

The command on a Linux-PC  to fix the IBSSID is:

iwconfig <interface> ap <your preferred cell-id like 02:CA:FF:EE:BA:BE>

Note that this is non-standard behavior, and is unlikely to work with 
other cards. Actually upon request from Freifunk this was modified in 
the Madwifi driver.

Old Cisco Aironet 802.11b works for me (mostly) as long as the mesh is 
the only ad-hoc network around... I use it every day, it is running 
stable until I stop it. Also ancient Atmel 76c503 based USB sticks work 
- I used to build mesh routers with them in the old days ;-) Old Prism2, 
2.5, 3 and Prism54 (Hard-Mac only) work, but are susceptible to 
cell-splitting (and may lock up if cell-splitting is already going on in 
your WiFi cell).

I have a Intel IPW3945 in a new notebook that works somehow with a 
little trick under Ubuntu (fix the Cell-ID in managed mode first, switch 
to ad-hoc, set essid, set channel, enable interface) -  but from time to 
time I get hiccups that seem to be associated with firmware errors 
(reported in syslog) - then I need to reset the interface). The 
experience with IPW2200 was even worse with a notebook I used a year 
ago, but I didn't try that recently.

Broadcom would be an option, but the company doesn't provide drivers for 
Linux-PCs. There is an open-source driver but I don't know whether it 
actually works in ad-hoc mode now.

cu elektra



> thanks, elektra, would it be possible, that an usb stick with wifi 
> chip and coded in software can be distributed? e.g. by foebud?
> we need a solution, where people use their laptop and not need to 
> configure their routers.
> The Laptop or USB-Stick has the wifi chip...
> is there a wiki, where all wifi chips are listed and how the bug 
> fixing for them is going on by whoom?
>  
> Maxx
> ------------------------------------------------------------------------
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>   


  reply	other threads:[~2008-04-23  1:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02  9:18 [B.A.T.M.A.N.] Node with two wireless interfaces - to bridge them or not? Predrag Balorda
2008-04-03 13:34 ` Simon Wunderlich
2008-04-03 14:58   ` Predrag Balorda
2008-04-04 10:47     ` elektra
2008-04-05 20:26       ` [B.A.T.M.A.N.] Who can help with BATMAN-ADV integration into ROBIN-FW? Solon Lutz
2008-04-06 16:21         ` elektra
2008-04-06 16:39         ` Marek Lindner
2008-04-10 15:37           ` Solon Lutz
2008-04-18  4:57             ` Marek Lindner
2008-04-18 10:39               ` Re[2]: " Solon Lutz
2008-04-18 11:53                 ` elektra
2008-04-18 11:58                   ` elektra
2008-04-22  5:13                 ` Simon Wunderlich
2008-04-30 17:20                   ` Re[2]: " Solon Lutz
2008-05-01 18:27                     ` Alexander Morlang
2008-05-02  7:40                       ` Solon Lutz
2008-04-22 16:24         ` M. Peterson
2008-04-22 19:00           ` elektra
     [not found]             ` <2520215E-4451-43DD-B86C-BE1AA134933B@philippeapril.com>
2008-04-22 20:42               ` elektra
2008-04-22 20:57                 ` dondavis
2008-04-22 21:07                   ` M. Peterson
2008-04-23  1:19                     ` elektra [this message]
     [not found]               ` <480E421E.3030407@gmx.net>
     [not found]                 ` <FF6CA3D4-0705-458F-8FD4-80D4CDA3A165@philippeapril.com>
2008-04-22 20:42                   ` elektra
2008-04-23 16:45             ` Alexander Morlang

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=480E8EA7.2040804@gmx.net \
    --to=onelektra@gmx.net \
    --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