Re: [PATCH] WFA certification with connman
On Wed, 2015-06-24 at 20:25 -0700, James Zipperer wrote: > My problem was related to connman using wpa_supplicant in wext mode instead > of nl80211. No patching required! Actually, now that nl80211 works for you, you probably should disable wext support from the kernel(s) to avoid these kind of nasty surprises in the future. Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: [PATCH] WFA certification with connman
On Wed, 2015-06-24 at 20:25 -0700, James Zipperer wrote: > My problem was related to connman using wpa_supplicant in wext mode instead > of nl80211. No patching required! > > Wext mode resulted in a WPA AP being selected if it had a higher signal > strength than a WPA2 AP with the same ssid. nl80211 mode selects WPA2 > regardless. Thanks for testing and documenting the result on the mailing list! Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: [PATCH] WFA certification with connman
My problem was related to connman using wpa_supplicant in wext mode instead of nl80211. No patching required! Wext mode resulted in a WPA AP being selected if it had a higher signal strength than a WPA2 AP with the same ssid. nl80211 mode selects WPA2 regardless. On Wed, Jun 24, 2015 at 3:08 PM, James Zipperer wrote: > Actually, my patch doesn't seem to work. > > The problem does seem related to how connman is controlling > wpa_supplicant. If I use wpa_cli instead of connman, it seems to make the > right decision about which network to connect to. > > Any ideas why using connman would result in choosing the WPA network over > the WPA2 network? > > Thanks! > > > > On Tue, Jun 23, 2015 at 10:30 PM, James Zipperer < > james.zippe...@synapse.com> wrote: > >> I think this may solve the problem I am seeing with WFA certification. >> Please let me know if this is the right way to solve it. In the case where >> both RSN and WPA are available, prefer RSN over WPA. >> >> Thanks! >> >> -- >> >> *James Zipperer* >> Software Engineer >> Synapse Product Development >> >> mail 1511 6th Ave Suite 400, Seattle, WA 98101 >> direct 206-832-1269,3614 | office 206-381-0898 | mobile 206-399-6228 >> james.zippe...@synapse.com | http://www.synapse.com >> >> This email and any files transmitted with it are confidential. >> Unauthorized publication, use or dissemination of this email is prohibited. >> Please consider the environment before printing. >> > > > > -- > > *James Zipperer* > Software Engineer > Synapse Product Development > > mail 1511 6th Ave Suite 400, Seattle, WA 98101 > direct 206-832-1269,3614 | office 206-381-0898 | mobile 206-399-6228 > james.zippe...@synapse.com | http://www.synapse.com > > This email and any files transmitted with it are confidential. > Unauthorized publication, use or dissemination of this email is prohibited. > Please consider the environment before printing. > -- *James Zipperer* Software Engineer Synapse Product Development mail 1511 6th Ave Suite 400, Seattle, WA 98101 direct 206-832-1269,3614 | office 206-381-0898 | mobile 206-399-6228 james.zippe...@synapse.com | http://www.synapse.com This email and any files transmitted with it are confidential. Unauthorized publication, use or dissemination of this email is prohibited. Please consider the environment before printing. ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: [PATCH] WFA certification with connman
Actually, my patch doesn't seem to work. The problem does seem related to how connman is controlling wpa_supplicant. If I use wpa_cli instead of connman, it seems to make the right decision about which network to connect to. Any ideas why using connman would result in choosing the WPA network over the WPA2 network? Thanks! On Tue, Jun 23, 2015 at 10:30 PM, James Zipperer wrote: > I think this may solve the problem I am seeing with WFA certification. > Please let me know if this is the right way to solve it. In the case where > both RSN and WPA are available, prefer RSN over WPA. > > Thanks! > > -- > > *James Zipperer* > Software Engineer > Synapse Product Development > > mail 1511 6th Ave Suite 400, Seattle, WA 98101 > direct 206-832-1269,3614 | office 206-381-0898 | mobile 206-399-6228 > james.zippe...@synapse.com | http://www.synapse.com > > This email and any files transmitted with it are confidential. > Unauthorized publication, use or dissemination of this email is prohibited. > Please consider the environment before printing. > -- *James Zipperer* Software Engineer Synapse Product Development mail 1511 6th Ave Suite 400, Seattle, WA 98101 direct 206-832-1269,3614 | office 206-381-0898 | mobile 206-399-6228 james.zippe...@synapse.com | http://www.synapse.com This email and any files transmitted with it are confidential. Unauthorized publication, use or dissemination of this email is prohibited. Please consider the environment before printing. ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
[PATCH] WFA certification with connman
I think this may solve the problem I am seeing with WFA certification. Please let me know if this is the right way to solve it. In the case where both RSN and WPA are available, prefer RSN over WPA. Thanks! -- *James Zipperer* Software Engineer Synapse Product Development mail 1511 6th Ave Suite 400, Seattle, WA 98101 direct 206-832-1269,3614 | office 206-381-0898 | mobile 206-399-6228 james.zippe...@synapse.com | http://www.synapse.com This email and any files transmitted with it are confidential. Unauthorized publication, use or dissemination of this email is prohibited. Please consider the environment before printing. prefer-wpa2.patch Description: Binary data ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
WFA certification with connman
Has anybody passed WFA certification with connman? I'm seeing some tests fail that I would expect to "just work". For instance: choosing to connect to an access point with WPA2-encryption over choosing to connect an access point with the same ssid that has WPA-encryption. connman appears to group those ssids into a single service ex. "wifi_xx_managed_psk", with no differentiation between the WPA network and WPA2 network presented to the user. Is it connman's responsibility to choose the WPA2 network over the WPA network? Or is it wpa_supplicant's resposibility? Or maybe the wifi kernel module? If it is connman's responsibility, how does it make the choice? It would be helpful to know which software package is responsible for making that choice. Thanks! -- *James Zipperer* Software Engineer Synapse Product Development mail 1511 6th Ave Suite 400, Seattle, WA 98101 direct 206-832-1269,3614 | office 206-381-0898 | mobile 206-399-6228 james.zippe...@synapse.com | http://www.synapse.com This email and any files transmitted with it are confidential. Unauthorized publication, use or dissemination of this email is prohibited. Please consider the environment before printing. ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
