[Voyage-linux] Voyage Linux 0.7.0 (27-May-2011 build) and WPA_Supplicant
John Schultz
(spam-protected)
Sat Jun 4 06:35:49 HKT 2011
We actually read up on batman, didnt think it was viable, however I will try
it in the lab setting and see what happens.
Thanks again,
John
On Fri, Jun 3, 2011 at 10:52, Gustin Johnson <gustin at meganerd.ca> wrote:
> I am not sure what you are trying to do, but have you looked at
> B.A.T.M.A.N.?
>
> http://en.wikipedia.org/wiki/B.A.T.M.A.N.
> http://www.open-mesh.org/
>
> I get the sense that this might be helpful.
>
> On Fri, Jun 3, 2011 at 2:12 AM, John Schultz <jschultz0614 at gmail.com>
> wrote:
> > I had to think about that for a minute or so.
> >
> > According to an article I just read, ad-hoc networks do not inherently
> allow
> > for bridging to wired lans with out a special gateway. And they are for
> use
> > with small networks only.
> >
> > Sigh...
> >
> > Back to the drawing board.
> >
> > Thanks,
> > John
> >
> > On Fri, Jun 3, 2011 at 00:40, Gustin Johnson <gustin at meganerd.ca> wrote:
> >>
> >> You still need to use brctl.
> >>
> >> I have a wireless device bridged with one of the lan ports on my Alix
> >> SBC, so I am pretty sure that the kernel supports it. You also should
> >> be setting the IP on the bridge device and not the physical interface.
> >> I am not currently at a machine with wireless, but I know that this
> >> does work. Perhaps it is a function of the wireless card being in
> >> ad-hoc mode, I have only ever done this as an AP or client.
> >>
> >> On Fri, Jun 3, 2011 at 12:08 AM, John Schultz <jschultz0614 at gmail.com>
> >> wrote:
> >> > I just ran across a page discussing ebtables, would this help at all?
> >> >
> >> > On Thu, Jun 2, 2011 at 21:56, John Schultz <jschultz0614 at gmail.com>
> >> > wrote:
> >> >>
> >> >> I tied to add the wlan0 iface to the bridge and I get "can't add
> wlan0
> >> >> to
> >> >> bridge bridge0: Operation not supported"
> >> >>
> >> >> Also after I add eth0 to the bridge it makes the interface unstable
> as
> >> >> it
> >> >> will not ping out or allow traffic in.
> >> >>
> >> >> I am assuming this is to be done on the gateway machine as I have
> read
> >> >> several times that bridging wlan ifaces is not supported in this
> >> >> kernel.
> >> >> Unless I have missed something.
> >> >>
> >> >> Here are some diagnostic information:
> >> >> iw list:
> >> >>>
> >> >>> Wiphy phy0
> >> >>> Band 1:
> >> >>> Capabilities: 0x11ce
> >> >>> HT20/HT40
> >> >>> SM Power Save disabled
> >> >>> RX HT40 SGI
> >> >>> TX STBC
> >> >>> RX STBC 1-stream
> >> >>> Max AMSDU length: 7935 bytes
> >> >>> DSSS/CCK HT40
> >> >>> Maximum RX AMPDU length 65535 bytes (exponent:
> 0x003)
> >> >>> Minimum RX AMPDU time spacing: 8 usec (0x06)
> >> >>> HT TX/RX MCS rate indexes supported: 0-15
> >> >>> Frequencies:
> >> >>> * 2412 MHz [1] (27.0 dBm)
> >> >>> * 2417 MHz [2] (27.0 dBm)
> >> >>> * 2422 MHz [3] (27.0 dBm)
> >> >>> * 2427 MHz [4] (27.0 dBm)
> >> >>> * 2432 MHz [5] (27.0 dBm)
> >> >>> * 2437 MHz [6] (27.0 dBm)
> >> >>> * 2442 MHz [7] (27.0 dBm)
> >> >>> * 2447 MHz [8] (27.0 dBm)
> >> >>> * 2452 MHz [9] (27.0 dBm)
> >> >>> * 2457 MHz [10] (27.0 dBm)
> >> >>> * 2462 MHz [11] (27.0 dBm)
> >> >>> * 2467 MHz [12] (disabled)
> >> >>> * 2472 MHz [13] (disabled)
> >> >>> * 2484 MHz [14] (disabled)
> >> >>> Bitrates (non-HT):
> >> >>> * 1.0 Mbps
> >> >>> * 2.0 Mbps (short preamble supported)
> >> >>> * 5.5 Mbps (short preamble supported)
> >> >>> * 11.0 Mbps (short preamble supported)
> >> >>> * 6.0 Mbps
> >> >>> * 9.0 Mbps
> >> >>> * 12.0 Mbps
> >> >>> * 18.0 Mbps
> >> >>> * 24.0 Mbps
> >> >>> * 36.0 Mbps
> >> >>> * 48.0 Mbps
> >> >>> * 54.0 Mbps
> >> >>> Band 2:
> >> >>> Capabilities: 0x11ce
> >> >>> HT20/HT40
> >> >>> SM Power Save disabled
> >> >>> RX HT40 SGI
> >> >>> TX STBC
> >> >>> RX STBC 1-stream
> >> >>> Max AMSDU length: 7935 bytes
> >> >>> DSSS/CCK HT40
> >> >>> Maximum RX AMPDU length 65535 bytes (exponent:
> 0x003)
> >> >>> Minimum RX AMPDU time spacing: 8 usec (0x06)
> >> >>> HT TX/RX MCS rate indexes supported: 0-15
> >> >>> Frequencies:
> >> >>> * 5180 MHz [36] (17.0 dBm)
> >> >>> * 5200 MHz [40] (17.0 dBm)
> >> >>> * 5220 MHz [44] (17.0 dBm)
> >> >>> * 5240 MHz [48] (17.0 dBm)
> >> >>> * 5260 MHz [52] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5280 MHz [56] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5300 MHz [60] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5320 MHz [64] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5500 MHz [100] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5520 MHz [104] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5540 MHz [108] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5560 MHz [112] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5580 MHz [116] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5600 MHz [120] (disabled)
> >> >>> * 5620 MHz [124] (disabled)
> >> >>> * 5640 MHz [128] (disabled)
> >> >>> * 5660 MHz [132] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5680 MHz [136] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5700 MHz [140] (20.0 dBm) (passive
> scanning,
> >> >>> no
> >> >>> IBSS, radar detection)
> >> >>> * 5745 MHz [149] (30.0 dBm)
> >> >>> * 5765 MHz [153] (30.0 dBm)
> >> >>> * 5785 MHz [157] (30.0 dBm)
> >> >>> * 5805 MHz [161] (30.0 dBm)
> >> >>> * 5825 MHz [165] (30.0 dBm)
> >> >>> Bitrates (non-HT):
> >> >>> * 6.0 Mbps
> >> >>> * 9.0 Mbps
> >> >>> * 12.0 Mbps
> >> >>> * 18.0 Mbps
> >> >>> * 24.0 Mbps
> >> >>> * 36.0 Mbps
> >> >>> * 48.0 Mbps
> >> >>> * 54.0 Mbps
> >> >>> max # scan SSIDs: 4
> >> >>> Supported interface modes:
> >> >>> * IBSS
> >> >>> * managed
> >> >>> * AP
> >> >>> * AP/VLAN
> >> >>> * WDS
> >> >>> * monitor
> >> >>> * mesh point
> >> >>> * Unknown mode (8)
> >> >>> * Unknown mode (9)
> >> >>> Supported commands:
> >> >>> * new_interface
> >> >>> * set_interface
> >> >>> * new_key
> >> >>> * new_beacon
> >> >>> * new_station
> >> >>> * new_mpath
> >> >>> * set_mesh_params
> >> >>> * set_bss
> >> >>> * authenticate
> >> >>> * associate
> >> >>> * deauthenticate
> >> >>> * disassociate
> >> >>> * join_ibss
> >> >>> * Unknown command (68)
> >> >>> * Unknown command (55)
> >> >>> * Unknown command (57)
> >> >>> * Unknown command (59)
> >> >>> * Unknown command (67)
> >> >>> * set_wiphy_netns
> >> >>> * Unknown command (65)
> >> >>> * Unknown command (66)
> >> >>> * connect
> >> >>> * disconnect
> >> >>
> >> >> iw dev wlan0 station dump
> >> >>>
> >> >>> Station 00:1b:b1:5d:ac:3c (on wlan0)
> >> >>> inactive time: 2680 ms
> >> >>> rx bytes: 36426
> >> >>> rx packets: 934
> >> >>> tx bytes: 0
> >> >>> tx packets: 0
> >> >>> signal: -79 dBm
> >> >>> tx bitrate: 6.0 MBit/s
> >> >>>
> >> >>
> >> >> ifconfig
> >> >>>
> >> >>> eth0 Link encap:Ethernet HWaddr 00:16:76:90:49:b7
> >> >>> inet addr:10.0.0.17 Bcast:10.255.255.255 Mask:255.0.0.0
> >> >>> inet6 addr: fe80::216:76ff:fe90:49b7/64 Scope:Link
> >> >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> >>> RX packets:3416 errors:0 dropped:0 overruns:0 frame:0
> >> >>> TX packets:4606 errors:0 dropped:0 overruns:0 carrier:0
> >> >>> collisions:0 txqueuelen:1000
> >> >>> RX bytes:777960 (759.7 KiB) TX bytes:310196 (302.9 KiB)
> >> >>>
> >> >>> lo Link encap:Local Loopback
> >> >>> inet addr:127.0.0.1 Mask:255.0.0.0
> >> >>> inet6 addr: ::1/128 Scope:Host
> >> >>> UP LOOPBACK RUNNING MTU:16436 Metric:1
> >> >>> RX packets:224 errors:0 dropped:0 overruns:0 frame:0
> >> >>> TX packets:224 errors:0 dropped:0 overruns:0 carrier:0
> >> >>> collisions:0 txqueuelen:0
> >> >>> RX bytes:33981 (33.1 KiB) TX bytes:33981 (33.1 KiB)
> >> >>>
> >> >>> wlan0 Link encap:Ethernet HWaddr 00:1b:b1:5d:ae:08
> >> >>> inet addr:10.1.0.1 Bcast:10.1.255.255 Mask:255.255.0.0
> >> >>> inet6 addr: fe80::21b:b1ff:fe5d:ae08/64 Scope:Link
> >> >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> >>> RX packets:5 errors:0 dropped:0 overruns:0 frame:0
> >> >>> TX packets:128 errors:0 dropped:0 overruns:0 carrier:0
> >> >>> collisions:0 txqueuelen:1000
> >> >>> RX bytes:378 (378.0 B) TX bytes:22903 (22.3 KiB)
> >> >>
> >> >> iwconfig
> >> >>>
> >> >>> lo no wireless extensions.
> >> >>>
> >> >>> eth0 no wireless extensions.
> >> >>>
> >> >>> wlan0 IEEE 802.11abgn ESSID:"###############"
> >> >>> Mode:Ad-Hoc Frequency:5.745 GHz Cell: 5E:F8:F9:99:8C:FA
> >> >>> Tx-Power=30 dBm
> >> >>> Retry long limit:7 RTS thr:off Fragment thr:off
> >> >>> Encryption key:off
> >> >>> Power Management:on
> >> >>
> >> >> I have not enabled wpa_supplicant yet as I need to get the network
> >> >> working
> >> >> before I can start locking it down.
> >> >>
> >> >> Thanks,
> >> >> John
> >> >>
> >> >> On Thu, Jun 2, 2011 at 20:59, Gustin Johnson <gustin at meganerd.ca>
> >> >> wrote:
> >> >>>
> >> >>> 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)
> >> >>> >>
> >> >>> >>
> >> >>> >
> >> >>> >
> >> >>
> >> >
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20110603/f1d011b8/attachment.html>
More information about the Voyage-linux
mailing list