Re: NWA Development and Sources?
Sorry for the late answer... I was trying some stuff... On Mar 11, 2010, at 19:22 , Nicola Mfb wrote: [...] I really like the concept of it (love it, actually) but not being able to connect to WEP secured networks is not that great. I cannot find any sources for it. Are you able to connect to your WEP network using wpa_supplicant manually? in that case NWA should work or it needs a trivial fix. I do get AppletController Cannot set network options Did not receive correct message arguments. Unaccepted options: QMap((key_mgmt, QVariant(QString, WEP) ) ( priority , QVariant(QString, 0) ) ( ssid , QVariant(QString, bishop) ) ( wep_key0 , QVariant(QString, **) ) ( wep_key1 , QVariant(QString, ) ) ( wep_key2 , QVariant(QString, ) ) ( wep_key3 , QVariant(QString, ) ) ( wep_tx_keyidx , QVariant(QString, 0) ) ) AppletController cannot add network QVariant(QString, GWN) QVariant(, ) Thats a dbus error reply from wpa_supplicant. Just guessing (I cannot check now) try to remove empty wep keys from .nwa.conf, or in general remove from it pair values in Unaccepted options that are not present in your wpa_supplicant.conf. Ok, I tried the following: 1. Removed the attributes wep_key1, wep_key2 and wep_key3 in .nwa.conf 2. Set the attributes wep_key1, wep_key2 and wep_key3 to the same value as wep_key0 in .nwa.conf 3. Moved my /etc/wpa_supplicant/wpa_supplicant.conf out of the way None of these, unfortunately, did make any difference. Could it maybe be because I give the key as a hex string (26 characters)? Do I have to prefix it with something to indicate it's a hex string? (I tried 0x... but that didn't work either) Btw, is there *any* documentation on the dbus interface of wpa supplicant? The only thing I could find was this statement: The wpa_supplicant dbus interface isn't particularly well documented [...] [...] I do actually have problems with the ar6000 driver if I do *not* blacklist it (in /etc/modprobe.d/blacklist). I do see kernel panics in the syslog and Wifi usually does not work (fsoraw fails to aquire the WiFi resource and I don't get the eth0 interface). I *seem* to have less problems if I load the driver later manually. I am running andy-tracking 3db70757d6fabb17 with my own config (DEBUG options disabled) but I have the same results with the current kernel from SHR-U. Is that aforementioned patch included? Not yet. Paul's patch did make a big difference in the stability of the driver, however, I also needed Hm, blacklisting didn't help. The driver stopped working for me later that day. It seems that Paul's patch made the driver more stable once it's working (have yet to see a PANIC). The problem that I encountered with the ar6000 driver seems to be described here: http://docs.openmoko.org/trac/ticket/2327 and when I added the suggested patch the driver loaded pretty well. Dirk Niko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
NWA Development and Sources?
Hi all, Does anybody know if NWA is still being developed? According to the page on the OpenMoko Wiki (http://wiki.openmoko.org/wiki/NWA) it seems that it was more like a proof of concept. Was it replaced by something else? I really like the concept of it (love it, actually) but not being able to connect to WEP secured networks is not that great. I cannot find any sources for it. The Subversion host mentioned in the binary package (svn://svn.noko.dnsalias.org/;module=nwa;proto=https) seems to be non-existant (I don't get a reply from svn.noko.dnsalias.org) and the homepage http://sourceforge.net/apps/mediawiki/noko/index.php?title=Main_Page (if that's the one) doesn't mention nwa at all. Thanks for any pointers, Dirk ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: NWA Development and Sources?
On Thu, Mar 11, 2010 at 10:14 PM, D. Gassen dirk.gas...@web.de wrote: Hi all, Does anybody know if NWA is still being developed? According to the page on the OpenMoko Wiki (http://wiki.openmoko.org/wiki/NWA) it seems that it was more like a proof of concept. Yes, it was born to make brainstorming, that's the reason sources were not released. Anyway I got no partecipation in that nor in wiki Discussion Board in several months, I guess becouse it's QT based. Developing was stopped due to lack of interest and kernel problems, but now Paul Ferster patched ar6000 module, and Ben reported that NWA now seems to be rock solid. Please try the patch and report on trac any issues, this should accelerate the upstream landing. NWA is now one of the neophysis wifi manager candidate, so I'm going in the next weeks to improve and clean it and finally release sources, so please be patient. Was it replaced by something else? I really like the concept of it (love it, actually) but not being able to connect to WEP secured networks is not that great. I cannot find any sources for it. Are you able to connect to your WEP network using wpa_supplicant manually? in that case NWA should work or it needs a trivial fix. Niko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: NWA Development and Sources?
On Mar 11, 2010, at 17:11 , Nicola Mfb wrote: On Thu, Mar 11, 2010 at 10:14 PM, D. Gassen dirk.gas...@web.de wrote: Hi all, Does anybody know if NWA is still being developed? According to the page on the OpenMoko Wiki (http://wiki.openmoko.org/wiki/NWA) it seems that it was more like a proof of concept. Yes, it was born to make brainstorming, that's the reason sources were not released. Anyway I got no partecipation in that nor in wiki Discussion Board in several months, I guess becouse it's QT based. Developing was stopped due to lack of interest and kernel problems, but now Paul Ferster patched ar6000 module, and Ben reported that NWA now seems to be rock solid. Please try the patch and report on trac any issues, this should accelerate the upstream landing. Do you have a URL handy by any chance? NWA is now one of the neophysis wifi manager candidate, so I'm going in the next weeks to improve and clean it and finally release sources, so please be patient. Was it replaced by something else? I really like the concept of it (love it, actually) but not being able to connect to WEP secured networks is not that great. I cannot find any sources for it. Are you able to connect to your WEP network using wpa_supplicant manually? in that case NWA should work or it needs a trivial fix. I do get AppletController Cannot set network options Did not receive correct message arguments. Unaccepted options: QMap((key_mgmt, QVariant(QString, WEP) ) ( priority , QVariant(QString, 0) ) ( ssid , QVariant(QString, bishop) ) ( wep_key0 , QVariant(QString, **) ) ( wep_key1 , QVariant(QString, ) ) ( wep_key2 , QVariant(QString, ) ) ( wep_key3 , QVariant(QString, ) ) ( wep_tx_keyidx , QVariant(QString, 0) ) ) AppletController cannot add network QVariant(QString, GWN) QVariant(, ) for both WEP networks that I have defined in .nwa.conf. However, this might be caused by the middleware since today for one time only nwa *was* able to associated with bishop. The WPA-PSK network at home works flawlessly. I have the same networks configured in /etc/wpa_supplicant/wpa_supplicant.conf and I can associate with the WEP networks without problems: r...@freerunner:~# fsoraw -r WiFi -- /usr/sbin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -ieth0 ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported CTRL-EVENT-SCAN-RESULTS Trying to associate with 00:19:aa:14:d9:60 (SSID='bishop' freq=2452 MHz) ioctl[SIOCSIWENCODEEXT]: Operation not supported Associated with 00:19:aa:14:d9:60 CTRL-EVENT-CONNECTED - Connection to 00:19:aa:14:d9:60 completed (auth) [id=3 id_str=] I do actually have problems with the ar6000 driver if I do *not* blacklist it (in /etc/modprobe.d/blacklist). I do see kernel panics in the syslog and Wifi usually does not work (fsoraw fails to aquire the WiFi resource and I don't get the eth0 interface). I *seem* to have less problems if I load the driver later manually. I am running andy-tracking 3db70757d6fabb17 with my own config (DEBUG options disabled) but I have the same results with the current kernel from SHR-U. Is that aforementioned patch included? Dirk Niko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: NWA Development and Sources?
On Fri, Mar 12, 2010 at 12:56 AM, D. Gassen dirk.gas...@web.de wrote: [...] now seems to be rock solid. Please try the patch and report on trac any issues, this should accelerate the upstream landing. Do you have a URL handy by any chance? It's on openmoko trac: https://docs.openmoko.org/trac/attachment/ticket/2333/0001-ar6000-minimise-possibility-of-race-in-ar6000_ioctl_.patch [...] I really like the concept of it (love it, actually) but not being able to connect to WEP secured networks is not that great. I cannot find any sources for it. Are you able to connect to your WEP network using wpa_supplicant manually? in that case NWA should work or it needs a trivial fix. I do get AppletController Cannot set network options Did not receive correct message arguments. Unaccepted options: QMap((key_mgmt, QVariant(QString, WEP) ) ( priority , QVariant(QString, 0) ) ( ssid , QVariant(QString, bishop) ) ( wep_key0 , QVariant(QString, **) ) ( wep_key1 , QVariant(QString, ) ) ( wep_key2 , QVariant(QString, ) ) ( wep_key3 , QVariant(QString, ) ) ( wep_tx_keyidx , QVariant(QString, 0) ) ) AppletController cannot add network QVariant(QString, GWN) QVariant(, ) Thats a dbus error reply from wpa_supplicant. Just guessing (I cannot check now) try to remove empty wep keys from .nwa.conf, or in general remove from it pair values in Unaccepted options that are not present in your wpa_supplicant.conf. [...] I do actually have problems with the ar6000 driver if I do *not* blacklist it (in /etc/modprobe.d/blacklist). I do see kernel panics in the syslog and Wifi usually does not work (fsoraw fails to aquire the WiFi resource and I don't get the eth0 interface). I *seem* to have less problems if I load the driver later manually. I am running andy-tracking 3db70757d6fabb17 with my own config (DEBUG options disabled) but I have the same results with the current kernel from SHR-U. Is that aforementioned patch included? Not yet. Niko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
