Beta Asuswrt-Merlin 388.1 Beta is available for select models

[Farley]

I bought a new GT-AX6000 two days ago and immediately installed the new Beta1 firmware, then upgraded yesterday to Beta2.

All seems to be going OK, except that a couple of times the 2.4GHz WiFi has totally refused to accept connections after a start or reboot of the router. The problem went away after another reboot. Is there a chance that it's the beta firmware, or am I more likely to have a faulty router? The log messages look like this when I turn on debugging:

Nov 13 08:09:55 wlceventd: wlceventd_proc_event(469): wl0.1: Deauth_ind D0:BA:E4:E7:A7:FC, status: 0, reason: Disassociated due to inactivity (4)
Nov 13 08:09:56 wlceventd: wlceventd_proc_event(469): wl0.1: Deauth_ind D0:BA:E4:E7:A7:FC, status: 0, reason: Unspecified reason (1)
Nov 13 08:09:56 wlceventd: wlceventd_proc_event(505): wl0.1: Auth D0:BA:E4:E7:A7:FC, status: Successful (0)

But then it keeps looping for all devices (which are mostly my IoT devices on the 2.4 guest network).

When I tried to connect to the regular 2.4 GHz SSID with an Android tablet it came up with a message along the lines of "access point is fully occupied" (or words to that effect).

 

[cc666]

Merlin or anyone else can you explain why all of a sudden I am getting these in my logs?
I am using DNS over TLS using 1.1.1.1 and 1.0.0.1.
The below comes in over andover again. Any help would be appreciated

Nov 12 21:51:46 dnsmasq[2042]: possible DNS-rebind attack detected: sensors.yodo1api.com
Nov 12 21:52:02 dnsmasq[2042]: possible DNS-rebind attack detected: logs.ironsrc.mobi
Nov 12 21:53:05 dnsmasq[2042]: possible DNS-rebind attack detected: sensors.yodo1api.com

CC

 

[Treadler]

Merlin or anyone else can you explain why all of a sudden I am getting these in my logs?
I am using DNS over TLS using 1.1.1.1 and 1.0.0.1.
The below comes in over andover again. Any help would be appreciated

Nov 12 21:51:46 dnsmasq[2042]: possible DNS-rebind attack detected: sensors.yodo1api.com
Nov 12 21:52:02 dnsmasq[2042]: possible DNS-rebind attack detected: logs.ironsrc.mobi
Nov 12 21:53:05 dnsmasq[2042]: possible DNS-rebind attack detected: sensors.yodo1api.com

CC

DNS rebinding - Wikipedia

en.wikipedia.org

The ‘why’ is above my pay grade, sorry.

 

[cc666]

DNS rebinding - Wikipedia

en.wikipedia.org

The ‘why’ is above my pay grade, sorry.

Well I can now report, under the firewall tab, enable IPV4 firewall under basic config was defaulted to OFF. I turned that on and now the log entried stopped. Why is the default setting OFF? I will let it run overnight and see if any logs return.

CC

 

[lepa71]

Does IPv6 work fine? I'm having some issues with it. I used to use only IPv4. I was thinking to play with IPv6 and enabled it. Apps on my GoogleTV would take quite a long time to start. Some websites would have issues loading. finance.yahoo.com is one of them.
Does anybody have IPv6 working fine?

Thanks

 

[PR3MIUM]

all fine...

 

[Jumpstarter]

APs still solid here after almost 48 hours.

View attachment 45281

*quietly misses the uptime thread*

I am still going !

 

[PR3MIUM]

I am still going !

View attachment 45439

version ? no dfind scans over there

 

[Jumpstarter]

I am going to hold off on switching my main from alpha to beta. When I alpha test, I alpha test for awhile!

 

[Treadler]

Does IPv6 work fine? I'm having some issues with it. I used to use only IPv4. I was thinking to play with IPv6 and enabled it. Apps on my GoogleTV would take quite a long time to start. Some websites would have issues loading. finance.yahoo.com is one of them.
Does anybody have IPv6 working fine?

Thanks

Whatever you may think of IPv6, certainly works smooth & snappy here. No latency issues.

 

[Treadler]

Does IPv6 work fine? I'm having some issues with it. I used to use only IPv4. I was thinking to play with IPv6 and enabled it. Apps on my GoogleTV would take quite a long time to start. Some websites would have issues loading. finance.yahoo.com is one of them.
Does anybody have IPv6 working fine?

Thanks

That yahoo site working fine via IPv6.

 

[RMerlin]

The fullcone nat not being supported by kernel is that because ASUS took it out or just not there in general? An if they did take it out why would they do that?

