[Release 380] Asuswrt-Merlin 380.69 is now available

[RMerlin]

More information regarding this problem.... I can't get the client 1 On/Off button to work, it gets stuck in applying setting and goes no where... No OpenVPN messages in syslog.... I did a factory reset and same result. Different browsers with same result.

But if I setup the client VPN in Client 2, then the On/Off button works as advertised....

Something is not right here....

Open the browser console and look for any Javascript error. I bet you have quotes or other invalid characters configured on that page.

 

[MXM]

Open the browser console and look for any Javascript error. I bet you have quotes or other invalid characters configured on that page.

{command: "rec_getSettings", data: {…}}
Advanced_OpenVPNClient_Content.asp:1 This page includes a password or credit card input in a non-secure context. A warning has been added to the URL bar.

mn.js:24 {command: "rec_getSettings", data: {…}}
mn.js:24 {command: "rec_getSettings", data: {…}}
2Advanced_OpenVPNClient_Content.asp:465 Uncaught TypeError: validator.ipv4_addr is not a function
at validForm (Advanced_OpenVPNClient_Content.asp:465)
at applyRule (Advanced_OpenVPNClient_Content.asp:480)
at HTMLInputElement.onclick (Advanced_OpenVPNClient_Content.asp:1317)



Here's what I got from the Browser Console.... Does it help pinpoint the problem?

Thanks.

 

[tsunami2311]

Updated from 380.67 to 380.69_2

Did my usual Factory default, Flash, Factory default
And reset everything up from scratch all looks good atm, Only thing strange that stands out is my 200mbit isnt hitting 200mbit on wired devices , but seeing we have snow storm and shirt ton of now, I gona assume its not the router and the isp atm. I will keep an eye on it for time being. If it still only 120 of 200mbit after it all cleared up I will do test direct from the modem to pc.

 

[tsunami2311]

I did notice another odd thing, There are 2 that are listed in mac address allow with there appropriate names, But when I set bandwidth limit to those device it just show the name as it mac address. instead of is wifi name.

*edit*

Ok i fiqure out the cause of this. IF all cap re used in the Mac address allow exmaple
Mac address allow uses
E4:A3:3E:2D:66:BC

Bandwitdth limiter must use
E4:A3:3E:2D:66:BC

to see name correct.
if
e4:a3:3e:2d:66:bc
is used it just displays a mac address

 

[tsunami2311]

All looks good wired is still getting 200/35mbit it should be. 2hz still get max of 100mbit and 5ghz still get 200mbit depending on range and distance to the device.

Wifi looks stable it only been 28 hours though, but it wifi so i use to it randomly droping and coming back. Reboot on schedule works. and DDNS works so does DNS filters.

 

[JoaoAntonio]

The "Apply" Button of OpenVPN Settings is not working for me. Does anyone else have the same issue?

 

[M@rco]

Asus says it can take up to a day before the correction on their side gets fully propagated.

Apparently folks at Asus HQ have already joined the pre-party for the Lunar New Year, as 5 days have gone by and it stills says:

Signature Version    : 1.110
Signature is up to date

Am I missing something spectacular now?

 

[Marsi4eg]

Re-updated my AC66U to 380.69_2 to test openvpn client1 page in console browser.

So it directs me to

TypeError: validator.ipv4_addr is not a function  Advanced_OpenVPNClient_Content.asp:465:53

and exactly to this string:

