Hey guys.
Usually i set my SSID using underscore like "WiFi_2.4G". I've set this via WEB UI
i tried to set my SSID using space like "WiFi 2.4G", and it appears nothing wrong with my device's Wi-Fi list.
Whenever i save this again without any differences, not even with changing SSID, i can see SSID is changed to "WiFi 2.4G 2.4G" at my device's Wi-Fi list. It shows "WiFi 2.4G" at my WEB UI's settings. it just shows "WiFi 2.4G 2.4G" at my device's Wi-Fi list.
So i changed SSID to "test" via WEB UI, and it shows "test 2.4G 2.4G" at my device's Wi-Fi list.
To fix this, i need to reset my router
If i am right, somehow my router "memorize" string after the first space, and keep pastes this at my new SSID.
Any ideas to solve this Problem? i already checked uci commands at my SDK and still i have no idea why is this happening.
No, it very obviously isn't. It's a vendor firmware based on Mediatek's proprietary SDK, which -while loosely based on LEDE 17.01- has ripped out essential parts (especially related to kernel, wireless drivers, configuration backend, etc.) and replaced them with their proprietary components. With this, all bets are off, and unless you can reproduce the issue with real (and contemporary) OpenWrt, there's nothing to talk about here, maybe it applies, maybe it doesn't, we don't know - and we can't help you with that anyways.
You probably should be looking at upgrading to something more recent. That is really old and there are bugs and security vulnerabilities that are fixed in later versions.
I got a SDK from Mediatek and i use this to develop, debug Routers, so i cannot say which hardware i am using currently. version is Reboot(17.01). I know this one is old version but i cannot upgrade to latest version since it's not 100% my project.
Are there any more things that i need to tell you guys? @slh@psherman
You'll be hard pressed to find anyone who really remembers the nuances of LEDE configuration. A lot has changed in the past 4 years... the way the firmware worked then is considerably different than how it works now.
your SDK is not vanilla LEDE, and therefore the customizations introduce differences in the capabilities and configuration methods. It also has the potential to introduce bugs that did not exist in the official LEDE releases.
Combining the two, there is really no way to get help here. You should ask MediaTek for assistance with your issue since they provided the SDK. If you are working on a current project, they should have field applications engineers who can help you debug the issue and move forward/