Asuswrt-Merlin 378.51 Beta 1 is out

[Speedluvver]

Thanks Merlin for your efforts....

I am running the beta and am seeing 2 items - not sure whether they are issues or not

1. Mar 3 12:32:05 kernel: br0: received packet on vlan1 with own address as source address - loads more of these than in 378.50 - still had them but only a few - I am also seeing this message with eth1 - but not as many as vlan1

2. Mar 3 12:20:50 kernel: net_ratelimit: 101 callbacks suppressed - google tells me that this is ipv6 related, but I have it disabled..

 

[RMerlin]

Thanks Merlin for your efforts....

I am running the beta and am seeing 2 items - not sure whether they are issues or not

1. Mar 3 12:32:05 kernel: br0: received packet on vlan1 with own address as source address - loads more of these than in 378.50 - still had them but only a few - I am also seeing this message with eth1 - but not as many as vlan1

2. Mar 3 12:20:50 kernel: net_ratelimit: 101 callbacks suppressed - google tells me that this is ipv6 related, but I have it disabled..

1 has been reported to death on these forums.

2 is simply Syslog telling you that the line just before that one has been repeated 101 more times. This has nothing to do with IPv6 in particular.

 

[Speedluvver]

1 has been reported to death on these forums.

2 is simply Syslog telling you that the line just before that one has been repeated 101 more times. This has nothing to do with IPv6 in particular.

ok.. Thankyou... so then 2. is the message from 1. being repeated - know the message has been reported to death, but wondered if there is something in the beta that may be causing it to come up more as in 378.50, I only got a few in the log..

 

[sovking]

