This is for the following device :

Google Chrome	51.0.2704.79 (Build officiel) (32 bits)
Révision	0
Plate-forme	8172.47.0 (Official Build) stable-channel peach_pit

Tried on a different SSID (an WiFi extender to the former one) and was first unable to connect with the same out-of-range error message:

GUID	Path	Name	Type	State	Connect?	Error	Security	Tech	Activation	Roam	Frequency	Strength
-	
	6E2A44F3		FBalmp_EXT	WiFi	NotConnected		out-of-range	WPA-PSK				2457	70
{
	"Connectable": true,
	"ConnectionState": "Connected",
	"ErrorState": "out-of-range",
	"GUID": "6E2A44F3-6709-4FBB-AB56-9EEE4BE39064",
	"IPConfigs": [
		{
			"Gateway": "192.168.0.254",
			"IPAddress": "192.168.0.47",
			"NameServers": [
				"192.168.0.254"
			],
			"RoutingPrefix": 24,
			"Type": "IPv4",
			"WebProxyAutoDiscoveryUrl": ""
		}
	],
	"MacAddress": "24:F5:AA:26:3B:7B",
	"Name": "FBalmp_EXT",
	"Priority": 0,
	"SavedIPConfig": {
		"Gateway": "192.168.0.254",
		"IPAddress": "192.168.0.47",
		"NameServers": [
			"192.168.0.254"
		],
		"RoutingPrefix": 24,
		"Type": "IPv4"
	},
	"Source": "User",
	"Type": "WiFi",
	"WiFi": {
		"AllowGatewayARPPolling": true,
		"AutoConnect": true,
		"BSSID": "a0:63:91:9e:f9:d3",
		"EAP": {
			"AnonymousIdentity": "",
			"Identity": "",
			"SaveCredentials": true,
			"ServerCAPEMs": [],
			"UseProactiveKeyCaching": false,
			"UseSystemCAs": true
		},
		"Frequency": 2457,
		"FrequencyList": [
			2457
		],
		"HexSSID": "4642616C6D705F455854",
		"HiddenSSID": false,
		"RoamThreshold": 0,
		"SSID": "FBalmp_EXT",
		"Security": "WPA-PSK",
		"SignalStrength": 74
	}
}

After another try I managed to get on without changing any configuration (chromebook or routers):

