moOde 5.0 RC1 In-Place Update

[Tim Curtis]

@JohnM73 - You might want to check your Router's WiFi logs to see if there are any errors from MAC address of the Pi thats trying to associate. Also make triple sure the SSID and password are correct. 

On moOde you can verify that the correct wireless regulatory domain is being used via the cmd below

Code:

iw reg get

Here is an example from one of my systems

Code:

pi@rp3:~ $ iw reg get
global
country US: DFS-FCC
       (2402 - 2472 @ 40), (N/A, 30), (N/A)
       (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
       (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
       (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
       (5735 - 5835 @ 80), (N/A, 30), (N/A)
       (57240 - 71000 @ 2160), (N/A, 40), (N/A)

And here is the wireless config

Code:

pi@rp3:~ $ iwconfig
wlan0     IEEE 802.11  ESSID:"AirnetN5"  
         Mode:Managed  Frequency:5.745 GHz  Access Point: 60:A4:4C:29:FA:D4  
         Bit Rate=150 Mb/s   Tx-Power=31 dBm  
         Retry short limit:7   RTS thr:off   Fragment thr:off
         Power Management:on
         Link Quality=49/70  Signal level=-61 dBm  
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.