Broadcom never implemented it on that newer SDK, due to changes in Netfilter's architecture in that newer kernel version. I simply hid the non-working setting on these models

If I leave the DNS field of the Wireguard client blank (it is optional), the DNS reported is the DoT DNS on the WAN page, as DNS Director is set to "router". Alternativly if I leave the DNS field blank in the Wireguard client, and manipulate DNS of a device in the tunnel with the DNS Director, it works great. I can change DNS back and forth. Is this the intended operation?

I can't double check at the moment, but if I recall, VPN dns has priority over DNS Director because that's what makes the most sense, you can simply edit the VPN configuration to select what DNS to use for that specific client.

Well I can now report, under the firewall tab, enable IPV4 firewall under basic config was defaulted to OFF. I turned that on and now the log entried stopped. Why is the default setting OFF? I will let it run overnight and see if any logs return.

CC

It's disabled by default because there are no configured rules. This new setting is specifically for manual rules configured on that page.

You are getting rebind messages because you enabled rebind protection, it's doing what it's meant to.

 

[skeal]

you can simply edit the VPN configuration to select what DNS to use for that specific client.

What if you have more than one device running through the VPN? Should I be using another Wireguard client or something?

 

[RMerlin]

What if you have more than one device running through the VPN? Should I be using another Wireguard client or something?

Why would you want different dns servers for clients using the same vpn tunnel? It you don't want to use the vpn-provided dns, then don't configure a dns on that vpn at all, and configure things in DNS Director.

 

[bigAL991]

I have noticed that using either Openvpn or Wireguard connections that certain sites or app are now not logging on as before. Mixcloud app on my phone will not log in if I direct my phone through a vpn on the router. (works fine if I use the vpn on my phone though) I thought maybe something to do with the DNS but have tested a few options without success.
has anyone any ideas how to cure this?

never had this issue on previous releases.

thanks

 

[tarzan2000]

AX86U

388.1_beta2

Spoiler

Nov 13 12:39:18 hostapd: eth7: STA 00:bb:60:3e:c0:d3 WPA: pairwise key handshake completed (RSN)
Nov 13 12:46:02 kernel: potentially unexpected fatal signal 11.
Nov 13 12:46:02 kernel: CPU: 1 PID: 6889 Comm: dcd Tainted: P O 4.1.52 #2
Nov 13 12:46:02 kernel: Hardware name: Broadcom-v8A (DT)
Nov 13 12:46:02 kernel: task: ffffffc03dc04b00 ti: ffffffc0248f4000 task.ti: ffffffc0248f4000
Nov 13 12:46:02 kernel: PC is at 0xf6e6b39c
Nov 13 12:46:02 kernel: LR is at 0x1dce0
Nov 13 12:46:02 kernel: pc : [<00000000f6e6b39c>] lr : [<000000000001dce0>] pstate: 40000010
Nov 13 12:46:02 kernel: sp : 00000000ffee6838
Nov 13 12:46:02 kernel: x12: 00000000000a2050
Nov 13 12:46:02 kernel: x11: 00000000f60ff024 x10: 00000000000a2876
Nov 13 12:46:02 kernel: x9 : 0000000000000020 x8 : 00000000000a287c
Nov 13 12:46:02 kernel: x7 : 000000000000001d x6 : 00000000f60ffe64
Nov 13 12:46:02 kernel: x5 : 0000000000000000 x4 : 00000000f60ffe00
Nov 13 12:46:02 kernel: x3 : 0000000034362f34 x2 : 0000000000000000
Nov 13 12:46:02 kernel: x1 : 000000000007d72e x0 : 0000000000000000

 

[Milan]

hi every 5 secs i am getting this error on AX88U beta2:

