Re: [Acx100-devel] not quite working acx111

[Jim C. <jim...@gm...>]

On Mon, Apr 9, 2012 at 1:02 AM, Oliver Winker <oli...@ol...> wrote:
> On 04/08/2012 10:26 PM, Jim Cromie wrote:
>> Im trying for client ATM since its simpler.  AP later..
>
> Hmmm, wireless ATM - I never tried that ;). Modes actually tested with
> the Acx are STA, AP and ADHOC.

sorry, that was "at the moment"


As of today, the link stayed up overnite, a major step forward.
Maybe talking about it helps ;-)

I guess Ill put some traffic thru it, see how it fares
iperf probably.

then try wpa

thanks for your help


, without any traffic ho


>
> A simple hostapd.conf for WPA2 could look like this. The full (in
> /etc/...) hostapd.conf contains quite some explanations for the
> different params.
> ---
> interface=wlan[0-9]
> driver=nl80211 (would need to check one time, if that's still uptodate)
> ssid=ACXTEST
> hw_mode=g
> channel=11 (preferably something with low traffic)
> wpa=2
> wpa_passphrase=[Put-Shared-Secret-Here]
> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=CCMP
> ---

Im keeping it simple for now.
Ubuntu's widget handles it on my laptop,
so Ive never messed with wpa-supplicant.
Id like to see a reliable connection before
I go adding more variables to the equation.

But I'll look into it eventually,
thanks for that info

>
> And then you would still need a small dhcp config and bit of routing maybe.
>
>> BTW, should this convo be on -devel or -user or both ?
>
> Doesn't really matter - let's have it on devel then ;).

ack.

>> But I backed it down to WEP to simplify the problem.
>> the working wifi on box-under-test was having some trouble / unreliability
>> with WPA too.
>
> Acx driver-wise WEP or WPA(2) doesn't really make a difference
> currently, since for both crypto is currently done in SW by mac80211. So
> don't mind to try directly WPA(2) - it's just better security-wise, also
> for testing, to avoid that others checkout your wlan by accident ;).

I dont really care if someone steals my bandwidth for a week.
It'll be like putting a dollar bill on a string, and yanking as they
bend down to pick it up. :-)


I
> don't however, if it could also work for wireless ATM ... . I remember
> to have tried one time WPA on ADHOC, but that didn't pan out (maybe
> because I didn't try enough hours ...).
>
>> auto wlan0
>> iface wlan0 inet dhcp
>>       wireless-essid yoduh
>>       wireless-key ********
>>       wireless-keymode open
>>
>> iface wlan1 inet dhcp
>>       wireless-essid yoduh
>>       wireless-key *******
>>       wireless-keymode open
>
> Yep, I think that should work as STA. But I don't try the WEP modes so
> often.



>> once I ifup it, scan looks pretty good - there are differences, I
>> think theyre unimportant.
>> Signal strength is not so good, tho AP is 10 feet away :-(
>> much better (65/70) on laptop, which is also 10 feet away.
>> issue ?
>> btw, this is console output, so has kernel messages too.
>
> Yes, the signal strength is currently not yet super correlated with
> reality - gives more an idea. A thing to improve ;).

Im referring to real signal strength here -
the other card also has poor strength.
I may try moving the box right next to the router,
to get best signal possible  - or try different antennas


>
>> root@voyage:~# ifup wlan1
> [...]
>> wlan1: authenticate with 00:14:d1:e8:65:0a
>> acx: Updating TX: enable, channel=1
>> acx: Updating RX: enable, channel=1
>> acx: Updating TX: enable, channel=4
>> acx: Updating RX: enable, channel=4
>> wlan1: send auth to 00:14:d1:e8:65:0a (try 1/3)
>> wlan1: authenticated
>> wlan1: associate with 00:14:d1:e8:65:0a (try 1/3)
>> wlan1: RX AssocResp from 00:14:d1:e8:65:0a (capab=0x11 status=0 aid=3)
>> wlan1: associated
>> ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
>> acx: acx_op_set_key: algorithm=1: ACX_SEC_ALGO_WEP
>> DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 5
>> DHCPOFFER from 192.168.10.1
>> DHCPREQUEST on wlan1 to 255.255.255.255 port 67
>> DHCPACK from 192.168.10.1
>> bound to 192.168.10.141 -- renewal in 273162 seconds.
>> root@voyage:~# wlan1: no IPv6 routers present
>
> Oh, so it actually worked !? So that's good :)!
>

yes it did, for a bit.
I had to restart it while writing this,

>> It looks reasonable.
>>
>> also, FWIW, this is all from driver with my patches,
>> but master looks the same.
>
> OK
>
>> openwrt yay,  Im running bleading edge on my wrt54g now,
>> starting to hack at it too :-)
>> The router used here is a trendnet with factory firmware.
>> it is linux based.  I hope to look at putting openwrt there eventually.
>
> When you try the current OpenWRT trunk, then there might be problems
> with the AR7/Acx part right now. Compat-wireless got updated, but the
> kernel version not yet for the AR7, so that mac80211 isn't avail then.
>
> SVN trunk revision 29836 works ok for me - maybe the acx-mac80211
> version in the package Makefile still needs a small update. Just let me
> know is case you want to try.
>
> Cheers, Oliver