[Release] Asuswrt-Merlin 384.11 is available

[L&LD]

Thank you or I will do a factory reset after an upgrade.

Yes, after flashing the firmware you want.

Look in my signature for the M&M Config link if you do decide to do a full reset.

 

[SOEJSU]

Hi, i know it's a nooby question but how to upgrade to 384.11_2 ? It isn't accepting the .trx file. I have 384.11 at the moment

 

[Quoc Huynh]

Do you have a RT-68U or RT-86U? As I know, the 86U or higher has different architecture, so it does not accept .trx file like the 68U.

* RT-68U firmware:
https://sourceforge.net/projects/asuswrt-merlin/files/RT-AC68U/Release/

* RT-86U firmware:
https://sourceforge.net/projects/asuswrt-merlin/files/RT-AC86U/Release/

 

[MDM]

Hi, i know it's a nooby question but how to upgrade to 384.11_2 ? It isn't accepting the .trx file. I have 384.11 at the moment

Take out USB if any, reboot, and try again.
IF you have correct FW, as @Quoc Huynh said...

 

[skeal]

Hi, i know it's a nooby question but how to upgrade to 384.11_2 ? It isn't accepting the .trx file. I have 384.11 at the moment

What router do you have? Is it a TM-1900? That model isn't supported here.

 

[doczenith1]

What router do you have? Is it a TM-1900? That model isn't supported here.

If he already has 384.11 then there is no way it's a TM-1900.

Edit: he most likely doesn't have a TM-1900. And if does and got 384.11 on it then he would for certain know how to get to _2

 

[L&LD]

If he already has 384.11 then there is no way it's a TM-1900.

Never say never.

 

[SOEJSU]

Sorry my mistake! I have an AC86U and accidentally downloaded the firmware for AC68U.. Noobie mistakes. Now i have the newest firmware on my router - thank you!

 

[AntonK]

Sorry my mistake! I have an AC86U and accidentally downloaded the firmware for AC68U.. Noobie mistakes. Now i have the newest firmware on my router - thank you!

Been there, done that!

Best,
Anton

 

[ollimoe]

https://www.snbforums.com/threads/a...d-forks-on-non-asus-devices-is-illegal.44636/

 

[QuikSilver]

I had to go down to firmware 384.10_2 because on my nighthawk r7000 network devices would not work on anything newer. Any ideas or settings i should check after updating ? I did try resetting the entire router to scratch and starting over a few times as well as a few reboots, that didn't help.

Your device is a netgear unit not Asus unit. Reading the forum rules/stickies would have lead you to this thread.

https://www.snbforums.com/threads/a...d-forks-on-non-asus-devices-is-illegal.44636/

 

[reckless]

Didnt realize my mistake deleted.

 

[nakti]

Yes, after flashing the firmware you want.

Look in my signature for the M&M Config link if you do decide to do a full reset.

Thank you. Btw is NVRAM: 51922 / 65536 bytes normal?
And I also get: nvram: consolidating space! in the log

 

[scjr]

Thank you. Btw is NVRAM: 51922 / 65536 bytes normal?
And I also get: nvram: consolidating space! in the log

Both normal.

 

[nakti]

Both normal.

Thank you,

 

[nakti]

I get kernel: [BLOCKED - INBOUND] IN=eth0 OUT all the time?
The ip starts with 81.22. which is russian but how to clear so that I dont get it full in the log

 

[L&LD]

I get kernel: [BLOCKED - INBOUND] IN=eth0 OUT all the time?
The ip starts with 81.22. which is russian but how to clear so that I dont get it full in the log

Are you using Skynet? You need to disable logging, I think.

 

[nakti]

Are you using Skynet? You need to disable logging, I think.

Yes im using Skynet. I will check this thanks

 

[Thermaltake]

I got these errors today, anyone have idea what could that be and why they appear ?

Jun  4 16:40:01 rc_service: httpd 311:notify_rc restart_dnsfilter
Jun  4 16:40:02 miniupnpd[25332]: shutting down MiniUPnPd
Jun  4 16:40:02 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Jun  4 16:40:03 miniupnpd[25443]: HTTP listening on port 33686
Jun  4 16:40:03 miniupnpd[25443]: Listening for NAT-PMP/PCP traffic on port 5351
Jun  4 16:41:07 rc_service: httpd 311:notify_rc restart_wlcscan
Jun  4 18:26:27 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  4 18:26:27 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  4 18:26:27 miniupnpd[25443]: upnpevents_processfds: 0x2c1e8, remove subscriber uuid:4f81e4dd-4ea3-41b3-8400-01bf92a97c65 after an ERROR cb: http://192.168.2.99:2869/upnp/eventing/vddfzgnmkr

 

[Swistheater]

I got these errors today, anyone have idea what could that be and why they appear ?

Jun  4 16:40:01 rc_service: httpd 311:notify_rc restart_dnsfilter
Jun  4 16:40:02 miniupnpd[25332]: shutting down MiniUPnPd
Jun  4 16:40:02 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Jun  4 16:40:03 miniupnpd[25443]: HTTP listening on port 33686
Jun  4 16:40:03 miniupnpd[25443]: Listening for NAT-PMP/PCP traffic on port 5351
Jun  4 16:41:07 rc_service: httpd 311:notify_rc restart_wlcscan
Jun  4 18:26:27 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  4 18:26:27 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  4 18:26:27 miniupnpd[25443]: upnpevents_processfds: 0x2c1e8, remove subscriber uuid:4f81e4dd-4ea3-41b3-8400-01bf92a97c65 after an ERROR cb: http://192.168.2.99:2869/upnp/eventing/vddfzgnmkr

That is normal for inactive connections on upnpd. The upnpd will clear out the connection if it is inactive for too long, this is a good thing and is normal behavior, unless you are on a device that is active but this is happening. If you notice the time difference between when it connects and loses connection is like a few hours. Which tells me it is probably a device that was used for a couple of hours and then turned off.