Release Asuswrt-Merlin 3004.388.8_2 is now available

[ciprian.trofin]

Thank you. Will try it soon.

What is the appropriate channel for bug reports ? SNB Forum or some dedicate email?

 

[iBest]

Hi! Can you please tell me where exactly you can disable the new kill-switch rule?
My openvpn is not able to communicate with wireguard vpn after this update.
Thanks !

PS: VPNDirector is not showing something new

 

[netmik3]

Excellent I hate ROG

 

[Kees17760]

Dirty update. Everything seemed to work fine, until reboot. After that router was unreachable (both HTTP and SCP).
Found out VPN configuration was the culprit. Had to setup VPN from scratch. Working fine now.

 

[iBest]

I have 2 sites, connected with AX routers both. And with Openvpn.
Site 2 has also some Wireguard server on it.
Site 2 and site 1 are always connected via openvpn and by demand with wireguard from mobile devices. (& to access servers on both sites)
Before the update, wireguard was working inside site 1 to site 2 without any problems
After the update wireguard cant access site 1 it's locked only on where it connects (on site2)

The connection site 1 to site 2 is not using vpn director and it's just injecting lan , without internet redirect.


So read the new changelog and since i don't relay on VPNDirector please advise how to disable the new vpn rules added to this new fw.
Thanks !

PS: Rolling back to 388.7 it just works.

 

[Mittenz]

@RMerlin

hey man can you upload the ROG version for the AX11000, the stock UI destroys my eyes in dark room tweaking settings.
ROG please, all previous versions have this.

Appreciate it and much love.

 

[bennor]

@RMerlin

hey man can you upload the ROG version for the AX11000, the stock UI destroys my eyes in dark room tweaking settings.
ROG please, all previous versions have this.

Appreciate it and much love.

If you haven't already seen it, note what RMerlin has already indicated about ROG firmware version in post #2 and #4 on the first page:

Known issues:

• No ROG versions of the release (was accidentally left disabled in the build process, should be re-included in the next release)

It was accidentally left disabled in my build script when I generated this release, so these images didn't get generated.

I don't really feel like going through the full rebuild + release process just to recreate all release archives with the missing images, so this release won't have ROG versions for the time being. Keep in mind that I initially mentionned that ROG releases were experimental and not fully supported, so they were never guaranteed to be alaways present or fully working. I am in fact dropping their support for the 3006 releases due to the amount of extra work involved in properly maintaining them.

If there is need for a 3004.388.8_2 point release at some point I will re-include them at that time.

 

[Mittenz]

Just read that 10seconds before the post. Appreciate the quotes for others to find it.

 

[BeachGuy]

I upgraded using this firmware on GT-AX6000. Was working fine, checked several settings. Was going to reset to factory defaults but decided to unplug and plug in again and no response (red ROG light and power light on). Tried method 1 (hold reset while powering on) and method 2 (hold WPS button while powering on) but seems to be bricked. I also tried both with the 30/30/30 method. Also tried rescue media but it doesn't connect. Have NEVER had any problems updating firmware. Any suggestions?

 

[elorimer]

This isn't a complaint. Make sure you have a current backup of everything before you update.

I went from .7 to .8 on an AX86 Pro with two openvpn clients with killswitches. Without a current backup. I lost everything, including the whole addon stuff on an SSD. I can't say I wasn't warned.

Time probably to reset to defaults anyway.

 

[Quoc Huynh]

Thank you. Will try it soon.

What is the appropriate channel for bug reports ? SNB Forum or some dedicate email?

I think you can comment logs associated with the bugs here, make a new post, or direct message the author.

 

[gmt]

AX86U here, quick upgrade from .07 to .08, all fine till now

 

[Mando]

Dirty upgrade from .7 on AX88U Pro without any issues.

Question about the (new) VPN Killswitch though..

I've used ProtonVPN Wireguard without killswitch for a while now but I want to finally enable the VPN killswitch for this connection. My setup is very simple, here are the VPN Director rules for my Wireguard Client 1 VPN connection:

Am I correct to say if I enable the killswitch for my Wireguard Client 1 it will only block WAN traffic for subnet 192.168.201.0/24 when booting the router (or when the tunnel goes down)? It should leave the 192.168.200.0/24 subnet WAN access working right? Because that one is routed solely to WAN & has nothing to do with the VPN.

The persistent rule in the routing table takes the VPN Directory rules into account I assume?

Just want to make sure before I enable this option & my apologies if this sounds like a stupid question.

 

[cc666]

Does anyone know the GPL code this release is based on?

CC

 

[Kees17760]

Does anyone know the GPL code this release is based on?

CC

From changelog 3004.388.6 >>> UPDATED: Merged GPL 388_24353

 

[BeachGuy]

I upgraded using this firmware on GT-AX6000. Was working fine, checked several settings. Was going to reset to factory defaults but decided to unplug and plug in again and no response (red ROG light and power light on). Tried method 1 (hold reset while powering on) and method 2 (hold WPS button while powering on) but seems to be bricked. I also tried both with the 30/30/30 method. Also tried rescue media but it doesn't connect. Have NEVER had any problems updating firmware. Any suggestions?

Anyone?

 

[jerry6]

I upgraded using this firmware on GT-AX6000. Was working fine, checked several settings. Was going to reset to factory defaults but decided to unplug and plug in again and no response (red ROG light and power light on). Tried method 1 (hold reset while powering on) and method 2 (hold WPS button while powering on) but seems to be bricked. I also tried both with the 30/30/30 method. Also tried rescue media but it doesn't connect. Have NEVER had any problems updating firmware. Any suggestions?

there is no ROG version in this update

 

[BeachGuy]

there is no ROG version in this update

I used GT-AX6000_3004_388.8_0_nand_squashfs.pkgtb. Is that what bricked it?

 

[jerry6]

I used GT-AX6000_3004_388.8_0_nand_squashfs.pkgtb. Is that what bricked it?

should not brick it , very hard to brick these routers 30-30-30 is not used on these routers try some of the other methods found on this site . Good luck

 

[BeachGuy]

"very hard to brick these routers". That's what I thought, but I seem to have found a way to do it. Tried every reset method and no luck. Going to contact ASUS.