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!

My upload speed is droped sottenly, its jumping up and Down , is this the fork firmware ?


Sent from my iPhone using Tapatalk
 
My upload speed is droped sottenly, its jumping up and Down , is this the fork firmware ?


Sent from my iPhone using Tapatalk
If I understand correctly, what you are seeing is your ISP applying your service level upload caps to your uploads. For me, I have a 5Mbs upload. When running a speedtest, it will initially jump up to about 12Mbs, then come down in steps to my 5Mbs cap.
 
Has anyone tried to get port mirroring to function on AC68U using the iptables TEE function instructions outlined here: http://www.snbforums.com/threads/enabling-port-mirroring-asus-rt-ac66u.23181/? Is there a different option?
I'd like to enable port mirroring on my RT-AC58U running John's latest if possible. TIA
The original article that was referenced was written in 2013, so my guess would be that it would work since this is a 2014 code base (but I've never tried it myself).

One caution is that other functions use the mangle table, such as QOS and the NAT loopback, so you may need to see if it intersects or disable those for it to work.
 
Last edited:
Wanted to post i switched routers to the RT-AC68R and this fork V-14 works just as well as it did on my trusty RT-N66R. Thanks again John and Merlin. :):D
 
First fork firmware that gave me constant WAN disconnects, with having to reboot router to correct. Went back to 13E1, and all is back to normal and fine, no disconnects. Thx as ever for your hard work though John :)
 
First fork firmware that gave me constant WAN disconnects, with having to reboot router to correct. Went back to 13E1, and all is back to normal and fine, no disconnects. Thx as ever for your hard work though John :)
You're the first to report a problem like this...so I'll need more data to be able to try and help. Start with some info on your type of connection (DHCP, PPPoE), any features used, and the syslog at the time of the failure.
 
Hi John,
after running fine RT-N16 on 13E1 for a while, in preparation to upgrade I went to backup jffs files to my computer (Win7) via samba share on the router just to see that it stopped working.
Code:
>dir \\192.168.x.x\entware
The request is not supported.
>net view \\192.168.x.x
System error 53 has occurred.
The network path was not found.
After upgrading to 14E1 samba share on the router is still inaccessible.
What would you say?
P.S. I didn't install samba (3.6.25) from the entware repo. It is 3.0.37 running.
P.P.S. After re-enabling Samba share it's all right!
Code:
>net view \\192.168.x.x
Shared resources at \\192.168.x.x
RT-N16
Share name  Type  Used as  Comment
-----------------------------------------
entware  Disk  sda1's entware
The command completed successfully.
 
Last edited:
P.P.S. After re-enabling Samba share it's all right!
Thanks for the quick follow-up. I was scratching my head since there were no samba changes.

But a general note/reminder to all. With 14E1, if you do a reset to factory defaults, the running of jffs scripts is disabled (same as Merlin main branch). This also includes any conf.add or .conf files. Since /jffs is not normally shared ,but can be added via a /jffs/configs/smb.conf.add file, it won't be accessible until you re-enable the running of scripts.
 
just a quick question John.
after upgrading to 14E1 and doing a hard reset the running of scripts is disabled ONLY for the jffs partion right.
i can still run a script of an usb stick?


Thanks for the quick follow-up. I was scratching my head since there were no samba changes.

But a general note/reminder to all. With 14E1, if you do a reset to factory defaults, the running of jffs scripts is disabled (same as Merlin main branch). This also includes any conf.add or .conf files. Since /jffs is not normally shared ,but can be added via a /jffs/configs/smb.conf.add file, it won't be accessible until you re-enable the running of scripts.
 
just a quick question John.
after upgrading to 14E1 and doing a hard reset the running of scripts is disabled ONLY for the jffs partion right.
i can still run a script of an usb stick?
The scripts/configs that are disabled are the specialized ones that are recognized by the firmware and automatically run during startup/shutdown.....the various xxx-start, xxx-stop, .postconf, .conf.add, etc. in /jffs.
Since telnet/ssh is disabled on a factory reset, you'd have to enable that first then you could execute any usb scripts (for example, when I test, I'll do the factory reset, then enable telnet, then use my NVRAM Restore utility off a usb stick to put things back).
 
LATEST RELEASE: Update-14E1

