Issues with setting WPA key on Zyxel NR5103E router

[EDIflyer]

Hi

Firmware V1.00(ACBJ.0)b12

I'm trying to setup the WiFi network on my new NR5103E. I have an existing (long!) WPA key that I wish to use and is already entered on multiple devices from my previous router setup. Some of these devices don't support special characters however the web UI interface blocks entries that don't conform to a pre-defined spec - this is despite the default random password that comes with the router (and is generated if you select 'random password') doesn't conforming with that same spec either!! In addition I found an interesting bug in that the UI script as currently written doesn't seem to properly check the passwords anyway (see screenshot below where what to me looks like a compliant password isn't accepted).

I read on ISPreview.co.uk about the potential to use SSH access to change things manually and have found that if I split 2.4GHz and 5GHz networks I can manually change the 5GHz password via SSH (and existing devices then connect fine), however I always get an error when trying to change 2.4GHz one (see screenshot below - top two lines also show me building the command with the ? function and it being valid). 

So I guess 2 questions (paging @JonathanB 😉😞

1. can the firmware please be fixed to allow customers to set their own passwords (after getting them to agree to a disclaimer if necessary!) without having to conform to the mandatory special character + number + uppercase + lowercase rule and
2. in the short term does anyone know why the 2.4GHz SSH command isn't working when the basically identical 5GHz one works?

I've also found if you combine 2.4GHz and 5GHz bands and manually change the 5GHz via SSH it says 'command successful' but actually doesn't change it.

The additional security from special characters is questionable and quite a few IoT devices have issues with it (presumably why the built-in default password doesn't use them either!) so I'd be really keen to have this fixed.

Thanks 😀

SSH commandscharacter restrictions that haven't been applied to default password

[HowieB]

Hi,

How do I get to this point?  I'm in the web interface but can't see anything like this.

Thanks

Howard 

[EDIflyer]

I've you're meaning my console screenshots that was via SSH into the router.

[HowieB]

Sorry, I meant to reply to how to alter name.js so I can avoid special chars in WiFi password 

[EDIflyer]

Ah OK, I'm afraid I didn't do that bit 🙂

[HenryL]

I'm an idiot, needs to be

t= 'ruleMeetingComplexPassword!11'

[HowieB]

Hi,

J

This is exactly what I need.  How do you see name.js to add this line?

Thanks

[HenryL]

This is the error I'm seeing: 

Any ideas?!

[HenryL]

@Hello1024 I can't seem to get your workaround to function for me. I can get the break point to pause using but I get an error when I enter t= 'ruleMeetingComplexPassword!11" into the console and hit enter - am I doing something wrong?

[Hello1024]

It is possible to bypass the password complexity checks in the WebUI by using the web inspector, the sources tab, app.js file, search for "checkPasswordStrenth:", put a breakpoint on the line below that, then whenever that breakpoint is hit, put the following into the console:

t= 'ruleMeetingComplexPassword!11"

and click continue.

This will let you bypass the warning and set any password you like.