[Voyage-linux] Voyage Linux 0.7.0 (27-May-2011 build) and WPA_Supplicant
Gustin Johnson
(spam-protected)
Fri Jun 3 10:59:08 HKT 2011
brctl addbr bridge01
brctl addif bridge01 eth0
brctl addif bridge01 wlan0
brctl stp bridge01 on
The two interfaces are now bridged together. You should assign your
IPs to the bridge interface. There are examples in the
/etc/network/interfaces file already.
On Thu, Jun 2, 2011 at 6:33 PM, John Schultz <jschultz0614 at gmail.com> wrote:
> 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 This Forum Post. I was able to get the ad-hoc
> network up and running on channel 146 (802.11a)
>
> Whats the next step to get the wlan0 card and eth0 (on the gateway) and
> wlan1 and wlan0 (on the node) meshed seamless?
>
> Thanks guys for all your help.
> John
>
>
> On Wed, Jun 1, 2011 at 19:49, Kim-man 'Punky' TSE <punkytse at punknix.com>
> wrote:
>>
>> Hi John,
>>
>> You can try the commands from this link.
>> https://forum.openwrt.org/viewtopic.php?id=29876
>>
>> I think using nl80211-based drivers with adhoc mode is new to many of us.
>> Please let us know if you have sucessful result.
>>
>> Regards,
>> Punky
>>
>> On 6/1/2011 5:44 PM, John Schultz wrote:
>>>
>>> OK....
>>>
>>> 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.
>>>
>>> Sorry for being such a noob, Im a windows guy at heart.
>>>
>>> anyway, thanks in advance for your help.
>>> John
>>>
>>> On Wed, Jun 1, 2011 at 02:03, Kim-man 'Punky' TSE <punkytse at punknix.com
>>> <mailto:punkytse at punknix.com>> wrote:
>>>
>>> Hi all,
>>>
>>> I have updated the wpasupplicant to 0.7.3. Please try to see if it
>>> could run adhoc for nl80211-based drivers
>>> (i.e. ath9k, ath5k)
>>>
>>>
>>> http://www.voyage.hk/dists/experimental/wpasupplicant/wpasupplicant_0.7.3-3_i386.deb
>>>
>>> Again, suggest to test ad-hoc link first. hostapd should not be a
>>> problem.
>>>
>>> Regards,
>>> Punky
>>>
>>>
>>>
>>> On 6/1/2011 3:20 PM, John Schultz wrote:
>>>
>>> Made changes as suggested on node 0 - (I failed to mention that
>>> this is a full blown install of Debian 0.6.0a
>>> w/ kernel 2.6.39-rc7 -- apologies)
>>>
>>> This node or server is the jump off point and has the same config
>>> files as node 1 does. I should also mention
>>> that I get the same results on node 1 as I do on node 0.
>>>
>>> This is what I have for my interfaces file:
>>>
>>> auto lo
>>> iface lo inet loopback
>>>
>>> auto eth0
>>> iface eth0 inet dhcp
>>>
>>> auto wlan0
>>> iface wlan0 inet static
>>> address 10.1.0.1
>>> netmask 255.0.0.0
>>> broadcast 10.0.0.0
>>> gateway 10.0.0.1
>>> wireless-channel 1
>>> wireless-essid ####################
>>> wireless-mode ad-hoc
>>> pre-up wpa_supplicant -B -Dwext -i wlan0
>>> -c/etc/wpa_supplicant.conf
>>> post-down killall -q wpa_supplicant
>>>
>>>
>>> and wpa_supplicant.conf:
>>>
>>> network={
>>> ssid="OmegaMeshBackhual"
>>>
>>> psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
>>> }
>>>
>>>
>>> here is the output from ifup wlan0 -v
>>>
>>> Configuring interface wlan0=wlan0 (inet)
>>> wpa_supplicant -B -Dwext -i wlan0 -c/etc/wpa_supplicant.conf
>>> ioctl[SIOCSIWPMKSA]: Invalid argument
>>> run-parts --verbose /etc/network/if-pre-up.d
>>> run-parts: executing /etc/network/if-pre-up.d/bridge
>>> run-parts: executing /etc/network/if-pre-up.d/hostapd
>>> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
>>> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
>>>
>>> ifconfig wlan0 10.1.0.1 netmask 255.0.0.0 broadcast 10.0.0.0
>>> up
>>> route add default gw 10.0.0.1 wlan0
>>> run-parts --verbose /etc/network/if-up.d
>>> run-parts: executing /etc/network/if-up.d/000resolvconf
>>> run-parts: executing /etc/network/if-up.d/avahi-autoipd
>>> run-parts: executing /etc/network/if-up.d/avahi-daemon
>>> run-parts: executing /etc/network/if-up.d/bind9
>>> run-parts: executing /etc/network/if-up.d/mountnfs
>>> run-parts: executing /etc/network/if-up.d/openssh-server
>>> run-parts: executing /etc/network/if-up.d/samba
>>> run-parts: executing /etc/network/if-up.d/wpasupplicant
>>>
>>>
>>> Thanks again,
>>> John
>>>
>>> On Wed, Jun 1, 2011 at 01:01, Gustin Johnson <gustin at meganerd.ca
>>> <mailto:gustin at meganerd.ca>
>>> <mailto:gustin at meganerd.ca <mailto:gustin at meganerd.ca>>> wrote:
>>>
>>> You may wish try simplifying your wpa_supplicant.conf
>>>
>>> Try removing everything except the ssid and psk lines. Then
>>> add the
>>> other variables in one at a time until you figure out which
>>> line is
>>> giving you the invalid argument error.
>>>
>>> You may also wish to try a 2.4 Ghz channel to start with. I
>>> have not
>>> checked in a while, but there used to be issues with 5Ghz
>>> channels in
>>> AP mode for some drivers (most of the open ones).
>>>
>>> 2011/5/31 John Schultz <jschultz0614 at gmail.com
>>> <mailto:jschultz0614 at gmail.com>
>>> <mailto:jschultz0614 at gmail.com <mailto:jschultz0614 at gmail.com>>>:
>>>
>>> > I am having issues getting WPA_Supplicant running in ad-hoc mode
>>> for a
>>> > multi-node mesh network.
>>> >
>>> > Right now, there are only two nodes in this network as this is a
>>> development
>>> > setting.
>>> >
>>> > Both nodes are running 2.6.38 or better
>>> >
>>> > Config for node 1 is as follows:
>>> > wlan0 is a DNMA-92
>>> >
>>> > interfaces file:
>>> >>
>>> >> auto lo
>>> >>
>>> >> iface lo inet loopback
>>> >>
>>> >> auto eth0
>>> >> iface eth0 inet dhcp
>>> >>
>>> >> auto wlan0
>>> >> iface wlan0 inet static
>>> >> address 10.1.0.1
>>> >> netmask 255.0.0.0
>>> >> broadcast 10.0.0.0
>>> >> gateway 10.0.0.1
>>> >> wireless-channel 149
>>> >> wireless-essid #################
>>> >> wireless-mode ad-hoc
>>> >
>>> > wpa_supplicant.conf
>>> >>
>>> >> ctrl_interface=/var/run/wpa_supplicant
>>> >> network={
>>> >> ssid="#################"
>>> >> key_mgmt=WPA-NONE
>>> >> mode=1
>>> >> proto=WPA
>>> >> pairwise=NONE
>>> >> group=TKIP
>>> >> psk="#################"
>>> >> }
>>> >
>>> > when this node is started up, I get
>>> > ioctl[SIOCSIWPMKSA]: Invalid argument
>>> >
>>> > I have tried adding the wpa-conf flag in the interfaces as well
>>> as calling
>>> > wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B and
>>> get the same
>>> > results either way.
>>> >
>>> > For node 2, the config is virtually the same with the exception
>>> that wlan0
>>> > is now wlan1. wlan1 on this node is for client access using
>>> hostapd.
>>> >
>>> > Ive spent over 8 hours on this problem so far with no luck and
>>> have not been
>>> > very fruitful searching google as everything I have found is a
>>> different
>>> > configuration of the above mentioned.
>>> >
>>> > Any assistance ANY one can provide would be most appreciative.
>>> >
>>> > Thanks,
>>> > John
>>> >
>>> > _______________________________________________
>>> > Voyage-linux mailing list
>>> > Voyage-linux at list.voyage.hk <mailto:Voyage-linux at list.voyage.hk>
>>> <mailto:Voyage-linux at list.voyage.hk
>>> <mailto:Voyage-linux at list.voyage.hk>>
>>>
>>> > http://list.voyage.hk/mailman/listinfo/voyage-linux
>>> >
>>> >
>>>
>>>
>>>
>>> _______________________________________________
>>> Voyage-linux mailing list
>>> Voyage-linux at list.voyage.hk <mailto:Voyage-linux at list.voyage.hk>
>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>>
>>>
>>>
>>> -- Regards,
>>> Kim-man "Punky" Tse
>>>
>>> * Open Source Embedded Solutions and Systems
>>> - Voyage Linux (http://linux.voyage.hk)
>>> - Voyage ONE (http://linux.voyage.hk/voyage-one)
>>> - Voyage MPD (http://linux.voyage.hk/voyage-mpd)
>>> * Voyage Store (http://store.voyage.hk)
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>> Kim-man "Punky" Tse
>>
>> * Open Source Embedded Solutions and Systems
>> - Voyage Linux (http://linux.voyage.hk)
>> - Voyage ONE (http://linux.voyage.hk/voyage-one)
>> - Voyage MPD (http://linux.voyage.hk/voyage-mpd)
>> * Voyage Store (http://store.voyage.hk)
>>
>>
>
>
More information about the Voyage-linux
mailing list