Update-14E1 HighLights:

  • Experimental option to improve QOS (bufferbloat)
    This option sets SFQ packet limits through an algorithm based on your upload bandwidth or allows you to tune the value for your specific environment. Please try with a value of '1' first (auto). The option is enabled via telnet or SSH logon to the router
    Code:
    nvram set qos_sfql=[0=off(default), 1=auto, 2-127 set this sfq packet limit] - that's a small 'L' in qos_sfql
    nvram commit
    followed by a reboot or a restart of QOS. Feedback is welcome, especially with respect to the 'auto' setting.


QOS with auto works good for me. Surfing is still possible while downloading. I'm happy! (RT N66U)
Thanks!
 
This version works better for me than the previous V13 one. Still have to reset the modem once every one or two days though. Thanks John!
 
This version works better for me than the previous V13 one. Still have to reset the modem once every one or two days though. Thanks John!

Do you know why you have to reset the modem? What is the symptom?

I recently had a problem with my ISP (not sure if it was a hardware problem or maintenance they were doing in my area) that caused upstream channel aborts. I wrote a script, executed via cru, that would run on the router and monitor the modem and reboot the modem if it detected aborted channels. If there is interest, I can post it up.
 
was this not solved by WAN-DHCP query mode set to normal instead of agressive.
also under USB application-3G/4G set USB modem to NO.


it helped in my situation.

it never ever reboots anymore.(yeh i am the one doing the rebooting whenever i like)



Do you know why you have to reset the modem? What is the symptom?

I recently had a problem with my ISP (not sure if it was a hardware problem or maintenance they were doing in my area) that caused upstream channel aborts. I wrote a script, executed via cru, that would run on the router and monitor the modem and reboot the modem if it detected aborted channels. If there is interest, I can post it up.
 
Do you know why you have to reset the modem? What is the symptom?

I recently had a problem with my ISP (not sure if it was a hardware problem or maintenance they were doing in my area) that caused upstream channel aborts. I wrote a script, executed via cru, that would run on the router and monitor the modem and reboot the modem if it detected aborted channels. If there is interest, I can post it up.

Thanks John! All clients lost connection (limited network) thus the restart. Below is one of the log when that happened