Hi,
I've upgraded my RT-N66U to 378.50 then to 378.51 beta1, every time I've done factory reset through the web interface.
Then I configured my router to act as an ACCESS POINT and everything was fine, even with entware and some applications
This morning the router rebooted (don't know why).
I noticed it because I cannot access wifi network.
Then when I login trough the web interface, the router prompt me with the quick internet connection wizard. I can re-enter configuration or skip it. After my wifi works.
If I reboots I get the same situation, like if it does not save the configuration.
It's a real problem.

What's happened ?

Here I paste part of syslog.log after booting

Dec  1 01:00:09 kernel: br0: port 3(eth2) entering learning state
Dec  1 01:00:09 kernel: br0: port 2(eth1) entering learning state
Dec  1 01:00:09 kernel: br0: port 1(vlan1) entering learning state
Dec  1 01:00:09 kernel: br0: topology change detected, propagating
Dec  1 01:00:09 kernel: br0: port 3(eth2) entering forwarding state
Dec  1 01:00:09 kernel: br0: topology change detected, propagating
Dec  1 01:00:09 kernel: br0: port 2(eth1) entering forwarding state
Dec  1 01:00:09 kernel: br0: topology change detected, propagating
Dec  1 01:00:09 kernel: br0: port 1(vlan1) entering forwarding state
Dec  1 01:00:10 dropbear[348]: Running in background
Dec  1 01:00:10 kernel: scsi 0:0:0:0: Direct-Access     Generic  External         2.10 PQ: 0 ANSI: 4
Dec  1 01:00:11 kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Dec  1 01:00:11 kernel: sd 0:0:0:0: [sda] Write Protect is off
Dec  1 01:00:11 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec  1 01:00:11 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec  1 01:00:11 kernel:  sda: sda1
Dec  1 01:00:11 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Dec  1 01:00:11 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Dec  1 01:00:11 kernel: scsi 1:0:0:0: Direct-Access     Multi    Flash Reader     1.00 PQ: 0 ANSI: 0
Dec  1 01:00:11 kernel: kjournald starting.  Commit interval 5 seconds
Dec  1 01:00:11 kernel: EXT3 FS on sda1, internal journal
Dec  1 01:00:11 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec  1 01:00:11 hotplug[372]: USB ext3 fs at /dev/sda1 mounted on /tmp/mnt/NexStar3
Dec  1 01:00:11 rc_service: hotplug 372:notify_rc restart_nasapps
Dec  1 01:00:11 kernel: sd 1:0:0:0: [sdb] 61405184 512-byte hardware sectors (31439 MB)
Dec  1 01:00:11 kernel: sd 1:0:0:0: [sdb] Write Protect is off
Dec  1 01:00:11 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Dec  1 01:00:11 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Dec  1 01:00:11 kernel:  sdb: sdb1 sdb2
Dec  1 01:00:11 kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk
Dec  1 01:00:11 kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Dec  1 01:00:14 RT-N66U: start httpd
Dec  1 01:00:14 RT-N66U: start httpd - SSL
Dec  1 01:00:15 crond[412]: crond: crond (busybox 1.20.2) started, log level 8
Dec  1 01:00:15 syslog: Generating SSL certificate...
Dec  1 01:00:15 syslog: Generating SSL certificate...
Dec  1 01:00:15 disk monitor: be idle
Dec  1 01:00:18 Samba Server: daemon is started
Dec  1 01:00:20 FTP Server: daemon is stopped
Dec  1 01:00:20 Samba Server: smb daemon is stopped
Dec  1 01:00:20 Samba Server: daemon is started
Dec  1 01:00:20 kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Dec  1 01:00:20 statd[502]: Version 1.1.6 Starting
Dec  1 01:00:20 statd[502]: statd running as root. chown /var/lib/nfs/sm to choose different user
Dec  1 01:00:21 kernel: kjournald starting.  Commit interval 5 seconds
Dec  1 01:00:21 kernel: EXT3 FS on sdb1, internal journal
Dec  1 01:00:21 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec  1 01:00:21 hotplug[405]: USB ext3 fs at /dev/sdb1 mounted on /tmp/mnt/sd
Dec  1 01:00:22 rc_service: hotplug 405:notify_rc restart_nasapps
Dec  1 01:00:22 FTP Server: daemon is stopped
Dec  1 01:00:22 Samba Server: smb daemon is stopped
Dec  1 01:00:22 mountd[520]: Caught signal 15, un-registering and exiting.
Dec  1 01:00:22 kernel: nfsd: last server has exited
Dec  1 01:00:22 kernel: nfsd: unexporting all filesystems
Dec  1 01:00:22 statd[502]: Caught signal 15, un-registering and exiting.
Dec  1 01:00:22 Samba Server: daemon is started
Dec  1 01:00:22 statd[555]: Version 1.1.6 Starting
Dec  1 01:00:22 statd[555]: statd running as root. chown /var/lib/nfs/sm to choose different user
Dec  1 01:00:24 kernel: kjournald starting.  Commit interval 5 seconds
Dec  1 01:00:24 kernel: EXT3 FS on sdb2, internal journal
Dec  1 01:00:24 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec  1 01:00:24 hotplug[406]: USB ext3 fs at /dev/sdb2 mounted on /tmp/mnt/data
Dec  1 01:00:24 rc_service: hotplug 406:notify_rc restart_nasapps
Dec  1 01:00:24 FTP Server: daemon is stopped
Dec  1 01:00:24 Samba Server: smb daemon is stopped
Dec  1 01:00:24 mountd[575]: Caught signal 15, un-registering and exiting.
Dec  1 01:00:24 kernel: nfsd: last server has exited
Dec  1 01:00:24 kernel: nfsd: unexporting all filesystems
Dec  1 01:00:24 statd[555]: Caught signal 15, un-registering and exiting.
Dec  1 01:00:24 Samba Server: daemon is started
Dec  1 01:00:24 statd[610]: Version 1.1.6 Starting
Dec  1 01:00:24 statd[610]: statd running as root. chown /var/lib/nfs/sm to choose different user
Dec  1 01:00:40 rc_service: udhcpc_lan 631:notify_rc stop_httpd
Dec  1 01:00:40 rc_service: udhcpc_lan 631:notify_rc start_httpd
Dec  1 01:00:40 rc_service: waitting "stop_httpd" via udhcpc_lan ...
Dec  1 01:00:41 rc_service: udhcpc_lan 631:notify_rc start_dnsmasq
Dec  1 01:00:41 rc_service: waitting "start_httpd" via udhcpc_lan ...
Dec  1 01:00:41 RT-N66U: start httpd
Dec  1 01:00:41 RT-N66U: start httpd - SSL
Dec  1 01:00:42 ntp: start NTP update
Dec  1 01:00:43 rc_service: udhcpc_lan 631:notify_rc restart_dms
Dec  1 01:01:09 ntp: start NTP update
Dec  1 01:01:37 ntp: start NTP update
Mar  3 17:02:42 rc_service: ntp 635:notify_rc restart_diskmon
Mar  3 17:02:42 disk monitor: be idle
Mar  3 17:03:05 crond[412]: time disparity of 133442 minutes detected
Mar  3 17:06:02 rc_service: httpd 633:notify_rc restart_net_and_phy
Mar  3 17:06:04 FTP Server: daemon is stopped
Mar  3 17:06:04 Samba Server: smb daemon is stopped
Mar  3 17:06:10 kernel: br0: port 3(eth2) entering disabled state
Mar  3 17:06:10 kernel: br0: port 2(eth1) entering disabled state
Mar  3 17:06:10 kernel: br0: port 1(vlan1) entering disabled state
Mar  3 17:06:10 kernel: vlan1: dev_set_promiscuity(master, -1)
Mar  3 17:06:10 kernel: device eth0 left promiscuous mode
Mar  3 17:06:10 kernel: device vlan1 left promiscuous mode
Mar  3 17:06:10 kernel: br0: port 1(vlan1) entering disabled state
Mar  3 17:06:10 kernel: device eth1 left promiscuous mode
Mar  3 17:06:10 kernel: br0: port 2(eth1) entering disabled state
Mar  3 17:06:10 kernel: device eth2 left promiscuous mode
Mar  3 17:06:10 kernel: br0: port 3(eth2) entering disabled state
Mar  3 17:06:11 kernel: wl_module_init: passivemode set to 0x0
Mar  3 17:06:11 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Mar  3 17:06:11 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Mar  3 17:06:12 kernel: vlan1: dev_set_promiscuity(master, 1)
Mar  3 17:06:12 kernel: device eth0 entered promiscuous mode
Mar  3 17:06:12 kernel: device vlan1 entered promiscuous mode
Mar  3 17:06:12 kernel: device eth1 entered promiscuous mode
Mar  3 17:06:12 kernel: device eth2 entered promiscuous mode
Mar  3 17:06:12 kernel: br0: port 3(eth2) entering learning state
Mar  3 17:06:12 kernel: br0: port 2(eth1) entering learning state
Mar  3 17:06:12 kernel: br0: port 1(vlan1) entering learning state
Mar  3 17:06:12 kernel: br0: topology change detected, propagating
Mar  3 17:06:12 kernel: br0: port 3(eth2) entering forwarding state
Mar  3 17:06:12 kernel: br0: topology change detected, propagating
Mar  3 17:06:12 rc_service: init 1:notify_rc restart_dms
Mar  3 17:06:12 rc_service: waitting "restart_net_and_phy" via  ...
Mar  3 17:06:12 kernel: br0: port 2(eth1) entering forwarding state
Mar  3 17:06:12 kernel: br0: topology change detected, propagating
Mar  3 17:06:12 kernel: br0: port 1(vlan1) entering forwarding state
Mar  3 17:06:43 rc_service: skip the event: restart_dms.
Mar  3 17:06:47 RT-N66U: start httpd
Mar  3 17:06:47 RT-N66U: start httpd - SSL
Mar  3 17:06:48 Samba Server: daemon is started
Mar  3 17:07:39 rc_service: httpd 762:notify_rc start_autodet
Mar  3 17:07:43 rc_service: httpd 762:notify_rc start_autodet
Mar  3 17:07:49 rc_service: httpd 762:notify_rc start_autodet

 

[snapilica2003]

I understand that the AC68U does not support FA hardware acceleration but for some reason after a factory reset now it shows everywhere that CTF and FA are both enabled. Is this a bug?

LE: It seems that after the 4th or 5th restart it's now showing CTF only. Strange

 

[VANT]

for me is not bug. 68U suport dpi and FA like 87U

 

[PaulC]

That's odd because my own Entware setup is persistent and correctly survives reboots. I'll take another look, but make sure that you don't have leftovers from Optware still there.

For some reason, the 'ln -sf $1/entware.arm /tmp/opt' line in post-mount wasn't overwriting an existing symbolic link to optware.

But on further investigation, there's something much stranger going on. 'disk monitor' is unmounting /dev/sda1 right after it mounts, and isn't remounting it for almost 20 seconds. In the meantime, services-start script runs, and the 'sleep 10' it starts with isn't nearly long enough for /dev/sda1 to have been remounted.

I also see a bunch of services being started well after services-start was invoked (but while /dev/sda1 is still unmounted). I thought services-start was supposed to be called after the system services had already been started?

Below I've pasted an excerpt from syslog from boot (I've replaced dnsmasq and dropbear 'noise' with '...'). My current services-start script looks like this:

#!/bin/sh
logger $(basename $0)
log=/tmp/$(basename $0).log
sleep 60
mounted="`mount | grep '/dev/sda1'`"
logger $(basename $0) ${mounted}
/opt/etc/init.d/rc.unslung start > $log

This script 'works'; changing the 'sleep 60' to anything below 19 secs doesn't result in rc.unslung being invoked. The default script uses 'sleep 10', so entware startup scripts are not being run.

Two things stand out to me:
a) services-start seems to be invoked a lot earlier that I expected. A number of services haven't been started at that point.
b) disk monitor unmounts /dev/sda1 for an extended period during boot when I'd expect it would need to be mounted. Perhaps related to the kernel fsck message? if disk monitor is doing an fsck, it's not resetting the flag, since it's doing it on every single boot.

I'd dig further, but spare time is short for the next few days. Let me know if there's anything I can do to help.

- Paul

---
Nov 30 16:00:15 kernel: sd 0:0:0:0: [sda] 15751168 512-byte logical blocks: (8.06 GB/7.51 GiB)
Nov 30 16:00:15 kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 30 16:00:15 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Nov 30 16:00:15 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Nov 30 16:00:15 kernel: sda: sda1
Nov 30 16:00:15 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Nov 30 16:00:15 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Nov 30 16:00:15 stop_nat_rules: apply the redirect_rules!
Nov 30 16:00:15 kernel: EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
Nov 30 16:00:15 qcsapi: write qcsapi conf ok
Nov 30 16:00:15 WAN Connection: ISP's DHCP did not function properly.
Nov 30 16:00:15 hotplug[578]: USB ext2 fs at /dev/sda1 mounted on /tmp/mnt/sda1
Nov 30 16:00:16 disk monitor: unmount partition
Nov 30 16:00:17 syslog: USB partition unmounted from /tmp/mnt/sda1
Nov 30 16:00:17 disk monitor: scan partition
Nov 30 16:00:24 dropbear[668]: Running in background
Nov 30 16:00:27 dnsmasq[682]: started, version 2.73test6 cachesize 1500
Nov 30 16:00:27 dnsmasq[682]: warning: no addresses found for interface vlan2
Nov 30 16:00:27 dnsmasq[682]: warning: no addresses found for interface vlan2
Nov 30 16:00:27 dnsmasq[682]: warning: interface ppp1* does not currently exist
Nov 30 16:00:27 dnsmasq[682]: asynchronous logging enabled, queue limit is 5 messages
Nov 30 16:00:27 dnsmasq-dhcp[682]: DHCP, IP range 10.11.1.80 -- 10.11.1.99, lease time 1h
Nov 30 16:00:27 dnsmasq-dhcp[682]: DHCP, IP range 10.11.1.100 -- 10.11.1.199, lease time 1d
Nov 30 16:00:27 dnsmasq[682]: read /etc/hosts - 5 addresses
Nov 30 16:00:27 dnsmasq[682]: read /etc/hosts.dnsmasq - 1 addresses
Nov 30 16:00:27 dnsmasq-dhcp[682]: read /etc/ethers - 1 addresses
Nov 30 16:00:27 RT-AC87U: start httpd
Nov 30 16:00:27 crond[690]: crond: crond (busybox 1.20.2) started, log level 8
Nov 30 16:00:28 kernel: gro enabled with interval 2
Nov 30 16:00:28 disk monitor: be idle
Nov 30 16:00:28 syslog: Generating SSL certificate...
Nov 30 16:00:30 Samba Server: daemon is started
Nov 30 16:00:30 admin: services-start
Nov 30 16:00:31 dnsmasq[682]: read /etc/hosts - 5 addresses
Nov 30 16:00:31 dnsmasq[682]: read /etc/hosts.dnsmasq - 1 addresses
Nov 30 16:00:31 dnsmasq-dhcp[682]: read /etc/ethers - 1 addresses
Nov 30 16:00:31 admin: /jffs/scripts/dhcpc-event deconfig
Nov 30 16:00:31 rc_service: udhcpc 768:notify_rc start_firewall
Nov 30 16:00:31 dnsmasq[682]: read /etc/hosts - 5 addresses
Nov 30 16:00:31 dnsmasq[682]: read /etc/hosts.dnsmasq - 1 addresses
Nov 30 16:00:31 dnsmasq-dhcp[682]: read /etc/ethers - 1 addresses
Nov 30 16:00:31 dnsmasq[682]: using nameserver 75.75.76.76#53 for domain local
Nov 30 16:00:31 dnsmasq[682]: using nameserver 75.75.76.76#53 for domain bad
Nov 30 16:00:31 dnsmasq[682]: using nameserver 75.75.75.75#53 for domain local
Nov 30 16:00:31 dnsmasq[682]: using nameserver 75.75.75.75#53 for domain bad
Nov 30 16:00:31 dnsmasq[682]: using nameserver 75.75.75.75#53
Nov 30 16:00:31 dnsmasq[682]: using nameserver 75.75.76.76#53
Nov 30 16:00:31 admin: /jffs/scripts/dhcpc-event bound
Nov 30 16:00:31 wan: finish adding multi routes
Nov 30 16:00:31 rc_service: udhcpc 768:notify_rc stop_upnp
Nov 30 16:00:31 rc_service: waitting "start_firewall" via udhcpc ...
...
Nov 30 16:00:35 WAN Connection: WAN was restored.
Nov 30 16:00:35 start_nat_rules: apply the nat_rules(/tmp/nat_rules)!
...
Nov 30 16:00:48 disk monitor: re-mount partition
Nov 30 16:00:48 kernel: EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
Nov 30 16:00:48 syslog: USB ext2 fs at /dev/sda1 mounted on /tmp/mnt/sda1
Nov 30 16:00:48 disk monitor: done
...
Nov 30 16:01:01 rc_service: skip the event: stop_upnp.
Nov 30 16:01:01 rc_service: udhcpc 768:notify_rc start_upnp
Nov 30 16:01:01 rc_service: waitting "start_firewall" via udhcpc ...
Nov 30 16:01:04 qtn: bootcfg.tgz exists
Nov 30 16:01:04 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan2_vlan2)!
Nov 30 16:01:05 kernel: nf_conntrack_rtsp v0.6.21 loading
Nov 30 16:01:05 kernel: nf_nat_rtsp v0.6.21 loading
Nov 30 16:01:08 miniupnpd[1099]: HTTP listening on port 34181
Nov 30 16:01:08 miniupnpd[1099]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 30 16:01:08 ddns update: ez-ipupdate: starting...
Nov 30 16:01:08 ddns update: connected to updates.dnsomatic.com (67.215.92.215) on port 80.
Nov 30 16:01:08 ddns update: request successful
Nov 30 16:01:08 ddns update: asusddns_update: 0
Nov 30 16:01:09 ddns: ddns update ok
Nov 30 16:01:09 dhcp client: bound 73.170.152.176 via 73.170.152.1 during 215985 seconds.
Nov 30 16:01:09 ntp: start NTP update
Mar 2 23:29:01 rc_service: hotplug 578:notify_rc restart_nasapps
Mar 2 23:29:01 rc_service: ntp 1132:notify_rc restart_upnp
Mar 2 23:29:01 rc_service: waitting "restart_nasapps" via hotplug ...
Mar 2 23:29:01 iTunes: daemon is stopped
Mar 2 23:29:01 FTP Server: daemon is stopped
Mar 2 23:29:02 Samba Server: smb daemon is stopped
Mar 2 23:29:02 kernel: gro disabled
Mar 2 23:29:02 Timemachine: daemon is stopped
Mar 2 23:29:02 kernel: gro enabled with interval 2
Mar 2 23:29:03 Samba Server: daemon is started
Mar 2 23:29:04 rc_service: ntp 1132:notify_rc restart_diskmon
Mar 2 23:29:04 rc_service: waitting "restart_upnp" via ntp ...
Mar 2 23:29:04 miniupnpd[1099]: shutting down MiniUPnPd
Mar 2 23:29:05 miniupnpd[1192]: HTTP listening on port 50541
Mar 2 23:29:05 miniupnpd[1192]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 2 23:29:08 disk monitor: be idle
Mar 2 23:29:13 dfs: start dfs scan
Mar 2 23:29:13 nodfs_scan: complete
Mar 2 23:29:14 dfs: start dfs scan
Mar 2 23:29:14 nodfs_scan: complete
...
Mar 2 23:29:22 admin: services-start /dev/sda1 on /tmp/mnt/sda1 type ext2 (rw,nodev,relatime,errors=continue,user_xattr)
Mar 2 23:29:23 admin: Started asterisk from .
...
Mar 2 23:29:53 crond[690]: time disparity of 132928 minutes detected
Mar 2 23:29:53 rc_service: rc 1336:notify_rc restart_wrs
Mar 2 23:29:54 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan2_vlan2)!

 

