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!

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.
Well, I don't have any upnp device connected to router.
 
Well, I don't have any upnp device connected to router.
some devices use them like computers that have the feature turned on as apart of network features for communication on the network. -- you wouldn't know if it was on or off unless you have physically gone and disabled them with inside the computer itself. you can troubleshoot the issue by looking at your connections log to determine what device has that local IP and choose to disable upnp if you have the option to on the device. your alternative is disabling upnp feature on the Wan internet connections page.. then no upnp will be able to connect. note some of your devices might rely on this though for some features as apart of their design.
 
upload_2019-6-5_1-2-21.png


upload_2019-6-5_1-2-47.png
 
upload_2019-6-5_1-6-54.png

A good example of something that uses this type of connection to function
upload_2019-6-5_1-4-57.png

deluge torrent
 
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

So some device with the local IP 192.168.2.99 connection timed out at port 2869 if you look at your syslogs tab there is a page called Port Forwarding and at the very bottom of that page you can see all devices making upnp connections, and sometimes the router can also tell you what program or device is causing it.
 
Where is the apply button for Portforwarding :/ saw this now.
Version: 384.11_2
AC66u B1
you no longer need it. the port forward list is linked to adding in real time, once you add it, it auto applys now.
 
I am considering getting a AC-86u. Is it as simple as downloading the most recent firmware and flashing said file from computer? Or does it require a specific asus firmware before I flash the first time?
 
I am considering getting a AC-86u. Is it as simple as downloading the most recent firmware and flashing said file from computer? Or does it require a specific asus firmware before I flash the first time?
i would simply let the router up date to the most recent stock firmware, then install the most recent merlin firmware, then factory reset clearing the nvram, then you should be good to go with your setup.
 
i would simply let the router up date to the most recent stock firmware, then install the most recent merlin firmware, then factory reset clearing the nvram, then you should be good to go with your setup.

Ok and clearing the nvram is done through the UI? Or was that a command I ran in the command line [emoji848]

Thanks btw!
 
Ok and clearing the nvram is done through the UI? Or was that a command I ran in the command line [emoji848]

Thanks btw!

Even with a brand new router, I would flash the firmware you want to use and then do a full reset to factory defaults. The M&M Config and the other links in my signature below are what I would suggest ensuring you are starting with a good/known router and network state.

https://www.snbforums.com/threads/major-issues-w-rt-ac86u.56342/page-4#post-495710

The link above outlines a nuclear reset (which was recommended for that poster to rule out hardware faults on his router). :)
 
With a new router, I do not think it's really important at the moment to clear NVRAM. I would simply try first flashing with the last firwmare of your choice(384.11_2, 384.12 alpha2,or with Asuswrt) , factory reset with the initialize box check and reconfig from the beginning.
Personally, I have an AC86 for almost 1 year, I never needed to erase nvram and everything still works perfectly and I flashed at least 100 times this router for my personal code compilation

Hint: if you run a VPN , this router is a beast and you should use merlin fw :)
 
Last edited:
So some device with the local IP 192.168.2.99 connection timed out at port 2869 if you look at your syslogs tab there is a page called Port Forwarding and at the very bottom of that page you can see all devices making upnp connections, and sometimes the router can also tell you what program or device is causing it.

It's saying

No active UPNP forward.


I got it yesterday again

Code:
Jun  5 17:24:53 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:24:57 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:25:37 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:25:37 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:25:37 miniupnpd[25443]: upnpevents_processfds: 0x2c2f8, remove subscriber uuid:e7f89ef0-5802-4549-a6c6-ddec826c9ee9 after an ERROR cb: http://192.168.2.99:2869/upnp/eventing/qomeuckdhc
Jun  5 17:29:50 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:29:55 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:30:07 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:30:07 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:30:13 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:30:13 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:30:13 miniupnpd[25443]: upnpevents_processfds: 0x2d240, remove subscriber uuid:6e149651-23ca-4535-961f-16712c11f1c5 after an ERROR cb: http://192.168.2.99:2869/upnp/eventing/frvnnyinpp
Jun  5 17:37:42 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:37:44 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:37:44 miniupnpd[25443]: upnpevents_processfds: 0x2c1e8, remove subscriber uuid:886605b8-1ba2-4329-90a9-acc147abe605 after an ERROR cb: http://192.168.2.99:2869/upnp/eventing/ukkgjganje
Jun  5 17:38:35 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:38:35 miniupnpd[25443]: upnp_event_process_notify: connect(192.168.2.99:2869): Connection timed out
Jun  5 17:38:35 miniupnpd[25443]: upnpevents_processfds: 0x2c1e8, remove subscriber uuid:49f9aa28-59c4-45d9-8385-663ae75bc5f8 after an ERROR cb: http://192.168.2.99:2869/upnp/eventing/fartznxmaf
 
Anyone else having issues with Wifi stability and/or disconnects?

Since moving from 384.10 to 384.11 my Wifi is WAY unstable.

My wifi security cams were rock solid on .10 but jump on/off the network with .11
I have 3 AC68P's (1 Router + 2 AP mode) same SSIDs per radio. 5.0 GHz seems more stable than 2.4
I watch WifiMan android app and see APs "pop" on/off the channel grid even when the signal is -60 to -70 while others much weaker signals (-85 to -90) from neighbors are shown
The channels are not overlapping and on both radios the strongest neighbor is -80 on any channel... and there are not many close by anyway.

any ideas?
 
Anyone else having issues with Wifi stability and/or disconnects?

Since moving from 384.10 to 384.11 my Wifi is WAY unstable.

My wifi security cams were rock solid on .10 but jump on/off the network with .11
I have 3 AC68P's (1 Router + 2 AP mode) same SSIDs per radio. 5.0 GHz seems more stable than 2.4
I watch WifiMan android app and see APs "pop" on/off the channel grid even when the signal is -60 to -70 while others much weaker signals (-85 to -90) from neighbors are shown
The channels are not overlapping and on both radios the strongest neighbor is -80 on any channel... and there are not many close by anyway.

any ideas?

I think my cameras are doing the same thing. Before this router I had RT55U Asus, and it was more stable then on this router with this firmware on it, same position same place router stands as previous one. Plus whats funny this router have 4 antennas and that RT55U had 2, and hardware was weaker a lot.
 
Last edited:
Okay so I'm getting delay start issues on OpenVPN client, whenever I reboot the router or manually restart the OpenVPN client it takes approximately 5 minutes to connect and before that it just sits there doing nothing ( not even trying to connect )

I've found these lines in the log which might be helpful (Check the timestamps):

Code:
Jun 12 04:19:36 rc_service: httpds 885:notify_rc start_vpnclient1
Jun 12 04:19:36 rc_service: waitting "restart_vpnclient1;restart_dnsmasq" via httpds ...   ( Also looks like a typo in the code as well "waitting"
Jun 12 04:19:51 rc_service: skip the event: start_vpnclient1.
Jun 12 04:24:09 kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Jun 12 04:25:19 ovpn-client1[6155]: OpenVPN 2.4.7 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on May 18 2019

Checked on two different providers so I dont believe its a service provider issue.

Important Information:
Asus RT-AC86U
Firmware Version:384.11_2
OpenVpn Providers tried: zpn.im and windscribe.com
 
Updated ac86 to 11.2 and now vpn server doesn’t route to vpn client anymore. Any idea to fix this please?
 

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