Sep 27 07:07:01 WAN Connection: Ethernet link up.
Sep 27 07:07:01 rc_service: wanduck 302:notify_rc restart_wan_if 0
Sep 27 07:07:01 dnsmasq[320]: read /etc/hosts - 6 addresses
Sep 27 07:07:01 dnsmasq[320]: using nameserver 208.67.222.222#53
Sep 27 07:07:01 dnsmasq[320]: using nameserver 8.8.4.4#53
Sep 27 07:07:01 stop_wan(): perform DHCP release
Sep 27 07:07:01 kernel: Attempt to kill tasklet from interrupt
Sep 27 07:07:01 miniupnpd[443]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Sep 27 07:07:01 miniupnpd[443]: Failed to get IP for interface eth0
Sep 27 07:07:01 miniupnpd[443]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Sep 27 07:07:01 dnsmasq[320]: read /etc/hosts - 6 addresses
Sep 27 07:07:01 dnsmasq[320]: using nameserver 208.67.222.222#53
Sep 27 07:07:01 dnsmasq[320]: using nameserver 8.8.4.4#53
Sep 27 07:07:01 kernel: br0: port 1(vlan1) entering disabled state
Sep 27 07:07:01 kernel: vlan1: dev_set_promiscuity(master, 1)
Sep 27 07:07:01 kernel: br0: port 1(vlan1) entering listening state
Sep 27 07:07:01 kernel: br0: port 1(vlan1) entering learning state
Sep 27 07:07:01 kernel: br0: topology change detected, propagating
Sep 27 07:07:01 kernel: br0: port 1(vlan1) entering forwarding state
Sep 27 07:07:01 dnsmasq[320]: read /etc/hosts - 6 addresses
Sep 27 07:07:01 dnsmasq[320]: using nameserver 208.67.222.222#53
Sep 27 07:07:01 dnsmasq[320]: using nameserver 8.8.4.4#53
Sep 27 07:07:03 dnsmasq[320]: read /etc/hosts - 6 addresses
Sep 27 07:07:03 dnsmasq[320]: using nameserver 208.67.222.222#53
Sep 27 07:07:03 dnsmasq[320]: using nameserver 8.8.4.4#53
Sep 27 07:07:03 rc_service: udhcpc 450:notify_rc start_firewall
Sep 27 07:07:03 rc_service: udhcpc 450:notify_rc stop_upnp
Sep 27 07:07:03 rc_service: waiting "start_firewall" via udhcpc ...
Sep 27 07:07:03 start_nat_rules: apply the nat_rules (/tmp/nat_rules_eth0_eth0)!
Sep 27 07:07:03 start_nat_rules: (/tmp/nat_rules_eth0_eth0) success!
Sep 27 07:07:04 rc_service: udhcpc 450:notify_rc start_upnp
Sep 27 07:07:04 rc_service: waiting "stop_upnp" via udhcpc ...
Sep 27 07:07:04 miniupnpd[443]: shutting down MiniUPnPd
Sep 27 07:07:05 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 30 seconds.
Sep 27 07:07:05 miniupnpd[484]: HTTP listening on port 45781
Sep 27 07:07:05 miniupnpd[484]: Listening for NAT-PMP/PCP traffic on port 5351
Sep 27 07:07:20 miniupnpd[484]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Sep 27 07:07:20 miniupnpd[484]: Failed to get IP for interface eth0
Sep 27 07:07:20 miniupnpd[484]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Sep 27 07:07:20 dnsmasq[320]: read /etc/hosts - 6 addresses
Sep 27 07:07:20 dnsmasq[320]: using nameserver 208.67.222.222#53
Sep 27 07:07:20 dnsmasq[320]: using nameserver 8.8.4.4#53
Sep 27 07:07:22 WAN Connection: ISP's DHCP did not function properly.
Sep 27 07:07:22 stop_nat_rules: apply the redirect_rules!
Sep 27 07:07:22 stop_nat_rules: (/tmp/redirect_rules) success!
Sep 27 07:07:25 dnsmasq[320]: read /etc/hosts - 6 addresses
Sep 27 07:07:25 dnsmasq[320]: using nameserver 208.67.222.222#53
Sep 27 07:07:25 dnsmasq[320]: using nameserver 8.8.4.4#53
Sep 27 07:07:25 rc_service: udhcpc 489:notify_rc start_firewall
Sep 27 07:07:25 rc_service: udhcpc 489:notify_rc stop_upnp
Sep 27 07:07:25 rc_service: waiting "start_firewall" via udhcpc ...
Sep 27 07:07:25 start_nat_rules: apply the nat_rules (/tmp/nat_rules_eth0_eth0)!
Sep 27 07:07:25 start_nat_rules: (/tmp/nat_rules_eth0_eth0) success!
Sep 27 07:07:26 rc_service: udhcpc 489:notify_rc start_upnp
Sep 27 07:07:26 rc_service: waiting "stop_upnp" via udhcpc ...
Sep 27 07:07:26 miniupnpd[484]: shutting down MiniUPnPd
Sep 27 07:07:27 dhcp client: bound xx.xx.117.218 via xx.xx.116.1 during 86400 seconds.
Sep 27 07:07:27 miniupnpd[523]: HTTP listening on port 60512
Sep 27 07:07:27 miniupnpd[523]: Listening for NAT-PMP/PCP traffic on port 5351
Sep 27 07:07:27 WAN Connection: WAN was restored.
 
  • Experimental option to improve QOS (bufferbloat)
    This option sets SFQ packet limits through an algorithm based on your upload bandwidth or allows you to tune the value for your specific environment. Please try with a value of '1' first (auto). The option is enabled via telnet or SSH logon to the router
    Code:
    nvram set qos_sfql=[0=off(default), 1=auto, 2-127 set this sfq packet limit] - that's a small 'L' in qos_sfql
    nvram commit
    followed by a reboot or a restart of QOS. Feedback is welcome, especially with respect to the 'auto' setting.
Hi John,
Does it mean if I turn on this setting, the HW Acceleration will still be turned off?
 
Hi John,
Does it mean if I turn on this setting, the HW Acceleration will still be turned off?
Yes, QOS and HW Acceleration are still not compatible (HW Acceleration will be disabled with QOS enabled). This change just makes a tweak to the QOS algorithms to hopefully make them a bit better.
 

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