OpenWrt Forum Archive

Topic: Routers for Mesh Type Network

The content of this topic has been archived on 3 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I was looking around for a router to use for a small mesh network (OLSR). It really does not have to be anything great, I am looking for something cheap since I am going to need multiple units.  It is just for sharing the internet between a few houses (relatives) that live around me.

I was looking into the Fonera as I can get 4 of them for "$110" or "$135†,depending on if I can get a discount, or if anyone knows another way to get them cheaper that would be great also. (maybe for $100 if i have 4 differant people order them)

I found some refurbished WRT54G V 1.1 units for $39....

Any other way to go about this or any issues you might see me facing with the fonera's?

Thanks

One thing you might want to be aware of is "BSSID partitioning".  Some chip/driver combinations are vulernable and others are not. Any one that is susceptible to partitioning is not suitable for a mesh node.

From the OLSR mailing list:

BSSID partitioning is something that happens at the MAC sublayer.  In
older designs, the MAC sublayer is implemented in firmware; in newer
(``softmac'') designs, the MAC sublayer is implemented in the driver.

In current Linux kernels, softmac designs use a common MAC implementation,
originally known as Devicescape and now renamed to mac80211.  Mac80211
does suffer from BSSID partitioning up to and including 2.6.26, but
this has been fixed in the current net-2.6 tree; hence, this issue
should be solved by 2.6.27 for all drivers using mac80211.  (But
I haven't tested it.)

After this short introduction, here's what I know about Linux drivers.

Atheros is a softmac design.  There are two drivers, the partly-binary
madwifi and the reverse-engineered ath5k.  Madwifi has its own MAC
implementation, and does not suffer from BSSID partitioning.  Older
versions of the Madwifi drivers had issues with ad-hoc mode, but
I believe that they have been solved by now.  (Can anyone confirm
that?)  Ath5k uses mac80211, see above.

Broadcom is a softmac design.  The binary-only ``wl'' driver has its
own MAC implementation, and does suffer from BSSID partitioning.  The
reverse-engineered ``b43'' driver uses mac80211, see above.

Intel has two distinct families of hardware designs which are handled
by the ipw2200 and iwlwifi drivers respectively.  The ipw2200 family
is a hardmac design, and I believe that it does not suffer from BSSID
partitioning (can anyone confirm that?).  The more recent iwlwifi
family is softmac and uses mac80211, see above.

Ralink is softmac, and uses mac80211, see above.  However, older
versions of the ralink driver did not support ad-hoc mode at all;
I haven't checked whether this has been fixed in recent releases.

The discussion might have continued from here.