What's new

[Release] Asuswrt-Merlin 384.11 is available

  • 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!

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.
 
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
 
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.
 
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/
 
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
 
Last edited:
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
 
Last edited:
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. :)
 
I got these errors today, anyone have idea what could that be and why they appear ?

Code:
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
 
I got these errors today, anyone have idea what could that be and why they appear ?

Code:
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.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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