Skip to content

Instantly share code, notes, and snippets.

@joar
Last active Mar 21, 2022
Embed
What would you like to do?
Using unicode in your SSID on ASUS RT-AC66U, in ASUSWRT

Using unicode in your SSID on ASUS RT-AC66U

!DANGER!

This might void your warranty. Do it on your own risk.

I'm using the 🐟 emoji character as my SSID, because I like to be special.

How I do it

Open the Wireless admin page in Chrome or Chromium.

  1. Enter your unicode SSID in the ASUSWRT admin.

  2. Open Chrome Dev Tools (CTRL+SHIF+I, I as in Inspector).

  3. Put your cursor in the Console panel of Chrome Dev Tools.

  4. Paste

    validator.stringSSID = function () {
        console.log('fake stringSSID', arguments);
        return true;
    };

    in your console and press ENTER. This will override the JavaScript function in ASUSWRT that rejects unicode characters.

  5. Press the Apply button in ASUSWRT. The network should be saved without problems.

Potential issues

In the latest firmware from ASUS, the unicode SSID is decoded incorrectly. This makes the left panel in ASUSWRT disappear. There are two solutions:

  • Go to http://router.asus.com/Advanced_Wireless_Content.asp and change the SSID back to a non-unicode SSID.
  • OR Install ASUSWRT-MERLIN.

For those that like digging

  1. Open the Chrome Dev Tools (CTRL+SHIF+I, I as in Inspector).

  2. Press CTRL+SHIFT+F, this should open a search input.

  3. Enter applyRule in the search input. There should be two results

    242 function applyRule(){
    803 <input type="button" id="applyButton" class="button_gen" value="Apply" onclick="applyRule();">
    
  4. Click on function applyRule(){. This will open Advanced Wireless_Content.asp in the Dev Tools main panel.

  5. Press CTRL+F and enter stringSSID. This will show you the call to the function that rejects Unicode characters.

@notflip
Copy link

notflip commented May 1, 2019

Working on RT-AC51U!

@idlpar
Copy link

idlpar commented Mar 21, 2022

Thanks
Worked Perfectly with ASUS RT-N12+

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