Topic: Recommendations for Multi SSID (AP+Adhoc) routers needed

Hi,

I´m searching for low cost routers that can do one AP and one Adhoc mode at the same time. And I need to run kernel >2.6.24 for B.A.T.M.A.N advanced kernel module on these devices. Until now I tested the Fonera an the D-Link Dir300 and on these devices it works.

Which other devices can you recommend me?

Regards
Floh1111

2 (edited by Orca 2011-02-20 11:38:03)

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

Doesn't the wiki help you?

There is a link (somewhere) to this:
http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers

I don't know if this is true, you can update. if you want to. You can also generate some own content.

This should be more reliable, but not necessarily up-to-date:  http://wireless.kernel.org/ You have to search a bit. They do lack a nice overview like the wikipedia has.

As for Kernel, I think everything but br 2.4 uses 2.6.32 and newer.

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

Thank you, this links where already helpfull to find some information about the status of the drivers. But I can´t find whether special devices can do ap and adhoc mode at the same time. It is only listed whether they can do adhoc or ap mode but not especially adhoc and ap at the same time (some kind of multi ssid).

So maybe has already tested a setup like this in reallife and experienced good results with some routers and can share his expecience with me?

Regards
Floh1111

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

Look at here for yourself. I think TP-LINK TL-WR741N/D is the cheapest one with 1T1R while TL-WR841N/D is capable of 2T2R.

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

Sorry that I need to ask but what does 1T1R and 2T2R mean?

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

IEEE 802.11n-2009 - Wikipedia, the free encyclopedia

7 (edited by sroppon 2011-04-16 20:47:43)

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

Thank you all for trying to help, but no one seems to understand what the question is about. None of those links have any information about running multi-SSID with ad-hoc and AP.

The point is that you can run mesh network with B.A.T.M.A.N or similar protocol in ad-hoc mode, but regular computer, phone etc. clients cannot connect to the mesh network as they understand nothing about the protocol. So you need a regular access point for them. With some chipsets it could be possible to run both with the same hardware simultaneously. That would be easier and less costly than using a second wireless AP or USB stick for regular clients.

Today I installed OpenWrt on a TP-Link TL-WR741ND rev. 1.9 and it's NOT POSSIBLE. It didn't even configure right and this is what I got in dmesg:

ath: Cannot create ADHOC interface when other interfaces already exist.
ath: Cannot create ADHOC interface when other interfaces already exist.
ath: Cannot create ADHOC interface when other interfaces already exist.
ath: Cannot create ADHOC interface when other interfaces already exist.

-sami

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

sroppon wrote:

Thank you all for trying to help, but no one seems to understand what the question is about. None of those links have any information about running multi-SSID with ad-hoc and AP.

OpenWrt manual

Limitations: There are certain limitations when combining modes. Only the following mode combinations are supported:

    * Broadcom:
          o 1x sta, 0-3x ap
          o 1-4x ap
          o 1x adhoc
          o 1x monitor

      WDS links can only be used in pure AP mode and cannot use WEP (except when sharing the settings with the master interface, which is done automatically).
    * Atheros:
          o 1x sta, 0-Nx ap
          o 1-Nx ap
          o 1x adhoc

      N is the maximum number of VAPs that the module allows, it defaults to 4, but can be changed by loading the module with the maxvaps=N parameter.

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

fyi wrote:

* Atheros:
          o 1x sta, 0-Nx ap
          o 1-Nx ap
          o 1x adhoc

Yeah, looking documentation this seems to be some kind of generic assumption. But Atheros AR2315 actually works right with 1 AP + 1 ad-hoc.

The mesh cell with OpenWrt and multi-SSID:

root@made:~# cat /proc/cpuinfo 
system type        : Atheros AR2315
----8<----

root@made:~# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

br-lan    no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:"batman-ap"  
          Mode:Master  Frequency:2.412 GHz  Access Point: 00:18:84:13:A8:09   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=36/70  Signal level=-60 dBm  Noise level=-96 dBm
          Rx invalid nwid:670172  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ath1      IEEE 802.11g  ESSID:"Vaasankatu B.A.T.M.A.N L2-12"  
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 02:C0:FF:EE:CA:11   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=36/70  Signal level=-60 dBm  Noise level=-96 dBm
          Rx invalid nwid:8044  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

bat0      no wireless extensions.

root@made:~# batctl if
ath1: active

root@made:~# brctl show
bridge name    bridge id        STP enabled    interfaces
br-lan        8000.00188413a808    no        eth0
                            bat0
                            ath0

root@made:~# ifconfig br-lan
br-lan    Link encap:Ethernet  HWaddr 00:18:84:13:A8:08  
          inet addr:10.0.64.11  Bcast:10.0.127.255  Mask:255.255.192.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24881 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2705 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2045098 (1.9 MiB)  TX bytes:301843 (294.7 KiB)

The gateway with Debian:

katiska:/etc/awstats# iwconfig wlan0
wlan0     IEEE 802.11bgn  ESSID:"Vaasankatu B.A.T.M.A.N L2-12"  
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 02:C0:FF:EE:CA:11   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          
katiska:/etc/awstats# ifconfig bat0
bat0      Link encap:Ethernet  HWaddr 92:8a:be:d6:80:a3  
          inet addr:10.0.64.1  Bcast:10.0.127.255  Mask:255.255.192.0
          inet6 addr: fe80::908a:beff:fed6:80a3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2048796 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3137178 errors:0 dropped:158 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:282185428 (269.1 MiB)  TX bytes:4194987497 (3.9 GiB)

A client computer with Ubuntu:

root@atom:~# iwconfig wlan0
wlan0     IEEE 802.11bg  ESSID:"batman-ap"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:18:84:13:A8:09   
          Bit Rate=48 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=46/70  Signal level=-64 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:20  Invalid misc:450   Missed beacon:0

root@atom:~# ping -f 10.0.64.1
PING 10.0.64.1 (10.0.64.1) 56(84) bytes of data.
..........^C    
--- 10.0.64.1 ping statistics ---
274 packets transmitted, 264 received, 3% packet loss, time 2519ms
rtt min/avg/max/mdev = 2.934/14.026/95.504/15.351 ms, pipe 8, ipg/ewma 9.228/14.361 ms

-sami

Re: Recommendations for Multi SSID (AP+Adhoc) routers needed

@Floh1111
I think you have to narrow your search down between devices that are equipped with Ralink drivers, as the Fonera and D-Link you mentioned. AFAIK, mac80211/ath9k still doesn't allow simultaneous ad-hoc + AP mode.