Release [Beta] Asuswrt-Merlin 384.19 beta is now available

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
Status
Not open for further replies.

dave14305

Part of the Furniture
Probably already been answered but how in gods green earth can i get rid of these in my history log

---

8 00:15:59 kernel: DROP IN=ppp0 OUT= MAC= SRC=37.49.225.166 DST=51.148.166.159 LEN=49 TOS=0x00 PREC=0x00 TTL=246 ID=54321 PROTO=UDP SPT=60408 DPT=5683 LEN=29
Aug 8 00:16:01 kernel: DROP IN=ppp0 OUT= MAC= SRC=45.129.33.40 DST=51.148.166.159 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=2170 PROTO=TCP SPT=58618 DPT=30916 SEQ=1319360033 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0

-----------------------

I have about a billion of them.... :/
Specifically, set "Logged packets type" to None on the Firewall tab, unless you're using Skynet also.
 

Xentrk

Part of the Furniture
Probably already been answered but how in gods green earth can i get rid of these in my history log

---

8 00:15:59 kernel: DROP IN=ppp0 OUT= MAC= SRC=37.49.225.166 DST=51.148.166.159 LEN=49 TOS=0x00 PREC=0x00 TTL=246 ID=54321 PROTO=UDP SPT=60408 DPT=5683 LEN=29
Aug 8 00:16:01 kernel: DROP IN=ppp0 OUT= MAC= SRC=45.129.33.40 DST=51.148.166.159 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=2170 PROTO=TCP SPT=58618 DPT=30916 SEQ=1319360033 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Aug 8 00:16:20 kernel: DROP IN=ppp0 OUT= MAC= SRC=125.64.94.130 DST=51.148.166.159 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=54321 PROTO=TCP SPT=35807 DPT=110 SEQ=1769365306 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0
Aug 8 00:16:31 kernel: DROP IN=ppp0 OUT= MAC= SRC=193.32.161.149 DST=51.148.166.159 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=45133 PROTO=TCP SPT=51261 DPT=65508 SEQ=2599151926 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Aug 8 00:16:32 kernel: DROP IN=ppp0 OUT= MAC= SRC=81.98.81.101 DST=51.148.166.159 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=45899 DF PROTO=TCP SPT=23061 DPT=7680 SEQ=3058404864 ACK=0 WINDOW=65472 RES=0x00 SYN URGP=0 OPT (0204055401010402)
Aug 8 00:16:33 kernel: DROP IN=ppp0 OUT= MAC= SRC=81.98.81.101 DST=51.148.166.159 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=45900 DF PROTO=TCP SPT=23061 DPT=7680 SEQ=3058404864 ACK=0 WINDOW=65472 RES=0x00 SYN URGP=0 OPT (0204055401010402)
Aug 8 00:16:35 kernel: DROP IN=ppp0 OUT= MAC= SRC=81.98.81.101 DST=51.148.166.159 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=45901 DF PROTO=TCP SPT=23061 DPT=7680 SEQ=3058404864 ACK=0 WINDOW=65472 RES=0x00 SYN URGP=0 OPT (0204055401010402)
Aug 8 00:16:39 kernel: DROP IN=ppp0 OUT= MAC= SRC=81.98.81.101 DST=51.148.166.159 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=45902 DF PROTO=TCP SPT=23061 DPT=7680 SEQ=3058404864 ACK=0 WINDOW=65472 RES=0x00 SYN URGP=0 OPT (0204055401010402)
Aug 8 00:16:44 kernel: DROP IN=ppp0 OUT= MAC= SRC=45.129.33.24 DST=51.148.166.159 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=52140 PROTO=TCP SPT=56008 DPT=21828 SEQ=3985651831 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Aug 8 00:16:47 kernel: DROP IN=ppp0 OUT= MAC= SRC=81.98.81.101 DST=51.148.166.159 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=45903 DF PROTO=TCP SPT=23061 DPT=7680 SEQ=3058404864 ACK=0 WINDOW=65472 RES=0x00 SYN URGP=0 OPT (0204055401010402)
Aug 8 00:16:56 kernel: DROP IN=ppp0 OUT= MAC= SRC=195.54.160.53 DST=51.148.166.159 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=44560 PROTO=TCP SPT=57467 DPT=45007 SEQ=2620303168 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Aug 8 00:17:00 kernel: DROP IN=ppp0 OUT= MAC= SRC=125.212.217.214 DST=51.148.166.159 LEN=44 TOS=0x00 PREC=0x00 TTL=110 ID=16979 PROTO=TCP SPT=13944 DPT=1010 SEQ=239357119 ACK=0 WINDOW=22760 RES=0x00 SYN URGP=0 OPT (020405B4)
Aug 8 00:17:45 kernel: DROP IN=ppp0 OUT= MAC= SRC=195.54.160.53 DST=51.148.166.159 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=24160 PROTO=TCP SPT=57467 DPT=6622 SEQ=2125783329 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0

-----------------------

I have about a billion of them.... :/
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
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.
They're the standard firewall logs. Skynet adds "blocked - inbound" etc. to the log entry
 

Jeffrey Young

Regular Contributor
Check your logging level on your firewall setting. Looks like you set to log dropped firewall hits. Set the level to none.
 

Natty

Occasional Visitor
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?
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

Very Senior Member
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.
1596899507881.png

1596899644369.png
 

dave14305

Part of the Furniture
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?
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.
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.
 

geobernd

Occasional Visitor
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.
 

chris.at

Regular Contributor
I installed this beta on 68U right now and LAN to WLAN (both directions, streaming from/to nas) traffic is still counted as internet up/down traffic on "Network Map" - "Internet Traffic" bars (first noticed on 384.18).
 

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

Regular Contributor
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.
Your current version is showing an Asus version, not Merlin. Merlin version would be: 384.19_beta1
 

Tom Ames

Occasional Visitor
Dirty flashed my AC86 today. After several unsuccessful attempts, I formatted the jffs partition and it updated on the next attempt. First time I've had any real problems updating Merlin firmware. Everything seems to be humming along now.
 

honu

New Around Here
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.
 

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.

 
Status
Not open for further replies.

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