Release Asuswrt-Merlin 388.2 is now available for select models

[capitan_asco]

I don't see that one on the supported list for Merlin FW.

See here: https://www.asuswrt-merlin.net/about

So it only refers to current routers with wifi 6 that support AsusWrt and does not refer to all Asus routers with wifi 6.

My mistake of interpretation.

All the best

 

[shabbs]

I'm not sure where you saw the statement "all routers" as Eric has always kept a list of supported devices so that eveyrone knows which version is supported on which platform.

 

[ComputerSteve]

I keep getting this error on this firmware when I check for updates: The router cannot connect to the update server to check for firmware updates.

 

[Bogey]

Im trying to track down an issue with the most recent dnsmasq (in 388.2) where reading the hosts file causes dnsmasq to catch a Fatal Signal 6 (Sig Abort). In my case, dnsmasq restarts and seems to give out addresses fine.

In your case, it shows a Signal 11 - Segmentation violation.

In my log I don't see a dnsmasq restart after the Signal 11. I guess "fatal" isn't so fatal in this case
There doesn't seem to be a pattern of some sort behind these Signal 11 notifications. Not in the frequency of appearing, one after 11 minutes, next one 4 minutes later, next x minutes, then y minutes.

 

[azuza]

I just upgraded my Merlin firmware for AX86U... now my ExpressVPN won't work.

Anyone else having this problem?

Thanks,
A

 

[L&LD]

@azuza, you need to provide much more details. And it doesn't matter if anyone else is having this problem.

Which firmware did you upgrade from? Why aren't you using the latest 388.2_2 final? What other scripts, options, and features are you using on your router? Have you tried deleting the VPN and re-adding it? Have you tried rebooting the router to see if that solves the issue?

 

[Smokey613]

I just upgraded my Merlin firmware for AX86U... now my ExpressVPN won't work.

Anyone else having this problem?

Thanks,
A

Which firmware were you running prior to the upgrade? You should now be running 388.2_2 as it is the latest Merlin firmware.

Also, make sure you are using a vpn client config that is compatible with openvpn 2.6 as this is the version used in the latest Merlin firmware.

Also, it helps to know the hardware you are running.

 

[octopus]

I just upgraded my Merlin firmware for AX86U... now my ExpressVPN won't work.

Anyone else having this problem?

Thanks,
A

What do your log says?

 

[saison2023]

In my log I don't see a dnsmasq restart after the Signal 11. I guess "fatal" isn't so fatal in this case
There doesn't seem to be a pattern of some sort behind these Signal 11 notifications. Not in the frequency of appearing, one after 11 minutes, next one 4 minutes later, next x minutes, then y minutes.

Like you, no dnsmasq and no real pattern

Example with this morning:

