What's new

Beta Asuswrt-Merlin 388.2 Beta is now available for Wifi 6 models

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Sorry for my english, google translate. After upgrading from Merlin 388.2alfa1 to 388.2alfa2 or to 388.2beta1, static entries in arp stop being static in fact and after five minutes they go into incomplete status and, accordingly, stop working. The bug manifests itself with any update - dirty and clean. I returned to 388.2alfa1 - everything is fine.
 

Attachments

  • 1.jpg
    1.jpg
    151 KB · Views: 99
The only problem I’m having might be related to something on my network.
If I reboot the AX88U Pro, some devices (iPhone, ecobee thermostat, Harmony Hub) seem to get assigned a DHCP address in the 10.10.13.X address space, even though they are on the correct SSID

Hmmm - I've also seen this, but only when I first installed 388.2B.
My windows P/C got allocated 10.8.0.2 - it's usually 192.168.1.105.

I only noticed it when checking my PiHole logs, the P/C has gone back to it's 'Normal' address now and I can't reproduce it.

I did see some dnsmasq messages in syslog, but I can't remember what they were now.
 
Having issues adding mesh nodes.
Rt-ax88u and rt-ax58u both fail if on 388.2 fully reset. Unable to add the even if 1 ft apart from master.
When flashing back to stock 388.22525 i can add them as nodes no problem.

I had issues too, where at ~25% it would turn off wireless on the main router and adding the node would fail but if I tried immediately to add it again, it would successfully add it the 2nd try
 
Hmmm - I've also seen this, but only when I first installed 388.2B.
My windows P/C got allocated 10.8.0.2 - it's usually 192.168.1.105.

I only noticed it when checking my PiHole logs, the P/C has gone back to it's 'Normal' address now and I can't reproduce it.

I did see some dnsmasq messages in syslog, but I can't remember what they were now.
Interesting. If it happens again, look in /tmp/syslog.log for something like this:

Mar 23 13:56:04 custom_script: Running /jffs/scripts/wan-event (args: 0 stopped)
Mar 23 13:56:04 kernel: CPU: 0 PID: 5488 Comm: dnsmasq Tainted: P O 4.19.183 #1
Mar 23 13:56:04 kernel: Hardware name: RTAX88U_PRO (DT)
Mar 23 13:56:04 kernel: pstate: 00070010 (nzcv q A32 LE aif)
Mar 23 13:56:04 kernel: pc : 00000000f781a3a4
Mar 23 13:56:04 kernel: lr : 00000000fffa0cb0
Mar 23 13:56:04 kernel: sp : 00000000fffa0cb0
Mar 23 13:56:04 kernel: x12: 0000000000000000
Mar 23 13:56:04 kernel: x11: 00000000fffa0f40 x10: 00000000f7910de0
Mar 23 13:56:04 kernel: x9 : 0000000000000002 x8 : 0000000000000001
Mar 23 13:56:04 kernel: x7 : 00000000000000af x6 : 00000000fffa0ef0
Mar 23 13:56:04 kernel: x5 : 00000000fffa0ef0 x4 : 0000000000000006
Mar 23 13:56:04 kernel: x3 : 0000000000000008 x2 : 0000000000000000
Mar 23 13:56:04 kernel: x1 : 00000000fffa0cb0 x0 : 0000000000000000
Mar 23 13:56:04 custom_script: Running /jffs/scripts/wan-event (args: 0 stopped)

Unfortunately debugging for me is a bit of an issue. Not good when my smart thermostat and Harmony Hub gets into an odd network state. And, my Amazon Echo is used quite a bit by my wife - so when it goes off network, I hear about it quickly.
What I find interesting in all cases is that the devices do connect to the correct SSID. Its the address they are assigned. My local lan is 192.168.1.X (been that way for years) -the affected devices all end up with a 10.10.13.X address - until time or me resetting them, often more than once, gets them back onto the correct lan address.
Also, I can't go back to anything other than 388... Im on an AX88U Pro.
 
I did a remote dirty upgrade :rolleyes: on my AX11000 and it went smoothly. Nodes come up very fast now!
 
If I reboot the AX88U Pro, some devices (iPhone, ecobee thermostat, Harmony Hub) seem to get assigned a DHCP address in the 10.10.13.X address space, even though they are on the correct SSID.
You have a rogue DHCP server running on your LAN, you need to locate it, and disable it.
 
Merlin just wanted to say many thanks for all the hard work and if you could please keep supporting RT-AX58U in the future! There are many of us who have it and love running Asuswrt-Merlin firmware on it!
Ditto!
My modest internet and WiFi requirements are more than satisfied by a RT-AX3000 (V1) Gateway and RT-AX56U Mesh node. It will be most disappointing to see Merlin support dropped for these devices.
Again, many thanks for your herculean efforts.
 
Found another issue:
The QoS - WAN/LAN Bandwidth Monitor for me only works for a few hours, then it no longer shows any throughput.
After a reboot it works again...

