Differences

This shows you the differences between two versions of the page.

Link to this comparison view

content:meshextender:prototyping_on_olinuxino_a13 [24/06/2013 07:30]
Paul Gardner-Stephen [Configuring AP+ad-hoc Wi-Fi]
content:meshextender:prototyping_on_olinuxino_a13 [24/06/2013 07:33] (current)
Paul Gardner-Stephen [Configuring AP+ad-hoc Wi-Fi]
Line 72: Line 72:
 The ath9k_htc driver requires patching to support simultaneous AP+adhoc mode, and this combination is not officially supported.  However, it does appear to work, with the caveat that it will only beacon the AP, not the ad-hoc cell.  That's mostly a bonus, as we don't waste airtime on ad-hoc beacons. The ath9k_htc driver requires patching to support simultaneous AP+adhoc mode, and this combination is not officially supported.  However, it does appear to work, with the caveat that it will only beacon the AP, not the ad-hoc cell.  That's mostly a bonus, as we don't waste airtime on ad-hoc beacons.
  
-Put something like the following in ''/etc/init.d/ath9k'' to get both simultaneous ap+adhoc (order of commands and order of raising interfaces seems to be important, but further exploration is required to confirm):+First, you need to install hostapd:  ''apt-get install hostapd'' (see previous discussion for getting Wi-Fi into client mode for easy downloading if required). 
 + 
 +Then put something like the following in ''/etc/init.d/ath9k'' to get both simultaneous ap+adhoc (order of commands and order of raising interfaces seems to be important, but further exploration is required to confirm):
  
 <file> <file>
Line 115: Line 117:
 iw dev adhoc0 ibss join mesh.servalproject.org 2437 02:ca:ff:dd:ca:ce iw dev adhoc0 ibss join mesh.servalproject.org 2437 02:ca:ff:dd:ca:ce
 </file> </file>
 +
 +Then create ''/etc/hostapd/hostapd.conf'' with the following:
 +
 +<file>
 +driver=nl80211
 +interface=public0
 +max_num_sta=255
 +ssid=public.servalproject.org
 +hw_mode=g
 +channel=6
 +ieee80211n=1
 +ht_capab=[HT40-][SHORT-GI-40][DSSS_CCK-40]
 +</file>
 +
 +Reboot, and viola!, you should have AP+ad-hoc mode.  This was tested to be able to ssh into one of our existing Mesh Extender units, confirming that arp and unicast traffic is fine.
  
 This will only work if you have applied the patch contained in: This will only work if you have applied the patch contained in:

Login