dave14305
Part of the Furniture
Specifically, set "Logged packets type" to None on the Firewall tab, unless you're using Skynet also.
Release [Beta] Asuswrt-Merlin 384.19 beta is now available
- Thread starter RMerlin
- Start date
-
- Tags
- asuswrt-merlin beta firmware
- Status
Xentrk
Part of the Furniture
Those msgs appear to come from skynet. You can install Scribe and uiScribe to create a separate log file for these messages which makes the system log file much easier on the eyes.
Jack Yaz
Part of the Furniture
They're the standard firewall logs. Skynet adds "blocked - inbound" etc. to the log entry
RAH-66
Senior Member
Jeffrey Young
Very Senior Member
Check your logging level on your firewall setting. Looks like you set to log dropped firewall hits. Set the level to none.
thanks guys for the help...
heysoundude
Part of the Furniture
And this beta is nearing a week old, which is when Merlin's betas usually ripen into releases
384.19 changelog includes: "- UPDATED: Merged bwdpi components from 385_20630 firmware image for RT-AC68U."
Does this mean the four vunerabilities/CVEs fixed in ASUS 385_20630 are also fixed in Merlin 384.19?
Does this mean the four vunerabilities/CVEs fixed in ASUS 385_20630 are also fixed in Merlin 384.19?
ASUS RT-AC66U B1 Firmware version 3.0.0.4.385.20630
Security update
- Fixed CVE-2020-12695 (CallStranger)
- Fixed Reflected XSS vulnerability.
- Fixed Directory traversal vulnerability.
- Fixed CVE-2017-15653.
SomeWhereOverTheRainBow
Part of the Furniture
Don,t know if any one has mentioned this yet, after updating to 384.19 on my RTAX88U, my router continues to advertise there is a new firmware update when there isn't.
dave14305
Part of the Furniture
Only if the fixes were in the non-closed portion of the AC86U 384.81992 GPL. The rest of the AC68U is still running binary blobs from 385_20490, except for the mentioned bwdpi components, which is only a small piece of the binary goodness needed. ASUS hasn’t released a 68U GPL in a while.
At least that’s what I think is happening.
Upgraded my AC68U yesterday.
No Problems - all running well (about 20 connected devices - all but 1 one wifi).
I noticed that Adaptive QoS (with FlexQoS) is responding quicker than before to limit multi-stream download spikes (e.g. non secure dslreports speedtest) so the short period of buffer bloat during ramp up are significantly reduced. I suspect that is part of bwdpi components from 385_20630 and a welcome improvement.
No Problems - all running well (about 20 connected devices - all but 1 one wifi).
I noticed that Adaptive QoS (with FlexQoS) is responding quicker than before to limit multi-stream download spikes (e.g. non secure dslreports speedtest) so the short period of buffer bloat during ramp up are significantly reduced. I suspect that is part of bwdpi components from 385_20630 and a welcome improvement.
taffeys
Regular Contributor
Upgraded both my AC86U router and AC3100 access point today. Only issue I see so far is the AC3100 now has the yellow flashing icon and "Your router is running low on free JFFS storage..." warning. Rebooted it twice with Format JFFS partition at next boot enabled but that didn't help. This AP is not running any add-ons. JFFS custom scripts and configs are not enabled. The Tools - Sys Info shows plenty of available memory. Any thoughts or ideas?
Last edited:
shabbs
Very Senior Member
Your current version is showing an Asus version, not Merlin. Merlin version would be: 384.19_beta1
SomeWhereOverTheRainBow
Part of the Furniture
No i didnt include the beta part in the screen shot.
I happened to get a brand new RT-AX88U this week, decided upon that model specifically because of RMerlin's support for it (I'd been using a Netgear with the XVortex port of Merlin's asuswrt port) so it was out of the box factory fresh with 384.19_beta1 thrown on top. I ran into one issue which may be beta related, but more likely to be "my" fault and resulted in a "oh no, I broke it" experience.
It had barely been configured; it was not connected to my WAN, just sitting on my desk being set up. I'd gone through the wizard and got as far as the WiFi set-up for 2Ghz and 5Ghz networks, but other than that, had only got as far as setting the https listener and adding my SSH keys.
Somewhere along the way, with making minor config changes, it needed a reboot. When it did, it got stuck/wedged. Four lights on the front, one red, and nothing further. No icmp, no ssh, no http(s). Couldn't use it. Tried recycling the power multiple times. Nothing. Mild moment of panic before reading about the WPS button hard reset / factory reset, and, thankfully that worked, and returned me back to 384.19_beta1 unconfigured.
What I think did it, and it's a long shot that I'm not going to repeat: I had used the ō character in the 5Ghz WiFi name.
Initially, this didn't seem to cause any issues, as the network came up, and my iPhone saw it just fine. However, it was about the only truly non-standard thing I did, and as I was navigating around the configuration, I did see, somewhere, that the UI had escaped the ō character (\0whatever), and had done so for the entire network name. I am wondering if during the reboot when those characters were read out of nvram for maybe bringing up the WiFi that that's what caused the hard hang. I have no proof, it's just really one of the only things that I'd managed to configure. Needless to say, when I got going again, I made the ō just an o, and I've had no issues. Don't know if this is beta related or not, but thought I'd at least mention the hard-hang.
It had barely been configured; it was not connected to my WAN, just sitting on my desk being set up. I'd gone through the wizard and got as far as the WiFi set-up for 2Ghz and 5Ghz networks, but other than that, had only got as far as setting the https listener and adding my SSH keys.
Somewhere along the way, with making minor config changes, it needed a reboot. When it did, it got stuck/wedged. Four lights on the front, one red, and nothing further. No icmp, no ssh, no http(s). Couldn't use it. Tried recycling the power multiple times. Nothing. Mild moment of panic before reading about the WPS button hard reset / factory reset, and, thankfully that worked, and returned me back to 384.19_beta1 unconfigured.
What I think did it, and it's a long shot that I'm not going to repeat: I had used the ō character in the 5Ghz WiFi name.
Initially, this didn't seem to cause any issues, as the network came up, and my iPhone saw it just fine. However, it was about the only truly non-standard thing I did, and as I was navigating around the configuration, I did see, somewhere, that the UI had escaped the ō character (\0whatever), and had done so for the entire network name. I am wondering if during the reboot when those characters were read out of nvram for maybe bringing up the WiFi that that's what caused the hard hang. I have no proof, it's just really one of the only things that I'd managed to configure. Needless to say, when I got going again, I made the ō just an o, and I've had no issues. Don't know if this is beta related or not, but thought I'd at least mention the hard-hang.
L&LD
Part of the Furniture
@honu, your theory may be correct (I don't know). But what I do know is that after flashing to RMerlin firmware, a full reset to factory defaults is required, for the router to 'see' and effectively use its expected defaults.
While you may have performed the reset and got the router to a usable state, you may want to bookmark the following link for future 'hiccups'. Specifically, the M&M Config and the Nuclear Reset guides.
www.snbforums.com
While you may have performed the reset and got the router to a usable state, you may want to bookmark the following link for future 'hiccups'. Specifically, the M&M Config and the Nuclear Reset guides.
Troubleshooting 101 Asus/RMerlin Routers 2020
Top 10 Simple Asus/RMerlin firmware powered Router Troubleshooting steps to try first: NOTE: Although this is for Asus/RMerlin-firmware powered routers, the steps below may be relevant to all routers, to get to a quick fix for common symptoms. Check that the router’s System Time is accurate on...
www.snbforums.com
RAH-66
Senior Member
To do this, this thread
- Status
Similar threads
Similar threads
Similar threads
-
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices- Started by RMerlin
- Replies: 70
-
-
-
Beta Asuswrt-Merlin 3006.102.1 Beta is now available for WIfi 7 devices
- Started by RMerlin
- Replies: 97
-
-
Beta Asuswrt-Merlin 386.13 beta is now available for AC models
- Started by RMerlin
- Replies: 32
-
-
-
Anyone else having issues trying to flash the newest merlin (stable or beta) to the GT-0AXE11000?
- Started by superdeleted
- Replies: 4
-
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
- Started by RMerlin
- Replies: 57