What's new

[Beta] Asuswrt-Merlin 384.7 Beta is now 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!

Status
Not open for further replies.
USB 3.0 SanDisk Ultra 32 GB (new) recognized in USB3 port when USB Mode 2.0 is selected but not when USB Mode 3.0 is selected. Have tried with "default" FAT 32 format and EXT 3 format. Neither worked. Tried two other USB 3.0 SanDisk drives with the same result. RT-AC66U_B1 with RT-AC68U 384-7 B2 firmware. Had loaded Entware on USB 2.0 and decided to try a USB 3.0 stick. Also, the external USB2.0 drive in the back port goes wonky when I switch the front USB to 3.0. Suggestions?

I'm having the exact same issues with the Sandisk 32 GB USB 3.0 Ultra Flair. Tried everything after seeing positive speed test results here, but I've given up on it. Support for USB 3.0 drives is terrible.
 
Last edited by a moderator:
Ditto the above post. USB3 support is awful on stock or merlin f/w.:(
 
I edited my IP and ddns host out.

Then I don`t understand what your post was about, sorry. That log shows a perfectly normal DDNS update to me.
 
I have an IP Camera (Foscam 8910W) and let it run in uPnP mode to open port. It worked flawlessly with old N66 and AC68U, old firmwares, new firmwares and 384.5 etc...

However, on 384.6 and 384.7b, it couldn't work. FYI, I have tried flashing, resetting, rebooting many times. It always worked with 384.5 and previous firmwares, but whenever the router ran 384.6-384.7b, it stopped working (its Camera Admin page would said uPnP got errors).

Maybe there is some new bug regarding uPnP? Obviously I can set the portforwarding, but maybe that was some bug, so I'd think I'd report it here.
 
I have an IP Camera (Foscam 8910W) and let it run in uPnP mode to open port. It worked flawlessly with old N66 and AC68U, old firmwares, new firmwares and 384.5 etc...

However, on 384.6 and 384.7b, it couldn't work. FYI, I have tried flashing, resetting, rebooting many times. It always worked with 384.5 and previous firmwares, but whenever the router ran 384.6-384.7b, it stopped working (its Camera Admin page would said uPnP got errors).

Maybe there is some new bug regarding uPnP? Obviously I can set the portforwarding, but maybe that was some bug, so I'd think I'd report it here.

What port are you trying to forward? By default the router will refuse to forward port numbers below 1024, for security reasons. You have to explicitly allow it on the WAN page first.
 
I'm having the exact same issues with the Sandisk 32 GB USB 3.0 Ultra Flair. Tried everything after seeing positive speed test results here, but I've given up on it. Support for USB 3.0 drives is terrible.

I had a similar issue with sandisk 16 gb usb mini. at first it worked flawlessly, then a few months back one of two partitions were undetected; i inserted it into usb2.0, problem solved. i haven't switched it back since but will test and see eventually.
 
Beta 2 working really good ! DDNS(Asus internal) and vpn server stable :)
Only thing i have noticed is the time format in Parental Controls Time Scheduling it`s stuck in am pm, cant change to 24h format
Using Sandisk Ultra 16Gb usb 3.0 working fine
 
What port are you trying to forward? By default the router will refuse to forward port numbers below 1024, for security reasons. You have to explicitly allow it on the WAN page first.
I set it run on 8080. As I said, the camera would run fine on the firmwares I tried if I set the portforwarding rule manually.
- On 384.6 and 384.7b (I have not tried with new stock firmwares maybe from 20308), it couldn't work using uPnP mode.
- On 384.5, 384.3, 380.70, 380.66 and corresponding stock firmwares etc..., uPnp mode worked perfectly.
 
Last edited:
I set it run on 8080. As I said, the camera would run fine on the firmwares I tried if I set the portforwarding rule manually.
- On 384.6 and 384.7b (I have not tried with new stock firmwares maybe from 20308), it couldn't work using uPnP mode.
- On 384.5, 384.3, 380.70, 380.66 and corresponding stock firmwares etc..., uPnp mode worked perfectly.

Try a different port, in case that port is already in use (possibly by AiCloud).

Also note that UPNP will now refuse to forward any port defined as a port forward, to prevent conflicts. Check the content of /etc/upnp/config to see the list of denied ports.
 
384.7 Beta 3 is now available. This primarily merges inadyn 2.5 (which contains a number of fixes and enhancements used by Asuswrt-Merlin, such as proper support for all.dnsomatic.com and built-in selfhost.de support).

Changes since beta 2:

Code:
0f4466852 rc: ddns: rely on inadyn's built-in CA certs location
2d94aa34d inadyn: hardcode SSL CA certs location
ed435437a Updated documentation
38c2be87f rc: dnsmasq: reject wpad hostname (protect against VU#598349)
3a5817d59 rc: ddns: roll AsusDDNS into main service case; minor cleanups
6de7827d7 rc: ddns: switch to built-in selfhost.de support added with inadyn 2.5
f44c37ed3 inadyn: updated to 2.5
4d8117f67 webui: fix clientlist layout on DNSFilter page; remove destIP field reference
c768123e5 rc: webui: dnsfilter: Add Quad9 to DNSFilter services; use https for DNSFilter services homepage links
34d4a9d1a rc: webui: dnsfilter: Remove discontinued Norton Safe services
a7b1b6928 rc: dnsfilter: replace Norton DNSFilter services with OpenDNS Family at boot time
7354abc68 Bumped version to beta 3
f3cc92125 inadyn: Don't try to resolve hostname for default@tunnelbroker.net service
6e74cf455 inadyn: fix previous commit, we were checking the IP instead of the hostname
768ae8074 inadyn: don't try to resolve all.dnsomatic.com
be09a6745 inadyn: recognize "nochg" responses in generic plugin (fixes selfhost.de)
bf829f6ac rc: inadyn: don't provide cache-dir location at runtime, it's now implemented in inadyn
97ece3de5 inadyn: change default cache location to /tmp/inadyn.cache for Asuswrt
 
Done. Flashed with no problems.;)
 
Please do one last round of tests on DDNS, to confirm that everything is good now and ready for a final release.
 
Dirty flashed over beta1. Noticed in the UI the server certificate has some SAN entries now.... i'm double NATed using the external method to get the IP, using No-IP service. Imported my pixelserv cert to use previously....
Code:
Status :    OK
Issued to :    10.10.10.1
SAN :    10.10.10.1 router.asus.com RT-AC68U-4690 RT-AC68U-4690.xxxxx.net xxxxxxx.hopto.org
Issued by :    10.10.10.1
Expires on :    2028/9/27
 
Last edited:
A comment on the WebUi here... using double NAT the DDNS page still mentions "The wireless router currently uses a private WAN IP address. This router may be in the multiple-NAT environment and DDNS service cannot work in this environment." which isn't strictly true anymore. Perhaps that could be changed to something more relevant. Additionally if the Lets Encrypt generate cert can only be used by ASUS DDNS service, then shouldn't the radio button for it be removed from other services?
 
Status
Not open for further replies.

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