OK,... it took some doing, namely reinstalling both nodes to a clean slate, and making sure that 60-crda.rules exists in /etc/udev/rules.d (file is attached) and following <a href="http://www.pcengines.info/forums/?page=post&id=799918CD-66C8-40F6-A60B-26A05A078D08&fid=DC038CE7-688B-4FD7-A449-014010E444D1">This Forum Post</a>. I was able to get the ad-hoc 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) and wlan1 and wlan0 (on the node) meshed seamless?<br><br>Thanks guys for all your help.<br>John<br>
<br><br><div class="gmail_quote">On Wed, Jun 1, 2011 at 19:49, Kim-man 'Punky' TSE <span dir="ltr"><<a href="mailto:punkytse@punknix.com">punkytse@punknix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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 of us. Please let us know if you have sucessful result.<br>
<br>
Regards,<br>
Punky<div class="im"><br>
<br>
On 6/1/2011 5:44 PM, John Schultz wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
OK....<br>
<br>
I was able to get both systems in the sam ad-hoc cell, unable to ping each other. but they do show that they are in the sam cell when you do a 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></div><div><div></div><div class="h5">
On Wed, Jun 1, 2011 at 02:03, Kim-man 'Punky' TSE <<a href="mailto:punkytse@punknix.com" target="_blank">punkytse@punknix.com</a> <mailto:<a href="mailto:punkytse@punknix.com" target="_blank">punkytse@punknix.com</a>>> wrote:<br>
<br>
Hi all,<br>
<br>
I have updated the wpasupplicant to 0.7.3. Please try to see if it could run adhoc for nl80211-based drivers<br>
(i.e. ath9k, ath5k)<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 be a 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 that 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 config 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 -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>
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 -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 /etc/network/if-pre-up.d/wireless-tools<br>
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant<br>
<br>
ifconfig wlan0 10.1.0.1 netmask 255.0.0.0 broadcast 10.0.0.0 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 <<a href="mailto:gustin@meganerd.ca" target="_blank">gustin@meganerd.ca</a> <mailto:<a href="mailto:gustin@meganerd.ca" target="_blank">gustin@meganerd.ca</a>><br>
</div></div><div class="im">
<mailto:<a href="mailto:gustin@meganerd.ca" target="_blank">gustin@meganerd.ca</a> <mailto:<a href="mailto:gustin@meganerd.ca" target="_blank">gustin@meganerd.ca</a>>>> wrote:<br>
<br>
You may wish try simplifying your wpa_supplicant.conf<br>
<br>
Try removing everything except the ssid and psk lines. Then add the<br>
other variables in one at a time until you figure out which line is<br>
giving you the invalid argument error.<br>
<br>
You may also wish to try a 2.4 Ghz channel to start with. I have not<br>
checked in a while, but there used to be issues with 5Ghz 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" target="_blank">jschultz0614@gmail.com</a> <mailto:<a href="mailto:jschultz0614@gmail.com" target="_blank">jschultz0614@gmail.com</a>><br>
</div>
<mailto:<a href="mailto:jschultz0614@gmail.com" target="_blank">jschultz0614@gmail.com</a> <mailto:<a href="mailto:jschultz0614@gmail.com" target="_blank">jschultz0614@gmail.com</a>>>>:<div><div></div>
<div class="h5"><br>
<br>
> I am having issues getting WPA_Supplicant running in ad-hoc mode for a<br>
> multi-node mesh network.<br>
><br>
> Right now, there are only two nodes in this network as this is a 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 as well as calling<br>
> wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B and get the same<br>
> results either way.<br>
><br>
> For node 2, the config is virtually the same with the exception that wlan0<br>
> is now wlan1. wlan1 on this node is for client access using hostapd.<br>
><br>
> Ive spent over 8 hours on this problem so far with no luck and have not been<br>
> very fruitful searching google as everything I have found is a different<br>
> configuration of the above mentioned.<br>
><br>
> Any assistance ANY one can provide would be most appreciative.<br>
><br>
> Thanks,<br>
> John<br>
><br>
> _______________________________________________<br>
> Voyage-linux mailing list<br></div></div>
> <a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">Voyage-linux@list.voyage.hk</a> <mailto:<a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">Voyage-linux@list.voyage.hk</a>> <mailto:<a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">Voyage-linux@list.voyage.hk</a><div class="im">
<br>
<mailto:<a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">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" target="_blank">Voyage-linux@list.voyage.hk</a> <mailto:<a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">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></div><div class="im">
-- 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>
</div></blockquote><div><div></div><div class="h5">
<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>
</div></div></blockquote></div><br>