Nov 13 11:25:13 RT-AX88U-F810 kernel: httpd: page allocation failure: order:1, mode:0x204020
Nov 13 11:25:13 RT-AX88U-F810 kernel: CPU: 2 PID: 1181 Comm: httpd Tainted: P           O    4.1.51 #2
Nov 13 11:25:13 RT-AX88U-F810 kernel: Hardware name: Broadcom-v8A (DT)
Nov 13 11:25:13 RT-AX88U-F810 kernel: Call trace:
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc000087658>] dump_backtrace+0x0/0x150
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc0000877bc>] show_stack+0x14/0x20
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00052d3e0>] dump_stack+0x90/0xb0
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc000101d40>] warn_alloc_failed+0xd8/0x120
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc0001043dc>] __alloc_pages_nodemask+0x404/0x6a0
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc000138c00>] cache_alloc_refill+0x350/0x610
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc000139060>] kmem_cache_alloc+0xa0/0xd8
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc0003cb840>] __alloc_skb+0x58/0x178
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00045c898>] sk_stream_alloc_skb+0x38/0x108
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc000469990>] tcp_write_xmit+0x490/0xd50
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00046a284>] __tcp_push_pending_frames+0x34/0x98
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00045b92c>] tcp_push.isra.2+0x54/0xb0
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00045d608>] tcp_sendmsg+0x728/0xa18
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00048483c>] inet_sendmsg+0x9c/0xd0
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc0003c0558>] sock_sendmsg+0x18/0x58
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc0003c060c>] sock_write_iter+0x74/0xd8
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00013d9c0>] __vfs_write+0xa8/0x108
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00013e2c0>] vfs_write+0x90/0x188
Nov 13 11:25:13 RT-AX88U-F810 kernel: [<ffffffc00013ec0c>] SyS_write+0x44/0xa0
Nov 13 11:25:13 RT-AX88U-F810 kernel: Mem-Info:
Nov 13 11:25:13 RT-AX88U-F810 kernel: active_anon:4308 inactive_anon:4363 isolated_anon:0
Nov 13 11:25:13 RT-AX88U-F810 kernel: active_file:29284 inactive_file:28754 isolated_file:0
Nov 13 11:25:13 RT-AX88U-F810 kernel: unevictable:1712 dirty:7 writeback:0 unstable:0
Nov 13 11:25:13 RT-AX88U-F810 kernel: slab_reclaimable:52306 slab_unreclaimable:71148
Nov 13 11:25:13 RT-AX88U-F810 kernel: mapped:3322 shmem:209 pagetables:999 bounce:0
Nov 13 11:25:13 RT-AX88U-F810 kernel: free:8056 free_pcp:465 free_cma:0
Nov 13 11:25:13 RT-AX88U-F810 kernel: DMA free:30116kB min:20480kB low:25600kB high:30720kB active_anon:17232kB inactive_anon:17452kB active_file:118136kB inactive_file:114916kB unevictable:6848kB isolated(anon):0kB isolated(file):0kB present:960512kB managed:903528kB mlocked:6848kB dirty:28kB writeback:0kB mapped:13288kB shmem:836kB slab_reclaimable:210424kB slab_unreclaimable:284592kB kernel_stack:4112kB pagetables:3996kB unstable:0kB bounce:0kB free_pcp:1868kB local_pcp:180kB free_cma:0kB writeback_tmp:0kB pages_scanned:196 all_unreclaimable? no
Nov 13 11:25:13 RT-AX88U-F810 kernel: lowmem_reserve[]: 0 0 0
Nov 13 11:25:13 RT-AX88U-F810 kernel: DMA: 5529*4kB (UE) 0*8kB 3*16kB (R) 4*32kB (R) 7*64kB (R) 2*128kB (R) 3*256kB (R) 2*512kB (R) 1*1024kB (R) 0*2048kB 0*4096kB = 25812kB
Nov 13 11:25:13 RT-AX88U-F810 kernel: 61778 total pagecache pages
Nov 13 11:25:13 RT-AX88U-F810 kernel: 1317 pages in swap cache
Nov 13 11:25:13 RT-AX88U-F810 kernel: Swap cache stats: add 19707454, delete 19706137, find 17732893/24699634
Nov 13 11:25:13 RT-AX88U-F810 kernel: Free swap  = 1917820kB
Nov 13 11:25:13 RT-AX88U-F810 kernel: Total swap = 2097148kB
Nov 13 11:25:13 RT-AX88U-F810 kernel: 240128 pages RAM
Nov 13 11:25:13 RT-AX88U-F810 kernel: 0 pages HighMem/MovableOnly
Nov 13 11:25:13 RT-AX88U-F810 kernel: 14246 pages reserved

 

[zer0bitz]

Hello! I was just tinkering around in router settings and came across this.

On network map page I see subnet mask 255.255.240.0 and on LAN page I see it as 255.255.255.0.

Is this correct or not?

 

[eightiescalling]

Hello! I was just tinkering around in router settings and came across this.

On network map page I see subnet mask 255.255.240.0 and on LAN page I see it as 255.255.255.0.

Is this correct or not?

Looks fine to me. First is the subnet on the isp side with the other being the subnet you're using for your own LAN.

 

[skeal]

Why would you want different dns servers for clients using the same vpn tunnel? It you don't want to use the vpn-provided dns, then don't configure a dns on that vpn at all, and configure things in DNS Director.

Thank you for the clarity.