2016-06-17T18:56:43.082393+02:00 INFO kernel: [ 1388.702824] mwifiex_sdio mmc1:0001:1: info: trying to associate	to 'FBalmp_EXT' bssid a0:63:91:9e:f9:d3
2016-06-17T18:56:43.137318+02:00 INFO kernel: [ 1388.759816] mwifiex_sdio mmc1:0001:1: info: associated to bssid a0:63:91:9e:f9:d3 successfully
2016-06-17T18:56:43.137356+02:00 INFO kernel: [ 1388.760137] cfg80211: Calling CRDA for country: DE
2016-06-17T18:56:43.142286+02:00 INFO kernel: [ 1388.760722] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready
2016-06-17T18:56:43.147340+02:00 INFO kernel: [ 1388.769713] cfg80211: Regulatory domain changed to country: DE
2016-06-17T18:56:43.147357+02:00 INFO kernel: [ 1388.769730] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2016-06-17T18:56:43.147364+02:00 INFO kernel: [ 1388.769742] cfg80211:   (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.147370+02:00 INFO kernel: [ 1388.769753] cfg80211:   (5150000 KHz - 5350000 KHz @ 80000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.147376+02:00 INFO kernel: [ 1388.769765] cfg80211:   (5470000 KHz - 5725000 KHz @ 80000 KHz), (N/A, 2698 mBm)
2016-06-17T18:56:43.147381+02:00 INFO kernel: [ 1388.769775] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
2016-06-17T18:56:43.149062+02:00 ERR wpa_supplicant[436]: WMM AC: Missing IEs
2016-06-17T18:56:43.477291+02:00 INFO kernel: [ 1389.098203] mwifiex_sdio mmc1:0001:1: info: successfully disconnected from a0:63:91:9e:f9:d3:	reason code 3
2016-06-17T18:56:43.477325+02:00 INFO kernel: [ 1389.098262] mwifiex_sdio mmc1:0001:1: info: successfully disconnected from 00:00:00:00:00:00:	reason code 1
2016-06-17T18:56:43.483076+02:00 INFO kernel: [ 1389.103421] cfg80211: Calling CRDA to update world regulatory domain
2016-06-17T18:56:43.489829+02:00 ERR shill[583]: [ERROR:wifi.cc(970)] Disconnected due to inability to connect to the service.
2016-06-17T18:56:43.497308+02:00 INFO kernel: [ 1389.118130] cfg80211: World regulatory domain updated:
2016-06-17T18:56:43.497328+02:00 INFO kernel: [ 1389.118146] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2016-06-17T18:56:43.497335+02:00 INFO kernel: [ 1389.118156] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.497342+02:00 INFO kernel: [ 1389.118165] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.497347+02:00 INFO kernel: [ 1389.118173] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.497353+02:00 INFO kernel: [ 1389.118182] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.497358+02:00 INFO kernel: [ 1389.118193] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.497364+02:00 INFO kernel: [ 1389.118201] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.497369+02:00 INFO kernel: [ 1389.118210] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
2016-06-17T18:56:43.497375+02:00 INFO kernel: [ 1389.118220] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)

Connecting to the original WiFi still fails.
I did try to forget the network and connect again.

Thanks for reporting! To clarify: you're consistently (100%) unable to connect to your home AP but can occasionally connect to the extender?

This should be fixed with the latest kernel patches, assigning to Wei-Ning to verify.

This is fixed in M52:

https://chromium-review.googlesource.com/#/c/348302/
https://chromium-review.googlesource.com/#/c/341295/

I've cherry-picked them to M51:
https://chromium-review.googlesource.com/354291
https://chromium-review.googlesource.com/354292

Waiting for merge approval.

+Bernie

Hmm, I am not sure whether this will meet the bar for cherry-pick into M51 given that M51 went stable on May 31.

[Automated comment] Request affecting a post-stable build (M51), manual review required.

We are seeing numerous reports on CBC concerning WiFi connection problems after the update to M51. We typically blame the router, but could there actually be a bug responsible?

Why does this happen only on home WiFi?

#CBC-RS/TC-watchlist

Some examples:
https://productforums.google.com/forum/#!topic/chromebook-central/Qocqy5AWlzs;context-place=forum/chromebook-central
https://productforums.google.com/forum/#!topic/chromebook-central/frTS2siFFj8;context-place=topicsearchin/chromebook-central/wifi%7Csort:date
https://productforums.google.com/forum/#!topic/chromebook-central/4Ux2nEM8rOk;context-place=topicsearchin/chromebook-central/wifi%7Csort:date
https://productforums.google.com/forum/#!topic/chromebook-central/wpqTQSZGrLI;context-place=topicsearchin/chromebook-central/wifi%7Csort:date

tinazh@, can you approve the M51 merging?

@Jim: I'm a TC from the Spanish Chrome Forum and we're also having a lot of reports about this :-P

It was a bug indeed, you can check out some more information about the fixes in comment #8.

Hi Shruthi,

Can you approve the M51 merging? Thanks!

This is marked as a P3, and the code changes do not look trivial to me. Could you please elaborate on impact of this issue in Stable and the risk of this change? Please note that the bar is very high for a post-stable merge. 

Would instructing the user to change from WPA to WPA2 fix the issue for them?

Is there anything that we can tell users who face this issue while waiting for the fix?

re #16, this issue affects both WPA and WPA2. This only happens to some of the APs. The user can try to switch to WEP or change an AP.

re #15, we have tested this patch on M52 and ToT on the Oak platform. I can verify that his patches fixes the WPA2 connection issue. Also, this patch is pulled from upstream thus reviewed by the upstream maintainer. I don't expect it to cause any other problems other then fixing the WPA2 issue.

There seems to be a workaround, plus does not seem very high impact. With that in mind, I would like to keep this out of M51. M52 stable should be out in a few weeks, and it looks like we already have this fix there. If you agree, please remove the merge request. 

> M52 stable should be out in a few weeks
ok let's keep it out of M51.

Issue 621796 has been merged into this issue.