SuperFly74
Regular Contributor
My upload speed is droped sottenly, its jumping up and Down , is this the fork firmware ?
Sent from my iPhone using Tapatalk
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.My upload speed is droped sottenly, its jumping up and Down , is this the fork firmware ?
Sent from my iPhone using Tapatalk
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).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
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.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
>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.
>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.
Thanks for the quick follow-up. I was scratching my head since there were no samba changes.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.
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.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?
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
followed by a reboot or a restart of QOS. Feedback is welcome, especially with respect to the 'auto' setting.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
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.
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.
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.
Hi John,
- 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
followed by a reboot or a restart of QOS. Feedback is welcome, especially with respect to the 'auto' setting.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
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.Hi John,
Does it mean if I turn on this setting, the HW Acceleration will still be turned off?
Great. ThanksYes, 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.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!