Closed jheretic closed 10 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Here's some more background information on the problem, which I realized I never formally captured anywhere:
Whether or not IBSS-RSN is supported on a given piece of hardware is primarily a function of a (a) the wireless driver in use and (b) the version of wpasupplicant installed on the machine, which must be both greater than 1.0 and have been compiled with the IBSS_RSN=y flag set. More details:
A) We have information about driver compatibility in various places in our installation instructions; I'm not sure there's much more we can do about that side of things at this point.
B) With regard to wpasupplicant, we have somewhat more control. A custom-compiled version of wpa_supplicant with the correct compile flag set is provided by commotion_wpa_supplicant for those OSes whose default package is out of date. Additionally, we have just reopened an old bug in Debian testing that will hopefully result in the IBSS_RSN=y flag being included in all future versions of the package. (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678147).
Finally, versions of Ubuntu => 13.04 have working versions of wpasupplicant out-of-the-box.
Jordan McCarthy Open Technology Institute | New America Foundation Public Key: 0xC08D8042 | 4A61 3D39 4125 127D 65EA DDC2 BFBD A2E9 C08D 8042
On 10/11/2013 02:11 PM, Josh King wrote:
We need to support IBSS-RSN. This is more about facilitating upstream support than anything we need to implement in our own software.
— Reply to this email directly or view it on GitHub https://github.com/opentechinstitute/commotion-linux-py/issues/5.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJSWEZyAAoJEL+9ounAjYBCCWUH/jhsKj3Nx6BcEk5tsvGW9xk1 pnkO3TkVCIyOshMkvfrsb0Mr3aWn6WNs6Zmb4qEQIQq0eLfBK6LMAkaCYRxXEEC8 kPJBPTQXAqwZYvjuRvT4wPLVuVHctfFsoxT3wAmDhcTh+ylvBTzzYlUu7WZb1xtg jztfC2mVlQZDxq19SLPjurkR0yenzw0fgsEqwSL7AdYKevYvajLSUpDmrv7PqB8E WMu+JwBprJPRMmkhwQY5GWOj3lXjdZhu4AawZSkSdRf+YZPWJIoCxcH4lNzo3/IZ tLblsAVAz+/oqXMK75ELvioOfJ6siqR+oOWlfqm+QJIVUX3FcJn4TogfXQtgAG8= =HF6Z -----END PGP SIGNATURE-----
Cool. I knew this was partly addressed, I mostly just wanted a place where we could make the status clear. I agree we have no influence over point A except for documentation. I'll leave this open pending news on that Debian bug from point B, other than that I see it primarily as a means of having clear requirements documentation. Thanks!
@technosopher @natmey Can this issue be closed out? Nothing that the pull request was tested and branch merged. I do recall mention last week of upstream support for IBSS-RSN. Is that right?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
This is an ongoing issue, which we'll have to periodically revisit as drivers and parts of the network manager stack are updated. So we can close it to indicate that a prototype implementation is in fact working, but we'll be working on various aspects of IBSS_RSN for a while to come.
Jordan McCarthy Open Technology Institute | New America Foundation Public Key: 0xC08D8042 | 4A61 3D39 4125 127D 65EA DDC2 BFBD A2E9 C08D 8042
On 12/09/2013 10:19 AM, critzo wrote:
@technosopher https://github.com/technosopher @natmey https://github.com/natmey Can this issue be closed out? Nothing that the pull request was tested and branch merged. I do recall mention last week of upstream support for IBSS-RSN. Is that right?
— Reply to this email directly or view it on GitHub https://github.com/opentechinstitute/commotion-linux-py/issues/5#issuecomment-30139943.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJSpeNuAAoJEL+9ounAjYBC0fUIAK9r3bT3WnoULPNTyiDdegfy bZPRaWf5jORZvj4P0wSEwq6Hi0pB0UF9nLyNkaYWr57PALHXm0ISV+7SH5N2bS/q MVanknLCjrq8G5KAGD5U/IrzAwUS+EEqUU964H+FfwCULFhsxK5nvPzD9cd4oV5/ TnujdhL+AvNYFFTwTm5gLid2liigoMKhWP6QdD81iNhUbSto1nLIXqtKw/+WdbD2 gX5+eHaCeBz09uQ3VXAbNAx9KWQxAOEz7J4sfgDppxioXTordtZuG0Q9m2g+js0f sI6HvK6nbaDWgXqGNdXh4vDLBujiQLFwOm2Z1kP5jNN+C0lZsaiZ8JdDt95Gf8c= =0C1i -----END PGP SIGNATURE-----
We need to support IBSS-RSN. This is more about facilitating upstream support than anything we need to implement in our own software.