Here's the solution: you must have accepted the "Trend Micro End User License Agreement" in order for the "QoS - WAN/LAN Bandwidth Monitor" to work. Either when switching on "Apps analysis" or when using the AiProtection. If you reject/withdraw the "Trend Micro End User License Agreement" the "QoS - WAN/LAN Bandwidth Monitor" will not work.

EDIT:
In addition, either "Apps analysis" or "AiProtection" must be activated.
 
Last edited:
Hmm... IPv6 Native enabled, DNS Director (Router) causing IPv4 test fail:

View attachment 48847


Is this normal or expected? First time seeing this...

DNS Director off:

View attachment 48846
Very possibly an error at their end. I have been getting very inconsistent results from ipv6-test recently (approx 4- 6 weeks) - including IPv4 not supported, IPv6 not supported and even IPv4 and IPv6 both not supported at the same time! Any other test tells me that IPv6 is working as expected, plus I can connect to IPv6 only sites - which given I am running dual stack with IPv6 native and DHCP-PD is what I would expect.
 
That test site is broken and has been for a long time, don't use it.
 
I have no idea if this is due to the new firmware or if my ISP (Sky in the UK) has changed its configuration but, for as long as I can recall the IPv4 WAN IP would appear as the default gateway address in the Routing Table. Now it is showing the root rather than the WAN IP, e.g. if my WAN IP is 2.122.61.140 the Gateway in Routing Table will show as 2.122.60.1
 
Have symmetic bandwidth 1G fiber with AT&T. Under normal conditions the PC/Ookla Speedtest comes back at ~930Mbs +/- 10Mbps and so does the router whether SPDMerlin or it's own Speedtest.

At random times, the SpeedTest results at the router whether using SPDMerlin or the it's own Speedtest the results come back asymetrical, ~410Mbps +/- 40Mbps on the down and ~650Mbps +/- 50Mbps on the up. I've yet to correlate anything in the log (running Scribe) at the time window that issue happens in. What I can say is that only a reboot fixes it back to normal, so far. Restarting the WAN interface or AT&T modem does not fix it, only a reboot at the router, does not look to be carrier related. When this happens WiFi gets hit as well, and Speedtest results drop by ~150Mbs, but with asymmetrical results where the down is lower than the up. But on the wired devices, its a consistent ~930Mbs +/- 10Mbps in both directions regardless of this drop. This also happend to me with the 388.1 releases but with so many WiFi issues with that release this took a back seat, all the TV's and streaming boxes are wired sny way. But its happening again, before I HW reset the AX88 router and start from scratch, curious if anyone else has run into this situation. Thinking I may just reboot the router and monitor it to capture the different logs at the time the router goes into limp mode, instead. I've yet to disable Skynet temporarily to eliminate it. Plenty of RAM on the router, and CPU is in the single digits also no QoS at play either. Trying to find/locate/capture the bandwidth drop in the log. Looking for way of fixing this without a reboot, but no luck so far.

Looks like this in SPDMerlin, very easy to see normal/abnormal conditions.
View attachment 48863

From a Scibe/UIScribe perspective, these filters are active
View attachment 48864

Any ideas?
Maybe a faulty ethernet connection with the modem and router wan port. You could try replacing the ethernet cable. Also, it wouldn't hurt to test without skynet. Also, make sure you are not use trendmicro and make sure you unaccept its privacy disclaimer.
 
Last edited:
Now it is showing the root rather than the WAN IP, e.g. if my WAN IP is 2.122.61.140 the Gateway in Routing Table will show as 2.122.60.1
This is what I would expect to see, so I don't think this is anything to do with this firmware. I don't know what you had before but the router can't have its own IP address as the default gateway, it has to be some other device.
 
I have no idea if this is due to the new firmware or if my ISP (Sky in the UK) has changed its configuration but, for as long as I can recall the IPv4 WAN IP would appear as the default gateway address in the Routing Table. Now it is showing the root rather than the WAN IP, e.g. if my WAN IP is 2.122.61.140 the Gateway in Routing Table will show as 2.122.60.1
Do you pay for a static ip? Or are you receiving ip from dynamic assignment?
 
You have a rogue DHCP server running on your LAN, you need to locate it, and disable it.
Agreed. Now to elimate clients one by one. I do have a suspicion though….
 
Installed on GT-AXE1600 over stock. Did a reset and setup as normal. Nothing fancy.
About 45 connections no VPN. ALL my Apple devices would not connect as well as my Alarm.com video doorbell. Very strange. I did another factory reset, set up my SSID's as I did many times again. Same result any ideas?

I then installed the Stock Firmware. Factor reset set up as normal. Everything connects perfectly.

Can I just install Beta 1 over the stock firmware with no reset? Maybe that may work but not sure.

CC
 
Last edited:
Status
Not open for further replies.

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top