if ((addrobj.value != "") && (alert_str != "") && (!validator.ipv4_addr(addrobj.value))) {

I am very sure that I have no any single or double quotes in every field and of course I have no quotes in server address field.

Not working Apply button also directs to the same string in console.

I fully understand that you're all in newer releases (380+) but could you just hide this glitchy 380.69_2 for models that have problems with it?

 

[RMerlin]

I fully understand that you're all in newer releases (380+) but could you just hide this glitchy 380.69_2 for models that have problems with it?

That is issue is nowhere serious enough to justify pulling the release. Use the previous release, or wait for me to have the time to look into it. This is a one-man project, I need to prioritize things.

 

[GDT]

More information regarding this problem.... I can't get the client 1 On/Off button to work, it gets stuck in applying setting and goes no where... No OpenVPN messages in syslog.... I did a factory reset and same result. Different browsers with same result.

But if I setup the client VPN in Client 2, then the On/Off button works as advertised.... But as soon as I enter any information on the Server Address, the buttons do not work anymore... Nothing is applied...saved....

So, you should be able to duplicate this problem.... Try to setup a new OpenVPN client.... Type an IP address into the Server Address... Then try Apply .... Nothing happens...

But if instead of an IP address I add the respective FQDN/Hostname, then everything works fine....

Something is not right here....

I got the same issue with the same router.

 

[MXM]

I got the same issue with the same router.

I still have the problem as originally described. I also have no invalid characters on any of the fields. So, this is a problem on the way the webpage is validating information.

But I found a way to get around it. If you enter an IP address, you run into the problem as described. If you enter a FQDN, it works just fine....

 

[GDT]

I still have the problem as originally described. I also have no invalid characters on any of the fields. So, this is a problem on the way the webpage is validating information.

But I found a way to get around it. If you enter an IP address, you run into the problem as described. If you enter a FQDN, it works just fine....

if it helps I added Ip with ssh console through commands:

nvram set vpn_client1_addr=<ip>
nvram commit

Then I started client with:

service start_vpnclient1

 

[DualPlatform]

Thank you @RMerlin! I've been on shibby/tomato for the last 5+ years, and finally made the plunge to this firmware. Waited until this specific release since it addresses KRACK.

Primary reason is that I'm switching over my router duties to my Ubiquiti EdgeRouter X soon, so my RT-N66U will be basically AP only. I also added a second AP, and needed Roaming Assistant for better handoff, which isn't a feature in Tomato. Took me literally less than 15 minutes to flash this firmware over Shibby, and reconfigure my port forwards and DDNS.

FWIW, Roaming Assistant isn't a silver bullet from what I've read. Its really just a suggestion for the clients, and does not hard disconnect when over the RSSI threshold. That said, having it is better than nothing. Though, I do wish I could set it higher than -70.

How has the transition to the EdgeRouter X and the RT-N66U running in AP mode? Did you attempt anything with the guest wifi and vlan between the router and APs?

 

[tsunami2311]

I notice the bug with Bandwidth limiter is still there from older verision

IF i edit the bandwidth limiter after it set it breaks limiting, some clients defined to be limited will be limited other will not be, only way to get to work for all them again is to turn off bandwidth limiting and then add them all again and then hit apply. any editing after the intitial setup seem to break it partial on random clients

 

[groth.ron]

On my RT-N66U, I upgraded from Asuswrt-Merlin 64 to 69_2. I used the NVRAM Utility to save the configuration, did the factory reset, upgraded the firmware, and and did the factory reset again. Then I used the NVRAM Utility to restore the configuration. Part of my configuration was the Network Services Filter in the Firewall. I have a screen cap here showing the NSF in the disabled state. When the configuration is enabled, none of my devices can access the internet. Windows 10 PCs show "Unable to detect proxy configuration for this network". The odd thing is that this configuration worked without issue in Asuswrt-Merlin 64 and the targeted device was unable to access the internet during the timeframes selected. So, for now I have it disabled. It's behaving as if its the whitelist instead of the blacklist. Has anyone else seen this? Is it a bug in underlying ASUS code?

Modem -- RT-N66U at modem location (in Router mode) -- RT-N66U in Living Room (in Repeater mode). Both devices have wireless and wired clients, and both are running 69_2.

 

[PDinDetroit]

FYI

https://www.snbforums.com/threads/end-of-year-2017-development-update.42965/

[Beta 384/NG] Asuswrt-merlin 384.4 Beta is now available

 

[groth.ron]

I appreciate that. Unfortunately I'm "stuck" on the legacy branch which I know will only get bug fix updates and probably not very many of those, since I have two RT-N66U devices. They work fine for what I do, so I have no immediate incentive to upgrade hardware for $. Just hoping that this particular bug, if it is that, can get resolution. Thanks.

 

[PDinDetroit]

I appreciate that. Unfortunately I'm "stuck" on the legacy branch which I know will only get bug fix updates and probably not very many of those, since I have two RT-N66U devices. They work fine for what I do, so I have no immediate incentive to upgrade hardware for $. Just hoping that this particular bug, if it is that, can get resolution. Thanks.

https://www.snbforums.com/threads/fork-asuswrt-merlin-374-43-lts-releases-v31e6.18914/

I have 2 RT-AC66's as well, will have to migrate to john9527 fork at some point.