We actually read up on batman, didnt think it was viable, however I will try it in the lab setting and see what happens.<br><br>Thanks again,<br>John<br><br><div class="gmail_quote">On Fri, Jun 3, 2011 at 10:52, Gustin Johnson <span dir="ltr"><<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I am not sure what you are trying to do, but have you looked at B.A.T.M.A.N.?<br>
<br>
<a href="http://en.wikipedia.org/wiki/B.A.T.M.A.N" target="_blank">http://en.wikipedia.org/wiki/B.A.T.M.A.N</a>.<br>
<a href="http://www.open-mesh.org/" target="_blank">http://www.open-mesh.org/</a><br>
<br>
I get the sense that this might be helpful.<br>
<div><div></div><div class="h5"><br>
On Fri, Jun 3, 2011 at 2:12 AM, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>> wrote:<br>
> I had to think about that for a minute or so.<br>
><br>
> According to an article I just read, ad-hoc networks do not inherently allow<br>
> for bridging to wired lans with out a special gateway. And they are for use<br>
> with small networks only.<br>
><br>
> Sigh...<br>
><br>
> Back to the drawing board.<br>
><br>
> Thanks,<br>
> John<br>
><br>
> On Fri, Jun 3, 2011 at 00:40, Gustin Johnson <<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a>> wrote:<br>
>><br>
>> You still need to use brctl.<br>
>><br>
>> I have a wireless device bridged with one of the lan ports on my Alix<br>
>> SBC, so I am pretty sure that the kernel supports it. You also should<br>
>> be setting the IP on the bridge device and not the physical interface.<br>
>> I am not currently at a machine with wireless, but I know that this<br>
>> does work. Perhaps it is a function of the wireless card being in<br>
>> ad-hoc mode, I have only ever done this as an AP or client.<br>
>><br>
>> On Fri, Jun 3, 2011 at 12:08 AM, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>> wrote:<br>
>> > I just ran across a page discussing ebtables, would this help at all?<br>
>> ><br>
>> > On Thu, Jun 2, 2011 at 21:56, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> I tied to add the wlan0 iface to the bridge and I get "can't add wlan0<br>
>> >> to<br>
>> >> bridge bridge0: Operation not supported"<br>
>> >><br>
>> >> Also after I add eth0 to the bridge it makes the interface unstable as<br>
>> >> it<br>
>> >> will not ping out or allow traffic in.<br>
>> >><br>
>> >> I am assuming this is to be done on the gateway machine as I have read<br>
>> >> several times that bridging wlan ifaces is not supported in this<br>
>> >> kernel.<br>
>> >> Unless I have missed something.<br>
>> >><br>
>> >> Here are some diagnostic information:<br>
>> >> iw list:<br>
>> >>><br>
>> >>> Wiphy phy0<br>
>> >>> Band 1:<br>
>> >>> Capabilities: 0x11ce<br>
>> >>> HT20/HT40<br>
>> >>> SM Power Save disabled<br>
>> >>> RX HT40 SGI<br>
>> >>> TX STBC<br>
>> >>> RX STBC 1-stream<br>
>> >>> Max AMSDU length: 7935 bytes<br>
>> >>> DSSS/CCK HT40<br>
>> >>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)<br>
>> >>> Minimum RX AMPDU time spacing: 8 usec (0x06)<br>
>> >>> HT TX/RX MCS rate indexes supported: 0-15<br>
>> >>> Frequencies:<br>
>> >>> * 2412 MHz [1] (27.0 dBm)<br>
>> >>> * 2417 MHz [2] (27.0 dBm)<br>
>> >>> * 2422 MHz [3] (27.0 dBm)<br>
>> >>> * 2427 MHz [4] (27.0 dBm)<br>
>> >>> * 2432 MHz [5] (27.0 dBm)<br>
>> >>> * 2437 MHz [6] (27.0 dBm)<br>
>> >>> * 2442 MHz [7] (27.0 dBm)<br>
>> >>> * 2447 MHz [8] (27.0 dBm)<br>
>> >>> * 2452 MHz [9] (27.0 dBm)<br>
>> >>> * 2457 MHz [10] (27.0 dBm)<br>
>> >>> * 2462 MHz [11] (27.0 dBm)<br>
>> >>> * 2467 MHz [12] (disabled)<br>
>> >>> * 2472 MHz [13] (disabled)<br>
>> >>> * 2484 MHz [14] (disabled)<br>
>> >>> Bitrates (non-HT):<br>
>> >>> * 1.0 Mbps<br>
>> >>> * 2.0 Mbps (short preamble supported)<br>
>> >>> * 5.5 Mbps (short preamble supported)<br>
>> >>> * 11.0 Mbps (short preamble supported)<br>
>> >>> * 6.0 Mbps<br>
>> >>> * 9.0 Mbps<br>
>> >>> * 12.0 Mbps<br>
>> >>> * 18.0 Mbps<br>
>> >>> * 24.0 Mbps<br>
>> >>> * 36.0 Mbps<br>
>> >>> * 48.0 Mbps<br>
>> >>> * 54.0 Mbps<br>
>> >>> Band 2:<br>
>> >>> Capabilities: 0x11ce<br>
>> >>> HT20/HT40<br>
>> >>> SM Power Save disabled<br>
>> >>> RX HT40 SGI<br>
>> >>> TX STBC<br>
>> >>> RX STBC 1-stream<br>
>> >>> Max AMSDU length: 7935 bytes<br>
>> >>> DSSS/CCK HT40<br>
>> >>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)<br>
>> >>> Minimum RX AMPDU time spacing: 8 usec (0x06)<br>
>> >>> HT TX/RX MCS rate indexes supported: 0-15<br>
>> >>> Frequencies:<br>
>> >>> * 5180 MHz [36] (17.0 dBm)<br>
>> >>> * 5200 MHz [40] (17.0 dBm)<br>
>> >>> * 5220 MHz [44] (17.0 dBm)<br>
>> >>> * 5240 MHz [48] (17.0 dBm)<br>
>> >>> * 5260 MHz [52] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5280 MHz [56] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5300 MHz [60] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5320 MHz [64] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5500 MHz [100] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5520 MHz [104] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5540 MHz [108] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5560 MHz [112] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5580 MHz [116] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5600 MHz [120] (disabled)<br>
>> >>> * 5620 MHz [124] (disabled)<br>
>> >>> * 5640 MHz [128] (disabled)<br>
>> >>> * 5660 MHz [132] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5680 MHz [136] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5700 MHz [140] (20.0 dBm) (passive scanning,<br>
>> >>> no<br>
>> >>> IBSS, radar detection)<br>
>> >>> * 5745 MHz [149] (30.0 dBm)<br>
>> >>> * 5765 MHz [153] (30.0 dBm)<br>
>> >>> * 5785 MHz [157] (30.0 dBm)<br>
>> >>> * 5805 MHz [161] (30.0 dBm)<br>
>> >>> * 5825 MHz [165] (30.0 dBm)<br>
>> >>> Bitrates (non-HT):<br>
>> >>> * 6.0 Mbps<br>
>> >>> * 9.0 Mbps<br>
>> >>> * 12.0 Mbps<br>
>> >>> * 18.0 Mbps<br>
>> >>> * 24.0 Mbps<br>
>> >>> * 36.0 Mbps<br>
>> >>> * 48.0 Mbps<br>
>> >>> * 54.0 Mbps<br>
>> >>> max # scan SSIDs: 4<br>
>> >>> Supported interface modes:<br>
>> >>> * IBSS<br>
>> >>> * managed<br>
>> >>> * AP<br>
>> >>> * AP/VLAN<br>
>> >>> * WDS<br>
>> >>> * monitor<br>
>> >>> * mesh point<br>
>> >>> * Unknown mode (8)<br>
>> >>> * Unknown mode (9)<br>
>> >>> Supported commands:<br>
>> >>> * new_interface<br>
>> >>> * set_interface<br>
>> >>> * new_key<br>
>> >>> * new_beacon<br>
>> >>> * new_station<br>
>> >>> * new_mpath<br>
>> >>> * set_mesh_params<br>
>> >>> * set_bss<br>
>> >>> * authenticate<br>
>> >>> * associate<br>
>> >>> * deauthenticate<br>
>> >>> * disassociate<br>
>> >>> * join_ibss<br>
>> >>> * Unknown command (68)<br>
>> >>> * Unknown command (55)<br>
>> >>> * Unknown command (57)<br>
>> >>> * Unknown command (59)<br>
>> >>> * Unknown command (67)<br>
>> >>> * set_wiphy_netns<br>
>> >>> * Unknown command (65)<br>
>> >>> * Unknown command (66)<br>
>> >>> * connect<br>
>> >>> * disconnect<br>
>> >><br>
>> >> iw dev wlan0 station dump<br>
>> >>><br>
>> >>> Station 00:1b:b1:5d:ac:3c (on wlan0)<br>
>> >>> inactive time: 2680 ms<br>
>> >>> rx bytes: 36426<br>
>> >>> rx packets: 934<br>
>> >>> tx bytes: 0<br>
>> >>> tx packets: 0<br>
>> >>> signal: -79 dBm<br>
>> >>> tx bitrate: 6.0 MBit/s<br>
>> >>><br>
>> >><br>
>> >> ifconfig<br>
>> >>><br>
>> >>> eth0 Link encap:Ethernet HWaddr 00:16:76:90:49:b7<br>
>> >>> inet addr:10.0.0.17 Bcast:10.255.255.255 Mask:255.0.0.0<br>
>> >>> inet6 addr: fe80::216:76ff:fe90:49b7/64 Scope:Link<br>
>> >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
>> >>> RX packets:3416 errors:0 dropped:0 overruns:0 frame:0<br>
>> >>> TX packets:4606 errors:0 dropped:0 overruns:0 carrier:0<br>
>> >>> collisions:0 txqueuelen:1000<br>
>> >>> RX bytes:777960 (759.7 KiB) TX bytes:310196 (302.9 KiB)<br>
>> >>><br>
>> >>> lo Link encap:Local Loopback<br>
>> >>> inet addr:127.0.0.1 Mask:255.0.0.0<br>
>> >>> inet6 addr: ::1/128 Scope:Host<br>
>> >>> UP LOOPBACK RUNNING MTU:16436 Metric:1<br>
>> >>> RX packets:224 errors:0 dropped:0 overruns:0 frame:0<br>
>> >>> TX packets:224 errors:0 dropped:0 overruns:0 carrier:0<br>
>> >>> collisions:0 txqueuelen:0<br>
>> >>> RX bytes:33981 (33.1 KiB) TX bytes:33981 (33.1 KiB)<br>
>> >>><br>
>> >>> wlan0 Link encap:Ethernet HWaddr 00:1b:b1:5d:ae:08<br>
>> >>> inet addr:10.1.0.1 Bcast:10.1.255.255 Mask:255.255.0.0<br>
>> >>> inet6 addr: fe80::21b:b1ff:fe5d:ae08/64 Scope:Link<br>
>> >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
>> >>> RX packets:5 errors:0 dropped:0 overruns:0 frame:0<br>
>> >>> TX packets:128 errors:0 dropped:0 overruns:0 carrier:0<br>
>> >>> collisions:0 txqueuelen:1000<br>
>> >>> RX bytes:378 (378.0 B) TX bytes:22903 (22.3 KiB)<br>
>> >><br>
>> >> iwconfig<br>
>> >>><br>
>> >>> lo no wireless extensions.<br>
>> >>><br>
>> >>> eth0 no wireless extensions.<br>
>> >>><br>
>> >>> wlan0 IEEE 802.11abgn ESSID:"###############"<br>
>> >>> Mode:Ad-Hoc Frequency:5.745 GHz Cell: 5E:F8:F9:99:8C:FA<br>
>> >>> Tx-Power=30 dBm<br>
>> >>> Retry long limit:7 RTS thr:off Fragment thr:off<br>
>> >>> Encryption key:off<br>
>> >>> Power Management:on<br>
>> >><br>
>> >> I have not enabled wpa_supplicant yet as I need to get the network<br>
>> >> working<br>
>> >> before I can start locking it down.<br>
>> >><br>
>> >> Thanks,<br>
>> >> John<br>
>> >><br>
>> >> On Thu, Jun 2, 2011 at 20:59, Gustin Johnson <<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> brctl addbr bridge01<br>
>> >>> brctl addif bridge01 eth0<br>
>> >>> brctl addif bridge01 wlan0<br>
>> >>> brctl stp bridge01 on<br>
>> >>><br>
>> >>> The two interfaces are now bridged together. You should assign your<br>
>> >>> IPs to the bridge interface. There are examples in the<br>
>> >>> /etc/network/interfaces file already.<br>
>> >>><br>
>> >>> On Thu, Jun 2, 2011 at 6:33 PM, John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>> > OK,... it took some doing, namely reinstalling both nodes to a clean<br>
>> >>> > slate,<br>
>> >>> > and making sure that 60-crda.rules exists in /etc/udev/rules.d (file<br>
>> >>> > is<br>
>> >>> > attached) and following This Forum Post. I was able to get the<br>
>> >>> > ad-hoc<br>
>> >>> > network up and running on channel 146 (802.11a)<br>
>> >>> ><br>
>> >>> > Whats the next step to get the wlan0 card and eth0 (on the gateway)<br>
>> >>> > and<br>
>> >>> > wlan1 and wlan0 (on the node) meshed seamless?<br>
>> >>> ><br>
>> >>> > Thanks guys for all your help.<br>
>> >>> > John<br>
>> >>> ><br>
>> >>> ><br>
>> >>> > On Wed, Jun 1, 2011 at 19:49, Kim-man 'Punky' TSE<br>
>> >>> > <<a href="mailto:punkytse@punknix.com">punkytse@punknix.com</a>><br>
>> >>> > wrote:<br>
>> >>> >><br>
>> >>> >> Hi John,<br>
>> >>> >><br>
>> >>> >> You can try the commands from this link.<br>
>> >>> >> <a href="https://forum.openwrt.org/viewtopic.php?id=29876" target="_blank">https://forum.openwrt.org/viewtopic.php?id=29876</a><br>
>> >>> >><br>
>> >>> >> I think using nl80211-based drivers with adhoc mode is new to many<br>
>> >>> >> of<br>
>> >>> >> us.<br>
>> >>> >> Please let us know if you have sucessful result.<br>
>> >>> >><br>
>> >>> >> Regards,<br>
>> >>> >> Punky<br>
>> >>> >><br>
>> >>> >> On 6/1/2011 5:44 PM, John Schultz wrote:<br>
>> >>> >>><br>
>> >>> >>> OK....<br>
>> >>> >>><br>
>> >>> >>> I was able to get both systems in the sam ad-hoc cell, unable to<br>
>> >>> >>> ping<br>
>> >>> >>> each other. but they do show that they are in the sam cell when<br>
>> >>> >>> you<br>
>> >>> >>> do a<br>
>> >>> >>> iwconfig.<br>
>> >>> >>><br>
>> >>> >>> Sorry for being such a noob, Im a windows guy at heart.<br>
>> >>> >>><br>
>> >>> >>> anyway, thanks in advance for your help.<br>
>> >>> >>> John<br>
>> >>> >>><br>
>> >>> >>> On Wed, Jun 1, 2011 at 02:03, Kim-man 'Punky' TSE<br>
>> >>> >>> <<a href="mailto:punkytse@punknix.com">punkytse@punknix.com</a><br>
>> >>> >>> <mailto:<a href="mailto:punkytse@punknix.com">punkytse@punknix.com</a>>> wrote:<br>
>> >>> >>><br>
>> >>> >>> Hi all,<br>
>> >>> >>><br>
>> >>> >>> I have updated the wpasupplicant to 0.7.3. Please try to see<br>
>> >>> >>> if<br>
>> >>> >>> it<br>
>> >>> >>> could run adhoc for nl80211-based drivers<br>
>> >>> >>> (i.e. ath9k, ath5k)<br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> <a href="http://www.voyage.hk/dists/experimental/wpasupplicant/wpasupplicant_0.7.3-3_i386.deb" target="_blank">http://www.voyage.hk/dists/experimental/wpasupplicant/wpasupplicant_0.7.3-3_i386.deb</a><br>
>> >>> >>><br>
>> >>> >>> Again, suggest to test ad-hoc link first. hostapd should not<br>
>> >>> >>> be a<br>
>> >>> >>> problem.<br>
>> >>> >>><br>
>> >>> >>> Regards,<br>
>> >>> >>> Punky<br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> On 6/1/2011 3:20 PM, John Schultz wrote:<br>
>> >>> >>><br>
>> >>> >>> Made changes as suggested on node 0 - (I failed to mention<br>
>> >>> >>> that<br>
>> >>> >>> this is a full blown install of Debian 0.6.0a<br>
>> >>> >>> w/ kernel 2.6.39-rc7 -- apologies)<br>
>> >>> >>><br>
>> >>> >>> This node or server is the jump off point and has the same<br>
>> >>> >>> config<br>
>> >>> >>> files as node 1 does. I should also mention<br>
>> >>> >>> that I get the same results on node 1 as I do on node 0.<br>
>> >>> >>><br>
>> >>> >>> This is what I have for my interfaces file:<br>
>> >>> >>><br>
>> >>> >>> auto lo<br>
>> >>> >>> iface lo inet loopback<br>
>> >>> >>><br>
>> >>> >>> auto eth0<br>
>> >>> >>> iface eth0 inet dhcp<br>
>> >>> >>><br>
>> >>> >>> auto wlan0<br>
>> >>> >>> iface wlan0 inet static<br>
>> >>> >>> address 10.1.0.1<br>
>> >>> >>> netmask 255.0.0.0<br>
>> >>> >>> broadcast 10.0.0.0<br>
>> >>> >>> gateway 10.0.0.1<br>
>> >>> >>> wireless-channel 1<br>
>> >>> >>> wireless-essid ####################<br>
>> >>> >>> wireless-mode ad-hoc<br>
>> >>> >>> pre-up wpa_supplicant -B -Dwext -i wlan0<br>
>> >>> >>> -c/etc/wpa_supplicant.conf<br>
>> >>> >>> post-down killall -q wpa_supplicant<br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> and wpa_supplicant.conf:<br>
>> >>> >>><br>
>> >>> >>> network={<br>
>> >>> >>> ssid="OmegaMeshBackhual"<br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb<br>
>> >>> >>> }<br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> here is the output from ifup wlan0 -v<br>
>> >>> >>><br>
>> >>> >>> Configuring interface wlan0=wlan0 (inet)<br>
>> >>> >>> wpa_supplicant -B -Dwext -i wlan0<br>
>> >>> >>> -c/etc/wpa_supplicant.conf<br>
>> >>> >>> ioctl[SIOCSIWPMKSA]: Invalid argument<br>
>> >>> >>> run-parts --verbose /etc/network/if-pre-up.d<br>
>> >>> >>> run-parts: executing /etc/network/if-pre-up.d/bridge<br>
>> >>> >>> run-parts: executing /etc/network/if-pre-up.d/hostapd<br>
>> >>> >>> run-parts: executing<br>
>> >>> >>> /etc/network/if-pre-up.d/wireless-tools<br>
>> >>> >>> run-parts: executing<br>
>> >>> >>> /etc/network/if-pre-up.d/wpasupplicant<br>
>> >>> >>><br>
>> >>> >>> ifconfig wlan0 10.1.0.1 netmask 255.0.0.0 broadcast<br>
>> >>> >>> 10.0.0.0<br>
>> >>> >>> up<br>
>> >>> >>> route add default gw 10.0.0.1 wlan0<br>
>> >>> >>> run-parts --verbose /etc/network/if-up.d<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/000resolvconf<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/avahi-autoipd<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/avahi-daemon<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/bind9<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/mountnfs<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/openssh-server<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/samba<br>
>> >>> >>> run-parts: executing /etc/network/if-up.d/wpasupplicant<br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> Thanks again,<br>
>> >>> >>> John<br>
>> >>> >>><br>
>> >>> >>> On Wed, Jun 1, 2011 at 01:01, Gustin Johnson<br>
>> >>> >>> <<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a><br>
>> >>> >>> <mailto:<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a>><br>
>> >>> >>> <mailto:<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a> <mailto:<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a>>>><br>
>> >>> >>> wrote:<br>
>> >>> >>><br>
>> >>> >>> You may wish try simplifying your wpa_supplicant.conf<br>
>> >>> >>><br>
>> >>> >>> Try removing everything except the ssid and psk lines.<br>
>> >>> >>> Then<br>
>> >>> >>> add the<br>
>> >>> >>> other variables in one at a time until you figure out<br>
>> >>> >>> which<br>
>> >>> >>> line is<br>
>> >>> >>> giving you the invalid argument error.<br>
>> >>> >>><br>
>> >>> >>> You may also wish to try a 2.4 Ghz channel to start<br>
>> >>> >>> with.<br>
>> >>> >>> I<br>
>> >>> >>> have not<br>
>> >>> >>> checked in a while, but there used to be issues with<br>
>> >>> >>> 5Ghz<br>
>> >>> >>> channels in<br>
>> >>> >>> AP mode for some drivers (most of the open ones).<br>
>> >>> >>><br>
>> >>> >>> 2011/5/31 John Schultz <<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a><br>
>> >>> >>> <mailto:<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>><br>
>> >>> >>> <mailto:<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a><br>
>> >>> >>> <mailto:<a href="mailto:jschultz0614@gmail.com">jschultz0614@gmail.com</a>>>>:<br>
>> >>> >>><br>
>> >>> >>> > I am having issues getting WPA_Supplicant running in<br>
>> >>> >>> ad-hoc<br>
>> >>> >>> mode<br>
>> >>> >>> for a<br>
>> >>> >>> > multi-node mesh network.<br>
>> >>> >>> ><br>
>> >>> >>> > Right now, there are only two nodes in this network as<br>
>> >>> >>> this<br>
>> >>> >>> is a<br>
>> >>> >>> development<br>
>> >>> >>> > setting.<br>
>> >>> >>> ><br>
>> >>> >>> > Both nodes are running 2.6.38 or better<br>
>> >>> >>> ><br>
>> >>> >>> > Config for node 1 is as follows:<br>
>> >>> >>> > wlan0 is a DNMA-92<br>
>> >>> >>> ><br>
>> >>> >>> > interfaces file:<br>
>> >>> >>> >><br>
>> >>> >>> >> auto lo<br>
>> >>> >>> >><br>
>> >>> >>> >> iface lo inet loopback<br>
>> >>> >>> >><br>
>> >>> >>> >> auto eth0<br>
>> >>> >>> >> iface eth0 inet dhcp<br>
>> >>> >>> >><br>
>> >>> >>> >> auto wlan0<br>
>> >>> >>> >> iface wlan0 inet static<br>
>> >>> >>> >> address 10.1.0.1<br>
>> >>> >>> >> netmask 255.0.0.0<br>
>> >>> >>> >> broadcast 10.0.0.0<br>
>> >>> >>> >> gateway 10.0.0.1<br>
>> >>> >>> >> wireless-channel 149<br>
>> >>> >>> >> wireless-essid #################<br>
>> >>> >>> >> wireless-mode ad-hoc<br>
>> >>> >>> ><br>
>> >>> >>> > wpa_supplicant.conf<br>
>> >>> >>> >><br>
>> >>> >>> >> ctrl_interface=/var/run/wpa_supplicant<br>
>> >>> >>> >> network={<br>
>> >>> >>> >> ssid="#################"<br>
>> >>> >>> >> key_mgmt=WPA-NONE<br>
>> >>> >>> >> mode=1<br>
>> >>> >>> >> proto=WPA<br>
>> >>> >>> >> pairwise=NONE<br>
>> >>> >>> >> group=TKIP<br>
>> >>> >>> >> psk="#################"<br>
>> >>> >>> >> }<br>
>> >>> >>> ><br>
>> >>> >>> > when this node is started up, I get<br>
>> >>> >>> > ioctl[SIOCSIWPMKSA]: Invalid argument<br>
>> >>> >>> ><br>
>> >>> >>> > I have tried adding the wpa-conf flag in the interfaces<br>
>> >>> >>> as<br>
>> >>> >>> well<br>
>> >>> >>> as calling<br>
>> >>> >>> > wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf<br>
>> >>> >>> -B<br>
>> >>> >>> and<br>
>> >>> >>> get the same<br>
>> >>> >>> > results either way.<br>
>> >>> >>> ><br>
>> >>> >>> > For node 2, the config is virtually the same with the<br>
>> >>> >>> exception<br>
>> >>> >>> that wlan0<br>
>> >>> >>> > is now wlan1. wlan1 on this node is for client access<br>
>> >>> >>> using<br>
>> >>> >>> hostapd.<br>
>> >>> >>> ><br>
>> >>> >>> > Ive spent over 8 hours on this problem so far with no<br>
>> >>> >>> luck<br>
>> >>> >>> and<br>
>> >>> >>> have not been<br>
>> >>> >>> > very fruitful searching google as everything I have found<br>
>> >>> >>> is<br>
>> >>> >>> a<br>
>> >>> >>> different<br>
>> >>> >>> > configuration of the above mentioned.<br>
>> >>> >>> ><br>
>> >>> >>> > Any assistance ANY one can provide would be most<br>
>> >>> >>> appreciative.<br>
>> >>> >>> ><br>
>> >>> >>> > Thanks,<br>
>> >>> >>> > John<br>
>> >>> >>> ><br>
>> >>> >>> > _______________________________________________<br>
>> >>> >>> > Voyage-linux mailing list<br>
>> >>> >>> > <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
>> >>> >>> <mailto:<a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a>><br>
>> >>> >>> <mailto:<a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
>> >>> >>> <mailto:<a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a>>><br>
>> >>> >>><br>
>> >>> >>> > <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux" target="_blank">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
>> >>> >>> ><br>
>> >>> >>> ><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> _______________________________________________<br>
>> >>> >>> Voyage-linux mailing list<br>
>> >>> >>> <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
>> >>> >>> <mailto:<a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a>><br>
>> >>> >>> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux" target="_blank">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>> -- Regards,<br>
>> >>> >>> Kim-man "Punky" Tse<br>
>> >>> >>><br>
>> >>> >>> * Open Source Embedded Solutions and Systems<br>
>> >>> >>> - Voyage Linux (<a href="http://linux.voyage.hk" target="_blank">http://linux.voyage.hk</a>)<br>
>> >>> >>> - Voyage ONE (<a href="http://linux.voyage.hk/voyage-one" target="_blank">http://linux.voyage.hk/voyage-one</a>)<br>
>> >>> >>> - Voyage MPD (<a href="http://linux.voyage.hk/voyage-mpd" target="_blank">http://linux.voyage.hk/voyage-mpd</a>)<br>
>> >>> >>> * Voyage Store (<a href="http://store.voyage.hk" target="_blank">http://store.voyage.hk</a>)<br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >>><br>
>> >>> >><br>
>> >>> >><br>
>> >>> >> --<br>
>> >>> >> Regards,<br>
>> >>> >> Kim-man "Punky" Tse<br>
>> >>> >><br>
>> >>> >> * Open Source Embedded Solutions and Systems<br>
>> >>> >> - Voyage Linux (<a href="http://linux.voyage.hk" target="_blank">http://linux.voyage.hk</a>)<br>
>> >>> >> - Voyage ONE (<a href="http://linux.voyage.hk/voyage-one" target="_blank">http://linux.voyage.hk/voyage-one</a>)<br>
>> >>> >> - Voyage MPD (<a href="http://linux.voyage.hk/voyage-mpd" target="_blank">http://linux.voyage.hk/voyage-mpd</a>)<br>
>> >>> >> * Voyage Store (<a href="http://store.voyage.hk" target="_blank">http://store.voyage.hk</a>)<br>
>> >>> >><br>
>> >>> >><br>
>> >>> ><br>
>> >>> ><br>
>> >><br>
>> ><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br>