[RMerlin]

For some reason, the 'ln -sf $1/entware.arm /tmp/opt' line in post-mount wasn't overwriting an existing symbolic link to optware.

You can't have both Optware (and/or Download Master) and Entware configured at the same time, they are mutually exclusive.

 

[RMerlin]

for me is not bug. 68U suport dpi and FA like 87U

FA is not supported by the RT-AC68U's BCM4708. You need a router with a BCM4709 for this, which means RT-AC68P, RT-AC87 or RT-AC3200.

If something reports FA as being enabled on an RT-AC68U then it's a webui bug - it's not supported by the hardware.

 

[rickygao]

FA is not supported by the RT-AC68U's BCM4708. You need a router with a BCM4709 for this, which means RT-AC68P, RT-AC87 or RT-AC3200.

If something reports FA as being enabled on an RT-AC68U then it's a webui bug - it's not supported by the hardware.

does FA still need "Adaptive QoS" and "Per IP traffic mornitoring" turned off?

 

[RMerlin]

does FA still need "Adaptive QoS" and "Per IP traffic mornitoring" turned off?

Yes. IPTraffic also needs the whole CTF disabled, not just FA.

 

[RogerSC]

FA is not supported by the RT-AC68U's BCM4708. You need a router with a BCM4709 for this, which means RT-AC68P, RT-AC87 or RT-AC3200.