Spoiler: Fatal Signal 11 (08:10:42

May 13 08:10:42 kernel: potentially unexpected fatal signal 11.
May 13 08:10:42 kernel: CPU: 1 PID: 6407 Comm: dcd Tainted: P O 4.1.52 #2
May 13 08:10:42 kernel: Hardware name: Broadcom-v8A (DT)
May 13 08:10:42 kernel: task: ffffffc0298d7440 ti: ffffffc022ffc000 task.ti: ffffffc022ffc000
May 13 08:10:42 kernel: PC is at 0xf6fb139c
May 13 08:10:42 kernel: LR is at 0x1dce0
May 13 08:10:42 kernel: pc : [<00000000f6fb139c>] lr : [<000000000001dce0>] pstate: 600b0010
May 13 08:10:42 kernel: sp : 00000000ff924bb8
May 13 08:10:42 kernel: x12: 00000000000a2050
May 13 08:10:42 kernel: x11: 00000000f62ff024 x10: 00000000000a23c4
May 13 08:10:42 kernel: x9 : 00000000f62ff8b4 x8 : 00000000000a287c
May 13 08:10:42 kernel: x7 : 00000000f62ff8ec x6 : 00000000000a2876
May 13 08:10:42 kernel: x5 : 0000000000000000 x4 : 00000000f62ff898
May 13 08:10:42 kernel: x3 : 0000000000000000 x2 : 00000000ff924b94
May 13 08:10:42 kernel: x1 : 000000000007d72e x0 : 0000000000000000

Spoiler: Fatal Signal 11 (08:38:07

May 13 08:38:07 kernel: potentially unexpected fatal signal 11.
May 13 08:38:07 kernel: CPU: 1 PID: 17890 Comm: dcd Tainted: P O 4.1.52 #2
May 13 08:38:07 kernel: Hardware name: Broadcom-v8A (DT)
May 13 08:38:07 kernel: task: ffffffc03e8d2180 ti: ffffffc027a0c000 task.ti: ffffffc027a0c000
May 13 08:38:07 kernel: PC is at 0xf6fa039c
May 13 08:38:07 kernel: LR is at 0x1dce0
May 13 08:38:07 kernel: pc : [<00000000f6fa039c>] lr : [<000000000001dce0>] pstate: 600b0010
May 13 08:38:07 kernel: sp : 00000000ffd6b0e8
May 13 08:38:07 kernel: x12: 00000000000a2050
May 13 08:38:07 kernel: x11: 00000000f62ff024 x10: 00000000000a23c4
May 13 08:38:07 kernel: x9 : 00000000f62ff8b4 x8 : 00000000000a287c
May 13 08:38:07 kernel: x7 : 00000000f62ff8ec x6 : 00000000000a2876
May 13 08:38:07 kernel: x5 : 0000000000000000 x4 : 00000000f62ff898
May 13 08:38:07 kernel: x3 : 0000000000000000 x2 : 00000000ffd6b0c4
May 13 08:38:07 kernel: x1 : 000000000007d72e x0 : 0000000000000000

Spoiler: Fatal Signal 11 (09:04:01 and 09:04:18)

May 13 09:04:01 kernel: potentially unexpected fatal signal 11.
May 13 09:04:01 kernel: CPU: 2 PID: 1334 Comm: dnsmasq Tainted: P O 4.1.52 #2
May 13 09:04:01 kernel: Hardware name: Broadcom-v8A (DT)
May 13 09:04:01 kernel: task: ffffffc028c60b40 ti: ffffffc009854000 task.ti: ffffffc009854000
May 13 09:04:01 kernel: PC is at 0xf7632654
May 13 09:04:01 kernel: LR is at 0x209ac
May 13 09:04:01 kernel: pc : [<00000000f7632654>] lr : [<00000000000209ac>] pstate: 20010010
May 13 09:04:02 kernel: sp : 00000000ffb9a6d8
May 13 09:04:02 kernel: x12: 0000000000000072
May 13 09:04:02 kernel: x11: 000000000003e4b3 x10: 000000000009a70c
May 13 09:04:02 kernel: x9 : 000000000003e4b4 x8 : 00000000ffffffff
May 13 09:04:02 kernel: x7 : 000000000009a70c x6 : 00000000016cded0
May 13 09:04:02 kernel: x5 : 00000000f76df5cc x4 : 00000000ffb9a580
May 13 09:04:02 kernel: x3 : 0000000000000000 x2 : 0000000000000120
May 13 09:04:02 kernel: x1 : 0000000000000000 x0 : 0000000000000072
May 13 09:04:18 kernel: potentially unexpected fatal signal 11.
May 13 09:04:18 kernel: CPU: 1 PID: 29610 Comm: dcd Tainted: P O 4.1.52 #2
May 13 09:04:18 kernel: Hardware name: Broadcom-v8A (DT)
May 13 09:04:18 kernel: task: ffffffc029902140 ti: ffffffc022ea0000 task.ti: ffffffc022ea0000
May 13 09:04:18 kernel: PC is at 0xf709839c
May 13 09:04:18 kernel: LR is at 0x1dce0
May 13 09:04:18 kernel: pc : [<00000000f709839c>] lr : [<000000000001dce0>] pstate: 600b0010
May 13 09:04:18 kernel: sp : 00000000ffe61cb8
May 13 09:04:18 kernel: x12: 00000000000a2050
May 13 09:04:18 kernel: x11: 00000000f63ff024 x10: 00000000000a23c4
May 13 09:04:18 kernel: x9 : 00000000f63ff8fc x8 : 00000000000a287c
May 13 09:04:18 kernel: x7 : 00000000f63ff934 x6 : 00000000000a2876
May 13 09:04:18 kernel: x5 : 0000000000000000 x4 : 00000000f63ff8e0
May 13 09:04:18 kernel: x3 : 0000000000000000 x2 : 00000000ffe61c94
May 13 09:04:18 kernel: x1 : 000000000007d72e x0 : 0000000000000000

Each time fatal signal happened, only one device was running and connected to Internet, our Android TV and we were watching streaming videos.
All other devices were "sleeping", so was not a heavy load that could cause a trouble.

 

[XIII]

Upgraded my AX6000 to 388.2_2 and noticed that my iPhone/iPad can reach the internet over the router's OpenVPN (via 4G), but my Mac can only reach my LAN over OpenVPN (via hotel WiFi); not the internet.

This is the first time I try OpenVPN on my Mac, so it might very well not be related to this release...

Visited a family member earlier today and OpenVPN worked fine on my MacBook Pro.

I guess it was the hotel WiFi that was the issue before (so indeed not 388.2_2 related).

 

[visortgw]

Visited a family member earlier today and OpenVPN worked fine on my MacBook Pro.

I guess it was the hotel WiFi that was the issue before (so indeed not 388.2_2 related).

Some hotels block common ports (e.g., 1194) used by VPNs.

 

[azuza]

@azuza, you need to provide much more details. And it doesn't matter if anyone else is having this problem.

Which firmware did you upgrade from? Why aren't you using the latest 388.2_2 final? What other scripts, options, and features are you using on your router? Have you tried deleting the VPN and re-adding it? Have you tried rebooting the router to see if that solves the issue?

Sorry. I upgraded from 388.2 to 388.2.2, I believe, from Sourceforge.

I don't know how to code custom scripts for my router. I can't figure out how to delete the VPN clients from the dropdown options. And as far as rebooting, I haven't tried that because I thought it already rebooted after the firmware installation.

edit: nevermind... i figured out how to delete vpn clients

 

[azuza]

Okay, I got it working.

I deleted all the VPN clients and re-did the whole set up.

Thanks everyone.

(I do hope that Merlin developers would consider Lightway as it establishes itself in the future.)

 

[saison2023]

Like some, i am experimenting problem with latest firmware and trying to troubleshoot.
It is related to Diversion.
I tested with pixelserv disabled and got a different error when "fatal signal 11"" occurred

Spoiler: Fatal signal dnsmasq

May 14 09:54:01 kernel: potentially unexpected fatal signal 11.
May 14 09:54:01 kernel: CPU: 2 PID: 8588 Comm: dnsmasq Tainted: P O 4.1.52 #2
May 14 09:54:01 kernel: Hardware name: Broadcom-v8A (DT)
May 14 09:54:01 kernel: task: ffffffc024def580 ti: ffffffc0239c0000 task.ti: ffffffc0239c0000
May 14 09:54:01 kernel: PC is at 0xf6efc654
May 14 09:54:01 kernel: LR is at 0x209ac
May 14 09:54:01 kernel: pc : [<00000000f6efc654>] lr : [<00000000000209ac>] pstate: 20010010
May 14 09:54:01 kernel: sp : 00000000fffdebd8
May 14 09:54:01 kernel: x12: 0000000000000072
May 14 09:54:01 kernel: x11: 00000000000541eb x10: 000000000009a70c
May 14 09:54:01 kernel: x9 : 00000000000541ec x8 : 00000000ffffffff
May 14 09:54:01 kernel: x7 : 000000000009a70c x6 : 0000000001641ca8
May 14 09:54:01 kernel: x5 : 00000000f6fa95cc x4 : 00000000fffdea80
May 14 09:54:01 kernel: x3 : 0000000000000000 x2 : 0000000000000120
May 14 09:54:01 kernel: x1 : 0000000000000000 x0 : 0000000000000072

I am still keeping pixelserv disabled and I have also disabled dnsmasq logging

 

[Damit1]

6 days, 388.2 running, no issues with WiFi or whatsoever.

36/80Mhz...

 

[John35]

I have a question which may have nothing to do with 388.2 (which I'm running on a GT-AX6000) but it's very odd, so I thought I'd ask...
I have this interfering 5GHz signal with the SSID "DIRECT-VK-Android_9c3f" and whenever I move the Router Channel away it moves to follow it shortly afterwards. It's extremely odd?
Blue is my 5GHz and Yellow is the "DIRECT" one...

 

[djbrad]

Some remotes like the firetv use wifi to link to the stick. Do you have an android box nearby?

 

[John35]

Some remotes like the firetv use wifi to link to the stick. Do you have an android box nearby?

I have a FireTV 4k, but haven't used it for some time, if the remote were not asleep and putting out WiFi I can't see the batteries would still be going? Also a Shield TV, but again not used for a long time. Thanks for the reply!

It's just so odd it tracks the router channel changes?

 

[ColinTaylor]

I have a FireTV 4k, but haven't used it for some time, if the remote were not asleep and putting out WiFi I can't see the batteries would still be going? Also a Shield TV, but again not used for a long time. Thanks for the reply!

It's just so odd it tracks the router channel changes?

This is a Wi-Fi Direct device and its behaviour is normal. This has nothing to do with this release so I suggest you start your own thread if you want to discuss it further.

 

[JGrana]

Like some, i am experimenting problem with latest firmware and trying to troubleshoot.
It is related to Diversion.
I tested with pixelserv disabled and got a different error when "fatal signal 11"" occurred

Spoiler: Fatal signal dnsmasq

May 14 09:54:01 kernel: potentially unexpected fatal signal 11.
May 14 09:54:01 kernel: CPU: 2 PID: 8588 Comm: dnsmasq Tainted: P O 4.1.52 #2
May 14 09:54:01 kernel: Hardware name: Broadcom-v8A (DT)
May 14 09:54:01 kernel: task: ffffffc024def580 ti: ffffffc0239c0000 task.ti: ffffffc0239c0000
May 14 09:54:01 kernel: PC is at 0xf6efc654
May 14 09:54:01 kernel: LR is at 0x209ac
May 14 09:54:01 kernel: pc : [<00000000f6efc654>] lr : [<00000000000209ac>] pstate: 20010010
May 14 09:54:01 kernel: sp : 00000000fffdebd8
May 14 09:54:01 kernel: x12: 0000000000000072
May 14 09:54:01 kernel: x11: 00000000000541eb x10: 000000000009a70c
May 14 09:54:01 kernel: x9 : 00000000000541ec x8 : 00000000ffffffff
May 14 09:54:01 kernel: x7 : 000000000009a70c x6 : 0000000001641ca8
May 14 09:54:01 kernel: x5 : 00000000f6fa95cc x4 : 00000000fffdea80
May 14 09:54:01 kernel: x3 : 0000000000000000 x2 : 0000000000000120
May 14 09:54:01 kernel: x1 : 0000000000000000 x0 : 0000000000000072

I am still keeping pixelserv disabled and I have also disabled dnsmasq logging

I had similar dnsmasq fatal errors with 388.2. With that release, dnsmasq is version 2.89. With the 388.1 release, it was 2.85.

I am now running 388.2 with the dnsmasq from 388.1. No more fatal errors.

If you still have 388.1 running, you can copy dnsmasq version 2.85 from that release (from /usr/sbin) to a usb stick, install 388.2 then copy the dnsmasq 2.85 binary to either /jffs or /opt (if Entware is installed). Then do what’s called a mount bind.
For example, I copied dnsmasq (v2.85) to /opt/tmp/sbin.
Then I ran this mount command:

mount -o bind,rw /opt/tmp/sbin/dnsmasq /usr/sbin/dnsmasq

Restert dnsmasq:

service restart_dnsmasq

Keep in mind, on a reboot, you will be back to dnsmasq 2.89 (unless you redo the mount and restart).

This is all temporary until the dnsmasq folks track down this issue.

In my case I was getting 2-3 dnsmasq Fatal 6 errors/day. Reverting to 2.85 a few days ago - none.