Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wifi Password gets corrupted after saving #384

Closed
TheHellSite opened this issue Dec 28, 2017 · 14 comments
Closed

Wifi Password gets corrupted after saving #384

TheHellSite opened this issue Dec 28, 2017 · 14 comments

Comments

@TheHellSite
Copy link

On the current AdvancedTomato build (3.5-140) for my asus rt-n18u I can't write my usual wifi password.
The following text is not my password, but it will show the bug just fine.

%WIFI$12§34$WIFI% ---> The field "wl_wpa_psk" is invalid. Please report this problem.
This password gives me the above text next to the save button and doesn't even save.

$Fr3e%1234%Fr3e$ ---> $Fr3e�34�3e$
My password only contains $ and % as special characters.
And the % char gets replaced by this strange symbol.
To reproduce the error just type any password with % or § (maybe there are more characters that are bugged) and save it. Either reload the page or click on "Basic Settings --> Network". Then click into the shared key field. It should be corrupted.
bug_1
bug_2

@Jackysi
Copy link
Owner

Jackysi commented Dec 30, 2017

Can you re-download image and re-flash it? There was some differences after 2 days of release and I didn't want to put whole new release number because I only changed the way special characters are handled. Other than that I have no idea what could it be, I have no problems.

@TheHellSite
Copy link
Author

When did you release the latest image? I downloaded the currently flashed one on the 26th dec., I think.
But I can try downloading it again.

@Jackysi
Copy link
Owner

Jackysi commented Dec 30, 2017

About a month ago. So that's probably not the case. Strange though, I tried to do that and it works fine here.

@TheHellSite
Copy link
Author

I even cleared NVRAM after installing the update.

@Jackysi
Copy link
Owner

Jackysi commented Dec 30, 2017

That has no effect on the problem though.
Can u try setting password via Shell / Telnet / SSH?

Something like "nvram set wl0_wpa_psk=password" it really depends on your router ( I don't know exact values ) and then see if it still shows wrong in GUI

@TheHellSite
Copy link
Author

TheHellSite commented Dec 30, 2017

Doesn't work either! The password gets set, but extremely cut.
"nvram set wl0_wpa_psk=%Fre3$1234$Fre3%" will give me "�e3�".
Without special characters, it works fine.
I will try telnet now.

@Jackysi
Copy link
Owner

Jackysi commented Dec 30, 2017

but did the login work via wifi? because otherwise its probably nvram limitation and can't be really fixed unless some one else does the fix. I develop gui only =)

@TheHellSite
Copy link
Author

TheHellSite commented Dec 30, 2017

So I just tried it with telnet.
"%Fre3$1234$Fre3%" gets to "%Fre3%".
I will try the 3.4-140 release now. I know you are only doing a GUI but with the 3.4 release I could set that password just fine.

@TheHellSite
Copy link
Author

TheHellSite commented Dec 30, 2017

Same bug on 3.4 release. Very strange.
I even tried different browsers and devices to set the password.
On the clients I get an authentication problem when the router has saved the corrupted password.

@VoxCodice
Copy link

The problem is that some of those special characters are used by the firmware. When you save the settings, the router basically gets a string of text in the form of URL parameters such as
wl_wpa_psk=somePassword&someOtherSetting=someOtherValue&etc
Notice that the "&" character is used to separate each setting. In this case the "&" is a special character and there are other such special characters that when you use in the password field, the router sees them as special characters.
To fix this, these characters need to be replaced with a code so that the router knows it's part of the password and not a special character. This is called encoding. For example, the "&" needs to be replaced with "%26".

I'm going to open another issue and provide a temporary solution so that you can set a password as you want.

@TheHellSite
Copy link
Author

Okay cool, thanks for pointing that out!

@TheHellSite
Copy link
Author

@Jackysi
I just tried the standard "1.28.0000 MIPSR2-140 K26 Max" build from shibby. No problems there.

@Jackysi
Copy link
Owner

Jackysi commented Feb 15, 2018

Fixed.

@mmartoccia
Copy link

Is this correction in a release yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants