What's new

[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

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

Hey John! Great firmware working well as usual. I am getting this in my logs over and over- is it an issue or should I just ignore it?

Mar 17 17:37:46 watchdog: restart httpd - SSL, error detected or process not responding (51)
Mar 17 17:37:46 rc_service: watchdog 411:notify_rc stop_httpd
Mar 17 17:37:46 rc_service: watchdog 411:notify_rc start_httpd
Mar 17 17:37:46 rc_service: waiting "stop_httpd" via watchdog ...
Mar 17 17:37:47 httpd: start httpd - SSL
Mar 17 17:38:16 watchdog: restart httpd - SSL, error detected or process not responding (51)
Mar 17 17:38:16 rc_service: watchdog 411:notify_rc stop_httpd
Mar 17 17:38:16 rc_service: watchdog 411:notify_rc start_httpd
Mar 17 17:38:16 rc_service: waiting "stop_httpd" via watchdog ...
Mar 17 17:38:17 httpd: start httpd - SSL
 
Hey John! Great firmware working well as usual. I am getting this in my logs over and over- is it an issue or should I just ignore it?

Mar 17 17:37:46 watchdog: restart httpd - SSL, error detected or process not responding (51)
Mar 17 17:37:46 rc_service: watchdog 411:notify_rc stop_httpd
Mar 17 17:37:46 rc_service: watchdog 411:notify_rc start_httpd
Mar 17 17:37:46 rc_service: waiting "stop_httpd" via watchdog ...
Mar 17 17:37:47 httpd: start httpd - SSL
Mar 17 17:38:16 watchdog: restart httpd - SSL, error detected or process not responding (51)
Mar 17 17:38:16 rc_service: watchdog 411:notify_rc stop_httpd
Mar 17 17:38:16 rc_service: watchdog 411:notify_rc start_httpd
Mar 17 17:38:16 rc_service: waiting "stop_httpd" via watchdog ...
Mar 17 17:38:17 httpd: start httpd - SSL
No, not OK. Are you using a self-generated cert for your https access? and if so, did you put a copy of it in /etc/cert.pem?

CURLE_PEER_FAILED_VERIFICATION (51)
The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK.
 
Didn't help. Never used this IP before so couldn't have been cached anyway. Never had this problem before in any previous firmware versions (including 17 beta).
Funny thing is that if I go through a VPN both DNS and IP works.
Have a theory. Do you have QoS active? If so, try this command on the router and see if it resolves the problem.

service restart_firewall
 
I seem to be having issues with a SAMBA share on an NTFS partition coming back and being visible under windows after a router reboot. I have to go into the SAMBA share on the router and disable/enable the guest login option for the share to appear and be accessible. Partition sda1 is ext3 and partition sda2 is NTFS. I can see sda1 upon router reboot in windows but not sda2 until the enable/disable option is invoked. Please see the system log after a reboot to see if there's anything I'm missing. I can duplicate this everytime after a reboot. thanks

Dec 31 19:00:34 Samba Server: daemon is started
Dec 31 19:00:34 custom script: Running /jffs/scripts/services-start
Dec 31 19:00:34 dnsmasq-dhcp[393]: DHCPDISCOVER(br0) 34:db:fd:5d:53:a9
Dec 31 19:00:34 dnsmasq-dhcp[393]: DHCPOFFER(br0) 192.168.0.18 34:db:fd:5d:53:a9
Dec 31 19:00:35 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.0.18 34:db:fd:5d:53:a9
Dec 31 19:00:35 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.0.18 34:db:fd:5d:53:a9 SPA112
Dec 31 19:00:36 dnsmasq[393]: read /etc/hosts - 6 addresses
Dec 31 19:00:36 dnsmasq[393]: read /etc/hosts.dnsmasq - 15 addresses
Dec 31 19:00:36 dnsmasq-dhcp[393]: read /etc/ethers - 15 addresses
Dec 31 19:00:36 kernel: Ebtables v2.0 registered
Dec 31 19:00:36 dnsmasq[393]: read /etc/hosts - 6 addresses
Dec 31 19:00:36 dnsmasq[393]: read /etc/hosts.dnsmasq - 15 addresses
Dec 31 19:00:36 dnsmasq-dhcp[393]: read /etc/ethers - 15 addresses
Dec 31 19:00:36 dnsmasq[393]: using nameserver 206.248.154.22#53
Dec 31 19:00:36 dnsmasq[393]: using nameserver 206.248.154.170#53
Dec 31 19:00:36 rc_service: udhcpc 476:notify_rc start_firewall
Dec 31 19:00:36 rc_service: waiting "restart_nasapps" via ...
Dec 31 19:00:36 NFS Server: daemon is stopped
Dec 31 19:00:36 MediaServer: daemon is stopped
Dec 31 19:00:37 FTP Server: daemon is stopped
Dec 31 19:00:37 Samba Server: smb daemon is stopped
Dec 31 19:00:37 Samba Server: daemon is started
Dec 31 19:00:37 rc_service: udhcpc 476:notify_rc stop_upnp
Dec 31 19:00:37 rc_service: waiting "start_firewall" via udhcpc ...
Dec 31 19:00:38 kernel: ufsd: sda2 without journal
Dec 31 19:00:38 hotplug[342]: USB ntfs fs at /dev/sda2 mounted on /tmp/mnt/sda2
Dec 31 19:00:38 WAN Connection: WAN was restored.
Dec 31 19:00:38 start_nat_rules: apply the nat_rules (/tmp/nat_rules)!
Dec 31 19:00:38 custom script: Running /jffs/scripts/post-mount (args: /tmp/mnt/sda2)
Dec 31 19:00:38 rc_service: hotplug 342:notify_rc restart_nasapps
Dec 31 19:00:38 rc_service: waiting "start_firewall" via udhcpc ...
Dec 31 19:00:39 dnsmasq-dhcp[393]: DHCPDISCOVER(br0) 192.168.0.24 30:cd:a7:a4:98:e2
Dec 31 19:00:39 dnsmasq-dhcp[393]: DHCPOFFER(br0) 192.168.0.24 30:cd:a7:a4:98:e2
Dec 31 19:00:39 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.0.24 30:cd:a7:a4:98:e2
Dec 31 19:00:39 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.0.24 30:cd:a7:a4:98:e2 SLM2885FW
Dec 31 19:00:42 start_nat_rules: (/tmp/nat_rules) cancelled!
Dec 31 19:00:45 nmbd[530]: [2010/12/31 19:00:45, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113)
Dec 31 19:00:45 nmbd[530]: Samba server RT-AC66U is now a domain master browser for workgroup WORKGROUP on subnet 192.168.0.1
Dec 31 19:00:48 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.0.13 40:30:04:b2:bf:c7
Dec 31 19:00:48 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.0.13 40:30:04:b2:bf:c7 Milenkos-iPad
Dec 31 19:00:49 rc_service: skip the event: restart_nasapps.
Dec 31 19:00:49 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.0.12 70:de:e2:71:71:ed
Dec 31 19:00:49 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.0.12 70:de:e2:71:71:ed Alysons-iPad
Dec 31 19:00:50 admin: Started transmission-daemon from .
Dec 31 19:00:50 start_nat_rules: apply the nat_rules (/tmp/nat_rules_eth0_eth0)!
Dec 31 19:00:50 start_nat_rules: (/tmp/nat_rules_eth0_eth0) success!
Dec 31 19:00:50 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 31 19:00:50 kernel: nf_nat_rtsp v0.6.21 loading
Dec 31 19:00:51 custom script: Running /jffs/scripts/firewall-start (args: eth0)
Dec 31 19:00:51 transmission-daemon[577]: UDP Failed to set receive buffer: requested 4194304, got 237568 (tr-udp.c:84)
Dec 31 19:00:51 transmission-daemon[577]: UDP Failed to set send buffer: requested 1048576, got 237568 (tr-udp.c:95)
Dec 31 19:00:51 rc_service: udhcpc 476:notify_rc start_upnp
Dec 31 19:00:51 rc_service: waiting "stop_upnp" via udhcpc ...
Dec 31 19:00:52 ddns: clear ddns cache file for server/hostname change
Dec 31 19:00:52 ddns update: ez-ipupdate: starting...
Dec 31 19:00:53 miniupnpd[631]: HTTP listening on port 60623
Dec 31 19:00:53 miniupnpd[631]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 31 19:00:53 ddns update: connected to dynupdate.no-ip.com (8.23.224.120) on port 80.
Dec 31 19:00:53 ddns update: request successful
Dec 31 19:00:53 ddns update: asusddns_update: 0
Dec 31 19:00:53 ddns: ddns update ok
Dec 31 19:00:53 rc_service: udhcpc 476:notify_rc start_ntpc
Dec 31 19:00:53 rc_service: udhcpc 476:notify_rc stop_ntpd
Dec 31 19:00:53 dhcp client: bound 192.0.166.204 via 192.0.166.193 during 3600 seconds.
Mar 17 13:09:12 rc_service: ntp 634:notify_rc restart_upnp
Mar 17 13:09:13 miniupnpd[631]: shutting down MiniUPnPd
Mar 17 13:09:13 miniupnpd[643]: HTTP listening on port 51257
Mar 17 13:09:13 miniupnpd[643]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 17 13:09:13 rc_service: ntp 634:notify_rc restart_diskmon
Mar 17 13:09:13 disk monitor: be idle
Mar 17 13:09:20 nmbd[530]: [2016/03/17 13:09:20, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Mar 17 13:09:20 nmbd[530]: Samba name server RT-AC66U is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.1
Mar 17 13:09:20 crond[401]: time disparity of 2739908 minutes detected
Mar 17 13:11:02 HTTP login: login 'admin' failed from 209.167.114.101
Mar 17 13:11:07 HTTP login: login 'admin' successful from 209.167.114.101
Mar 17 13:13:18 rc_service: httpd 394:notify_rc restart_samba_force
Mar 17 12:13:21 Samba Server: smb daemon is stopped
Mar 17 12:13:21 Samba Server: daemon is started
Mar 17 13:13:30 nmbd[680]: [2016/03/17 13:13:30, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113)
Mar 17 13:13:30 nmbd[680]: Samba server RT-AC66U is now a domain master browser for workgroup WORKGROUP on subnet 192.168.0.1
Mar 17 13:13:36 rc_service: httpd 394:notify_rc restart_samba_force
Mar 17 12:13:39 Samba Server: smb daemon is stopped
Mar 17 12:13:39 Samba Server: daemon is started
Mar 17 13:13:48 nmbd[698]: [2016/03/17 13:13:48, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113)
Mar 17 13:13:48 nmbd[698]: Samba server RT-AC66U is now a domain master browser for workgroup WORKGROUP on subnet 192.168.0.1
 
I seem to be having issues with a SAMBA share on an NTFS partition coming back and being visible under windows after a router reboot. I have to go into the SAMBA share on the router and disable/enable the guest login option for the share to appear and be accessible. Partition sda1 is ext3 and partition sda2 is NTFS. I can see sda1 upon router reboot in windows but not sda2 until the enable/disable option is invoked. Please see the system log after a reboot to see if there's anything I'm missing. I can duplicate this everytime after a reboot. thanks
Don't see anything out of the ordinary (I'm assuming the restart_samba_force at the end is you resetting things in the gui).

Is this Windows 10? I just read a post about problems with Windows 10 and Samba....you may want to give this a try (thnx for posting @sfx2000)
http://www.snbforums.com/threads/ext-usb-3-0-hd-access-problem.31057/#post-245362
 
CTF changes affecting 68U also, before I had just on and off, now I can choose between off, level1 and level2. I have kept it off as I want fully functional QoS etc.
 
CTF changes affecting 68U also, before I had just on and off, now I can choose between off, level1 and level2. I have kept it off as I want fully functional QoS etc.
Rev B1? What speed processor.....there was also a bug for a while in the base Asus code where it would say the AC68U supported FA mode (but it really doesn't, unless possibly the B1 rev)
 
Don't see anything out of the ordinary (I'm assuming the restart_samba_force at the end is you resetting things in the gui).

Is this Windows 10? I just read a post about problems with Windows 10 and Samba....you may want to give this a try (thnx for posting @sfx2000)
http://www.snbforums.com/threads/ext-usb-3-0-hd-access-problem.31057/#post-245362
Well I decided to unmount the device and do a file and disk check under Ubuntu. I checked each partition one at a time and it found a minor problem under the ext3 partition which it fixed. Plugged the drive back into the router, powered on the router and voila all is well with both partitions showing up under windows after a router reboot. Sorry guess I should of tried the simple stuff first. Thanks again John for this great firmware. Cheers
 
No, not OK. Are you using a self-generated cert for your https access? and if so, did you put a copy of it in /etc/cert.pem?

CURLE_PEER_FAILED_VERIFICATION (51)
The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK.

Have always just let the router create the cert for https access- and https access to router works despite these errors.

I do use an unconventional set of ip addresses- the router is 10.xxx.xxx.xxx

Also use unconventional port for https access, and only use https access.

*** UPDATE ***
I had the setting on "YES" to save the cert to jffs. Turned it to "NO" and the router rebooted (and I think created a new cert). Error no longer in logs every 30 sec or so. Perhaps the cert got corrupted during the firmware update? I'll let you know if I see the error again.
 
Last edited by a moderator:
Allow me to add my voice to the chorus of thanks, John. Your firmware has breathed new life into my trusty RT-N66U. Thank you for all your hard work!
 
Have always just let the router create the cert for https access- and https access to router works despite these errors.

I do use an unconventional set of ip addresses- the router is 10.xxx.xxx.xxx

Also use unconventional port for https access, and only use https access.

*** UPDATE ***
I had the setting on "YES" to save the cert to jffs. Turned it to "NO" and the router rebooted (and I think created a new cert). Error no longer in logs every 30 sec or so. Perhaps the cert got corrupted during the firmware update? I'll let you know if I see the error again.
Interesting.....I was going to ask you to set the save cert to 'Yes'.....I've been running that way for a long time (so I could load the cert into the browser and not have it change at every reboot) and didn't see that during the development/testing. A bit stumped here....

In any event, I've coded a patch that will shut down the http/https response check after 5 consecutive fails. It's really not good to keep starting/stopping httpd and filling up the syslog in case of a problem.
 
Interesting.....I was going to ask you to set the save cert to 'Yes'.....I've been running that way for a long time (so I could load the cert into the browser and not have it change at every reboot) and didn't see that during the development/testing. A bit stumped here....

In any event, I've coded a patch that will shut down the http/https response check after 5 consecutive fails. It's really not good to keep starting/stopping httpd and filling up the syslog in case of a problem.

I do prefer it saving the cert as well. I will put it back to yes and report my results.

*** REPORT ***
Set saving the cert back to yes and no issue in the logs.

Thanks again for all you do. This release is a freakin' juggernaut!

Just for your information in case you have a coding epiphany- my settings when things went wrong-
Router ip- 10.xxx.xxx.xxx
Authentication method- https only
Https lan port- not 443
Save https cert- yes
Enable web access from wan- no
Auto logout- 0
Allow specified IP address- no
 
Last edited by a moderator:
@john9527 Is your version numbering explained in this thread? (I have no idea what "E" refers to... "errata"?)

Regardless, I would prefer a more intuitive, common version numbering system, perhaps like Firefox or the Linux kernel. http://www.linfo.org/kernel_version_numbering.html
Not too much of a mystery...it's evolved a bit over time :)

3743.43_2-17E2j9527

374.43_2 = the base Merlin level for the fork
17 =major release level (two digits - decimal)
E = next letter after..... 'B' (for Beta)....I didn't like C, and 'D' I use for 'Development' if I'm working privately with someone on a new feature. So 'E' for released code.
2 = minor release level (single hex digit)
j9527 = short form of my forum id. When I first approached Merlin about doing a fork, we decided to include an identifier to distinguish it from his work.
 
Not too much of a mystery...it's evolved a bit over time :)

3743.43_2-17E2j9527

374.43_2 = the base Merlin level for the fork
17 =major release level (two digits - decimal)
E = next letter after..... 'B' (for Beta)....I didn't like C, and 'D' I use for 'Development' if I'm working privately with someone on a new feature. So 'E' for released code.
2 = minor release level (single hex digit)
j9527 = short form of my forum id. When I first approached Merlin about doing a fork, we decided to include an identifier to distinguish it from his work.

I understand the merlin base & "j9527" suffix, but very little of the rest makes sense to me.

For a project like yours that focuses on end-users (rather than devs), the versioning system is confusing. Mixing hex & decimal is completely unexpected. At least include an explanation of your peculiar versioning system in the first post.

The "Ex" versioning system has confused me from day one, so I thought I would bring it up.
 
I have a problem with the media server... it doesn't start on many reboots, even with the scan on every boot option set to yes.
I can see these in the log upon every reboot:

Jan 1 05:30:13 hotplug[313]: USB ntfs fs at /dev/sda1 mounted on /tmp/mnt/WD_NAS
Jan 1 05:30:14 hotplug[313]: USB partition unmounted from /tmp/mnt/WD_NAS
Jan 1 05:30:15 hotplug[313]: USB /dev/sda1(ntfs) failed to mount at the first try!
Jan 1 05:30:15 kernel: ufsd: use builtin utf8 instead of kernel utf8
Jan 1 05:30:17 kernel: ufsd: sda1 without journal
Jan 1 05:30:17 hotplug[313]: USB ntfs fs at /dev/sda1 mounted on /tmp/mnt/WD_NAS

Don't know if this is what is causing the issue. If i subsequently switch off the media server and switch it on again then it starts up. Any workarounds to delay starting the media server upon boot?

EDIT: Also the scheduled disk scanner when set to anything other than disabled does not stick.

Yep..its quitting on every soft reboot now. I found this https://github.com/RMerl/asuswrt-merlin/wiki/delay-start-of-minidlna-to-wait-for-the-USB-disk-mount to delay starting of the media server. Will it work?
 
Last edited:
I always thought the 'E' = experimental..

Sent from my Game Boy Advance 32gb 4GLTE/WiFi using Tapatalk
 
I always thought the 'E' = experimental..

Sent from my Game Boy Advance 32gb 4GLTE/WiFi using Tapatalk

The confusion is the problem I am concerned with.
 

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