If something reports FA as being enabled on an RT-AC68U then it's a webui bug - it's not supported by the hardware.

I'm wondering now why my router shows "CTF only" in "Tools", and "CTF(Cut Through Forwarding) is enabled" in LAN ->Switch Control, no "FA" enabled anywhere? My router is an RT-AC68P, and I don't have Per IP traffic or any QoS turned on, or App Analysis or Traffic Statistics turned on. But yet, no FA.

Do have any idea what might be causing this? Not particularly worried about it, just wondering what it might be that's keeping FA off?

I do see this via telnet:

admin@RT-AC68P-0980:/tmp/home/root# nvram show | grep -i ctf
size: 40639 bytes (24897 left)
ctf_fa_mode=0
ctf_disable=0
ctf_disable_force=0
ctf_pt_udp=0
admin@RT-AC68P-0980:/tmp/home/root#

Thanks.

 

[technet]

RT-AC87U.

Reset before and after upgrade.

DNS-O-MATIC DDNS does not update automatically, only when forced on DDNS page.

WAN type is PPPoE.

 

[pepeEL]

Hello Merlin
Can you add label to this on Network MAP when i click the client ?

 

[idimitro]

About the RT-N16 support.

You say that no new features will be developed. How about security fixes?
Would you provide fixes for RT-N16 on top of 378.50?

Thanks for the effort.

 

[got_milk]

About the RT-N16 support.

You say that no new features will be developed. How about security fixes?
Would you provide fixes for RT-N16 on top of 378.50?

Thanks for the effort.

He is dropping support for the SDK5 platform therefore there won't be any more builds for it, security fixes or otherwise.

 

[idimitro]

He is dropping support for the SDK5 platform therefore there won't be any more builds for it, security fixes or otherwise.

As far as I understood, te support will be dropped in 378.51 onwards. My question was if there will be security fixes on top of 378.50.

 

[got_milk]

As far as I understood, te support will be dropped in 378.51 onwards. My question was if there will be security fixes on top of 378.50.

Sorry - misread. It would be a decent amount of effort to maintain a separate branch for just the RT-N16U and whatever fixes go along with it unless a fork like @john9527's opts to maintain support independently, but that will be up to each maintainer to decide.

 

[Deleted member 22229]

I believe Asus will still support that router even though Merlin will not be.

 

[rickygao]

Hello Merlin
Can you add label to this on Network MAP when i click the client ?

That's a good idea, I was confusing first time as well