WiFi passwords containing a $ sign doesn't since FW 5.8.1 #151
Comments
|
Can you please post the log, especially the part that covers the save and read of the config file. Also I am a bit confused what you mean with “VLAN”, guess that should be WLAN right? |
|
Nope VLAN. I've multiple strictly isolated WLAN SSIDs. Each SSID has it's own (untagged) VLAN and a own IP Subnet. I used the SSID "JBLM" with the IP Subnet 10.10.10.0/24 and the PSK with a $ sign since the iSpindle firmware 1.x. Afterwards I entered the config-mode and coosed another of my SSIDs (JBLM-IOT-PLAYGROUND), with a PSK without $ signs and a separate IP Subnet. Back in Config Mode I tried to go back to the JBLM SSID: parsed config: ▒l▒ calling Ubidots POST /api/v1.6/devices/J2?token=myToken HTTP/1.1 HTTP/1.1 200 OK 8d Final-sleep: 900s; RT:5349 As you can see: Same behavior on 5 iSpindles after upgrading them to 5.8.1 or 5.8.2. |
|
So IEEE 802.11 has no concept of VLANs by itself, that is logically analogous to WiFi SSIDs what you are referring to. Now, what you are to know is that the Esp8266 has a special register to hold the last WiFi credentials that are automagically loaded on boot up hence connecting if possible. This is actually used to again a extremely fast connection after sleep interval. And in the log there is a message posted if these register are resetted or invalidated for new credentials. Now if this very refresh does not succeed therefore the old credentials are still existing in the register and will cause a reconnect to the old SSID. Now it would be interesting to see what and why the credentials are not updated. Unfortunately with your scrambled logs I can’t determine really what’s going on there... |
|
I scrambled just the passwords and tokens :-) I learned: the iSpindle reboots after saving, because it has working wifi credentials of another SSID in the CMOS. The configured SSID "JBLM" and the PSK "$$MyPassword123" is correct. The iSpindle worked with this credentials before upgrading and other devices are still able to connect. Nothing has changed, except the new firmware. *WM: Sent wifi save page |
|
The question is if the password phrase was correctly received from the html form into the config file and can be read again correctly. Thats why I was questioning your scrambled secret if it really reflects the conditions. Please double check if this is the case. If so, then the error must be in the never SDK. |
|
I think it's an HTML encoding issue. Unfortunately the behavior isn't consistent. A spindle, that has just seen the SSID "JBLM" (with the $ sign PSK) is showing %24 instead of the $ in the PSK field, after loading the config. There's no reboot after saving but the iSpindel AP desappears and the config-flasing keeps alive. A spindle, that was once connected to the SSID "JBLM-IOT-PLAYGROUND" (without the $ sign PSK) works fine. If I turn again into the config-mode and go back to the SSID "JBLM" and enter the "$ sign PSK" the iSpindle does a reboot after saving, sending data and so on. Everything looks fine, but the spindle uses secretly the priorly configured SSID "JBLM-IOT-PLAYGROUND". I doublechecked this. Unfortunately I'm unable to investigate the 1st case deeper, because all of my ispindles were already connected to the 2nd SSID in the meantime. |
|
Maybe this worx? |
|
I double checked and I am sure this is not a Firmware issue. The special character |
|
Did you compile yourself? |
|
No, it's the official firmware from the repo. |
|
Just tested, and it does not appear in my test setup. |
|
The prior log was a try to go back to an older firmware that worked with that spindle and my WiFi. Here's a fully unscrambled log for a try to change the SSID back to "JBLM". 1st save -> Reboot because of backup cedentials If you cant see anything close this issue. I planned to change my WiFi PSK next time. ------------- 5.8.2 ---------------- d`gr▒▒▒n ▒l{▒▒g POST /api/v1.6/devices/J2?token=A1E-ToKeN123 HTTP/1.1 POST /api/v1.6/devices/J2?token=A1E-ToKeN123 HTTP/1.1 Final-sleep: 900s; RT:5168 ▒d▒ ▒l{▒▒g sllܞ|▒l▒| parsed config: ▒ ▒d▒ {"Name":"J2","Token":"A1E-ToKeN123","Sleep":900,"Server":"","API":0,"Port":80,"URL":"","Vfact":191.8,"SSID":"JBLM","PSK":"$$password123","POLY":"","aX":0,"aY":0,"aZ":0} l▒b|▒▒▒s▒c▒ sdl▒▒|▒d▒|▒ Parse error at 1 Parse error at 1 {dd▒▒|▒d▒| Parse error at 1 |
Very strange behavior.
When the WiFi PAS contains a double $ sign and you save the config, then the iSpindle stops the iSpinled hotspot but doesn't reboot and endless continues the "config-mode flashing" (without reboot).
*WM: Sent wifi save page
*WM: Connecting to new AP
*WM: Connecting wifi with new parameters...
*WM: previous settings invalidated
*WM: After waiting...
After a manual reset the iSpindle can't connect to the WLAN.
When you reenter the config mode each $ # the PSK was replaced with "%24".
The strange thing is: If I connect to another SSID (another VLAN), where the PSK doesn't contain a $ sign (WiFI works) and you reenter the config mode, go back to the 1st SSID, then the 1st SSID and the correct PSK is show in the config, but the 2nd SSID and the matching PSK is used in background for the still working WiFi connection. Even there's no trace entry "using rescue credentials" th this case. The trace is showing PSK und SSID from the 1st WLAN ($ sign PSK) but the iSpindle gets an IP fron the 2nd SSIDs VLAN.
The text was updated successfully, but these errors were encountered: