Asuswrt-Merlin 3.0.0.4.354.28 Beta 1

[ilium007]

So what is the best build to revert to for 5GHz radio stability ?

 

[Booker-T]

I would like to ask is current build support Sierra DirectIP mode for its usb dongles?

 

[RMerlin]

So what is the best build to revert to for 5GHz radio stability ?

In general, 270.26b. But your experience might vary based on which router you have, which clients you have, etc...

 

[RMerlin]

I would like to ask is current build support Sierra DirectIP mode for its usb dongles?

If Asus does, then so do I. USB support is unchanged from the original firmware.

 

[SCADAMON]

Where is the page for enable / disable Master Browser? I thought I saw it before but cant find it now.
I have a NAS that has the option to be "Local master browser", if this is enabled in the NAS does it disappear from the AC66U?
I don't see anything in the sys logs.
Thanks.

 

[SCADAMON]

Does this F/W use ASUS DDNS automatically? Even if you don't have an account with ASUS and use a different DDNS?
Why the "strange server response"?
See Log, is this normal?


Dec 31 15:00:08 kernel: CPU revision is: 00019749
Dec 31 15:00:08 kernel: Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Dec 31 15:00:08 kernel: Determined physical RAM map:
Dec 31 15:00:08 kernel: memory: 07fff000 @ 00000000 (usable)
Dec 31 15:00:08 kernel: memory: 08000000 @ 87fff000 (usable)
Dec 31 15:00:08 kernel: Built 1 zonelists. Total pages: 585216
Dec 31 15:00:08 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Dec 31 15:00:08 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Dec 31 15:00:09 syslog: module ledtrig-usbdev not found in modules.dep
Dec 31 15:00:09 kernel: PID hash table entries: 2048 (order: 11, 8192 bytes)
Dec 31 15:00:09 kernel: CPU: BCM5300 rev 1 pkg 0 at 600 MHz
Dec 31 15:00:09 kernel: Using 300.000 MHz high precision timer.
Dec 31 15:00:09 syslog: module leds-usb not found in modules.dep
Dec 31 15:00:09 kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Dec 31 15:00:09 kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 31 15:00:09 kernel: Mount-cache hash table entries: 512
Dec 31 15:00:09 kernel: PCI: Initializing host
Dec 31 15:00:09 kernel: PCI: Reset RC
Dec 31 15:00:09 kernel: PCI: Initializing host
Dec 31 15:00:09 kernel: PCI: Reset RC
Dec 31 15:00:09 kernel: PCI: Fixing up bus 0
Dec 31 15:00:09 kernel: PCI/PCIe coreunit 0 is set to bus 1.
Dec 31 15:00:09 kernel: PCI: Fixing up bridge
Dec 31 15:00:09 kernel: PCI: Fixing up bridge
Dec 31 15:00:09 kernel: PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
Dec 31 15:00:09 kernel: PCI: Fixing up bus 1
Dec 31 15:00:09 kernel: PCI/PCIe coreunit 1 is set to bus 2.
Dec 31 15:00:09 kernel: PCI: Fixing up bridge
Dec 31 15:00:09 kernel: PCI: Fixing up bridge
Dec 31 15:00:09 kernel: PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
Dec 31 15:00:09 kernel: PCI: Fixing up bus 2
Dec 31 15:00:09 kernel: IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
Dec 31 15:00:09 kernel: TCP established hash table entries: 16384 (order: 5, 131072 bytes)
Dec 31 15:00:09 kernel: TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
Dec 31 15:00:09 kernel: highmem bounce pool size: 64 pages
Dec 31 15:00:09 kernel: pflash: found no supported devices
Dec 31 15:00:09 kernel: Boot partition size = 262144(0x40000)
Dec 31 15:00:09 kernel: Found a Zentel NAND flash with 2048B pages or 128KB blocks; total size 128MB
Dec 31 15:00:09 kernel: lookup_nflash_rootfs_offset: offset = 0x0
Dec 31 15:00:09 kernel: dev_nvram_init: _nvram_init
Dec 31 15:00:09 kernel: _nvram_init: allocat size= 65536
Dec 31 15:00:09 kernel: u32 classifier
Dec 31 15:00:09 kernel: OLD policer on
Dec 31 15:00:09 kernel: Netfilter messages via NETLINK v0.30.
Dec 31 15:00:09 kernel: nf_conntrack version 0.5.0 (2048 buckets, 16384 max)
Dec 31 15:00:09 kernel: ipt_time loading
Dec 31 15:00:09 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 15:00:09 kernel: net/ipv4/netfilter/tomato_ct.c [Apr 19 2013 19:28:27]
Dec 31 15:00:09 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 15:00:09 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Dec 31 15:00:09 kernel: Warning: unable to open an initial console.
Dec 31 15:00:09 kernel: Failed to execute /sbin/preinit. Attempting defaults...
Dec 31 15:00:09 kernel: ctf: module license 'Proprietary' taints kernel.
Dec 31 15:00:09 kernel: et_module_init: passivemode set to 0x0
Dec 31 15:00:09 kernel: et_module_init: et_txq_thresh set to 0x400
Dec 31 15:00:09 kernel: bcm_robo_enable_switch: EEE is disabled
Dec 31 15:00:09 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.30.102.9 (r366174)
Dec 31 15:00:09 kernel: PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
Dec 31 15:00:09 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.102.9 (r366174)
Dec 31 15:00:09 kernel: PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Dec 31 15:00:10 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.102.9 (r366174)
Dec 31 15:00:10 kernel: Algorithmics/MIPS FPU Emulator v1.5
Dec 31 15:00:10 kernel: NTFS (with native replay) support included
Dec 31 15:00:10 kernel: optimized: speed
Dec 31 15:00:10 kernel: Build_for__asus_n66u_2011-10-27_U86_r187446_b122
Dec 31 15:00:11 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Dec 31 15:00:11 stop_nat_rules: apply the redirect_rules!
Dec 31 15:00:11 WAN Connection: Fail to connect with some issues.
Dec 31 15:00:11 dnsmasq[494]: failed to bind DHCP server socket: Address already in use
Dec 31 15:00:11 dnsmasq[494]: FAILED to start up
Dec 31 15:00:11 RT-AC66U: start httpd
Dec 31 15:00:12 disk monitor: be idle
Dec 31 15:00:22 pppd[526]: Connected to XX:XX:XX:XX:XX:XX via interface eth0
Dec 31 15:00:38 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Dec 31 15:00:38 rc_service: ip-up 547:notify_rc stop_dnsmasq
Dec 31 15:00:38 rc_service: ip-up 547:notify_rc start_dnsmasq
Dec 31 15:00:38 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 31 15:00:38 kernel: nf_nat_rtsp v0.6.21 loading
Dec 31 15:00:38 rc_service: ip-up 547:notify_rc stop_upnp
Dec 31 15:00:38 rc_service: ip-up 547:notify_rc start_upnp
Dec 31 15:00:39 ddns update: ez-ipupdate: starting...
Dec 31 15:00:39 WAN Connection: WAN was restored.
Dec 31 15:00:39 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
Dec 31 15:00:39 ddns update: error recv()ing reply: Connection reset by peer
Dec 31 15:00:39 ddns update: strange server response, are you connecting to the right server?
Dec 31 15:00:39 ddns update: asusddns_update: 1
Dec 31 15:00:39 rc_service: ip-up 547:notify_rc stop_ntpc
Dec 31 15:00:39 rc_service: ip-up 547:notify_rc start_ntpc
May 6 18:18:04 rc_service: ntp 624:notify_rc restart_upnp
May 6 18:18:04 rc_service: ntp 624:notify_rc restart_diskmon
May 6 18:18:04 disk monitor: be idle
May 6 18:18:07 watchdog: start ddns.
May 6 18:18:07 rc_service: watchdog 506:notify_rc start_ddns
May 6 18:18:07 ddns update: ez-ipupdate: starting...
May 6 18:18:16 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
May 6 18:18:16 ddns update: error recv()ing reply: Connection reset by peer
May 6 18:18:16 ddns update: strange server response, are you connecting to the right server?
May 6 18:18:16 ddns update: asusddns_update: 1
May 6 18:18:26 crond[499]: time disparity of 1234218 minutes detected
May 6 18:18:37 watchdog: start ddns.
May 6 18:18:37 rc_service: watchdog 506:notify_rc start_ddns
May 6 18:18:37 ddns update: ez-ipupdate: starting...
May 6 18:18:37 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
May 6 18:18:37 ddns update: error recv()ing reply: Connection reset by peer
May 6 18:18:37 ddns update: strange server response, are you connecting to the right server?
May 6 18:18:37 ddns update: asusddns_update: 1
May 6 18:19:07 watchdog: start ddns.
May 6 18:19:07 rc_service: watchdog 506:notify_rc start_ddns
May 6 18:19:07 ddns update: ez-ipupdate: starting...
May 6 18:19:07 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
May 6 18:19:07 ddns update: error recv()ing reply: Connection reset by peer
May 6 18:19:07 ddns update: strange server response, are you connecting to the right server?
May 6 18:19:07 ddns update: asusddns_update: 1
May 6 18:19:37 watchdog: start ddns.
May 6 18:19:37 rc_service: watchdog 506:notify_rc start_ddns
May 6 18:19:37 ddns update: ez-ipupdate: starting...
May 6 18:19:37 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
May 6 18:19:37 ddns update: request successful
May 6 18:19:37 ddns update: asusddns_update: 0
May 6 18:19:37 ddns: ddns update ok
May 7 06:03:00 rc_service: httpd 495:notify_rc restart_wlcscan

 

[Raptor]

Where is the page for enable / disable Master Browser? I thought I saw it before but cant find it now.
I have a NAS that has the option to be "Local master browser", if this is enabled in the NAS does it disappear from the AC66U?
I don't see anything in the sys logs.
Thanks.

First you must use Merlin's firmware. This option does not exist in ASUS firmware.
Go to USB Applications -> Servers Center -> Miscellaneous setting (Tab) -> Select "Force as Master Browser" and save.
It's best to use the router as the Master Browser as it has the best discovery of static and DHCP devices.

 

[SCADAMON]

First you must use Merlin's firmware. This option does not exist in ASUS firmware.
Go to USB Applications -> Servers Center -> Miscellaneous setting (Tab) -> Select "Force as Master Browser" and save.
It's best to use the router as the Master Browser as it has the best discovery of static and DHCP devices.

That explains it... I do use Merlin's firmware but do not use the USB (Samba) services in the router. I use it on my NAS (E-Net).

 

[SCADAMON]

Why is this happening???

May 7 08:58:11 miniupnpd[632]: Failed to get IP for interface ppp0
May 7 08:58:11 miniupnpd[632]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 7 08:58:11 WAN Connection: Fail to connect with some issues.
May 7 08:58:11 stop_nat_rules: apply the redirect_rules!
May 7 08:58:11 rc_service: wanduck 487:notify_rc stop_dnsmasq
May 7 08:58:11 rc_service: wanduck 487:notify_rc start_dnsmasq
May 7 08:58:11 rc_service: start_dnsmasq is waitting stop_dnsmasq...
May 7 08:58:27 pppd[526]: Connected to XX:XX:XX:XX:XX:XX via interface eth0
May 7 08:58:28 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 7 08:58:28 rc_service: ip-up 2617:notify_rc stop_dnsmasq
May 7 08:58:28 rc_service: ip-up 2617:notify_rc start_dnsmasq
May 7 08:58:28 rc_service: start_dnsmasq is waitting stop_dnsmasq...
May 7 08:58:29 rc_service: ip-up 2617:notify_rc stop_upnp
May 7 08:58:29 rc_service: ip-up 2617:notify_rc start_upnp
May 7 08:58:29 ddns update: ez-ipupdate: starting...
May 7 08:58:29 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
May 7 08:58:30 ddns update: request successful
May 7 08:58:30 ddns update: asusddns_update: 0
May 7 08:58:30 ddns: ddns update ok
May 7 08:58:33 WAN Connection: WAN was restored.
May 7 09:02:09 miniupnpd[2651]: Failed to get IP for interface ppp0
May 7 09:02:09 miniupnpd[2651]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 7 09:02:13 WAN Connection: Fail to connect with some issues.
May 7 09:02:13 stop_nat_rules: apply the redirect_rules!
May 7 09:02:13 rc_service: wanduck 487:notify_rc stop_dnsmasq
May 7 09:02:13 rc_service: wanduck 487:notify_rc start_dnsmasq
May 7 09:02:13 rc_service: start_dnsmasq is waitting stop_dnsmasq...
May 7 09:02:26 pppd[526]: Connected to XX:XX:XX:XX:XX:XX via interface eth0
May 7 09:02:27 miniupnpd[2651]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
May 7 09:02:27 miniupnpd[2651]: Failed to get IP for interface ppp0
May 7 09:02:27 miniupnpd[2651]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 7 09:02:27 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 7 09:02:27 rc_service: ip-up 2681:notify_rc stop_dnsmasq
May 7 09:02:27 rc_service: ip-up 2681:notify_rc start_dnsmasq
May 7 09:02:27 rc_service: start_dnsmasq is waitting stop_dnsmasq...
May 7 09:02:28 rc_service: ip-up 2681:notify_rc stop_upnp
May 7 09:02:28 rc_service: ip-up 2681:notify_rc start_upnp
May 7 09:02:28 rc_service: start_upnp is waitting stop_upnp...
May 7 09:02:29 ddns update: ez-ipupdate: starting...
May 7 09:02:29 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
May 7 09:02:29 WAN Connection: WAN was restored.
May 7 09:02:30 ddns update: request successful
May 7 09:02:30 ddns update: asusddns_update: 0
May 7 09:02:30 ddns: ddns update ok

 

[EvgeniX]

May 6 04:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 04:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 04:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 04:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 05:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 05:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 05:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 05:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 07:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 07:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 07:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 07:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 09:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 09:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 09:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 09:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 11:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 11:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 11:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 11:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 13:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 13:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 13:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 13:42:34 kernel: nf_ct_ras: decoding error: out of bound
May 6 13:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 13:42:35 kernel: nf_ct_ras: decoding error: out of range
May 6 13:42:35 kernel: nf_ct_ras: decoding error: out of range
May 6 13:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 13:42:35 kernel: nf_ct_ras: decoding error: out of range
May 6 13:42:35 kernel: nf_ct_ras: decoding error: out of range
May 6 15:42:35 kernel: printk: 1 messages suppressed.
May 6 15:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 15:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 15:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 15:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 17:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 17:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 17:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 17:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 19:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 19:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 19:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 19:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 21:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 21:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 21:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 23:42:35 kernel: nf_ct_ras: decoding error: out of bound
May 6 23:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 23:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 6 23:42:36 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:53 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:53 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:53 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:53 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:14:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:16:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:16:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:16:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:16:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:31:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:31:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:31:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 02:31:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 03:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 03:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 03:01:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 03:01:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 04:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 04:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 04:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 04:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 06:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 06:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 06:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 06:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 08:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 08:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 08:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 08:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 10:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 10:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 10:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 10:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 12:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 12:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 12:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 12:01:57 kernel: nf_ct_ras: decoding error: out of bound
May 7 12:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 12:01:58 kernel: nf_ct_ras: decoding error: out of range
May 7 12:01:58 kernel: nf_ct_ras: decoding error: out of range
May 7 12:01:58 kernel: nf_ct_ras: decoding error: out of bound
May 7 12:01:58 kernel: nf_ct_ras: decoding error: out of range
May 7 12:01:58 kernel: nf_ct_ras: decoding error: out of range
May 7 14:01:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 14:01:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 14:01:59 kernel: nf_ct_ras: decoding error: out of bound
May 7 14:01:59 kernel: nf_ct_ras: decoding error: out of bound


looks something wrong

 

[SCADAMON]

Again with the disconnect from WAN.. Help...

May 7 12:13:11 miniupnpd[2715]: Failed to get IP for interface ppp0
May 7 12:13:11 miniupnpd[2715]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 7 12:13:12 WAN Connection: Fail to connect with some issues.
May 7 12:13:12 stop_nat_rules: apply the redirect_rules!
May 7 12:13:12 rc_service: wanduck 487:notify_rc stop_dnsmasq
May 7 12:13:12 rc_service: wanduck 487:notify_rc start_dnsmasq
May 7 12:13:12 rc_service: start_dnsmasq is waitting stop_dnsmasq...
May 7 12:13:27 pppd[526]: Connected to XX:XX:XX:XX:XX:XX via interface eth0
May 7 12:13:28 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 7 12:13:28 rc_service: ip-up 3147:notify_rc stop_dnsmasq
May 7 12:13:28 rc_service: ip-up 3147:notify_rc start_dnsmasq
May 7 12:13:28 rc_service: start_dnsmasq is waitting stop_dnsmasq...
May 7 12:13:29 rc_service: ip-up 3147:notify_rc stop_upnp
May 7 12:13:29 rc_service: ip-up 3147:notify_rc start_upnp
May 7 12:13:29 ddns update: ez-ipupdate: starting...
May 7 12:13:29 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
May 7 12:13:30 ddns update: request successful
May 7 12:13:30 ddns update: asusddns_update: 0
May 7 12:13:30 ddns: ddns update ok
May 7 12:13:31 WAN Connection: WAN was restored.

 

[RMerlin]

May 7 14:01:59 kernel: nf_ct_ras: decoding error: out of bound


looks something wrong

Try a search for that error message on these forums - I have answered that question a couple of times already Short version: you can ignore this message.

 

[RMerlin]

Again with the disconnect from WAN.. Help...

If your WAN randomly disconnects, then it is typically a problem with the ISP, the modem, or the cable between modem and the router.

 

[SCADAMON]

If your WAN randomly disconnects, then it is typically a problem with the ISP, the modem, or the cable between modem and the router.

Turned out it was the ISP... They came and found the modem bad. I been fighting this for over a week... I will be keeping an eye on it.
Thanks RMerlin.

 

[RMerlin]

I suspect we might not be getting an updated driver from Asus for a while, since they seem to be focusing on getting everything ready for the new router launch scheduled for Computex. I will most likely make a Beta 2 release later this week since there are quite a few changes I want to push live, and the firmware is working fine for RT-AC66U and RT-N16 users (and a lot of RT-N66U users not using the 5 GHz band).

Most notable changes are a lot of RT-N16 issues fixed since I now have a (donated) RT-N16 to test things on it. Various tweaks and fixes to the Site Survey page as well based on user feedback. 3 TB HDD support is also improved - even my Vantec USB enclosure now works fine with it - provided the disk is formated in ext3. And version updates for miniupnpd and dropbear (nothing major in either cases).

 

[przemek]

cfg file from original firmware

Hi,
I could not find the answer, and don't want to brick router: can I upload configuration file from original newest firmware after flashing Merlin version? If they are compatible, in theory it schould work, but...

 

[RMerlin]

Hi,
I could not find the answer, and don't want to brick router: can I upload configuration file from original newest firmware after flashing Merlin version? If they are compatible, in theory it schould work, but...

Flashing won't erase your original settings, so there is no need to even reload your saved settings.

However if you are coming from an older version (for example, 270), it is strongly recommended to reset to factory defaults after flashing to 354. Do not reload saved settings in that case, or you will completely nullify the idea of returning to factory defaults by reloading the exact same settings as before.

 

[przemek]

However if you are coming from an older version (for example, 270), it is strongly recommended to reset to factory defaults after flashing to 354. Do not reload saved settings in that case, or you will completely nullify the idea of returning to factory defaults by reloading the exact same settings as before.

Thanks for the answer.
To be precise: I had 246 or something like that in new router, then I upgraded to official 354 without reseting to factory defaults.
And I have now settings exported from 354.
So in that case would it better to clean or it schould works fine?

 

[RMerlin]

Thanks for the answer.
To be precise: I had 246 or something like that in new router, then I upgraded to official 354 without reseting to factory defaults.
And I have now settings exported from 354.
So in that case would it better to clean or it schould works fine?

Better to clean. In the switch from 246 to 354, Asus has changed a few low-level settings. Not reseting to factory default means you are still using some of those older values, which can lead to issues.

You can always give it a try, but if anything doesn't work quite right, the first thing to try will be to wipe your settings.

 

[RogerSC]

I suspect we might not be getting an updated driver from Asus for a while, since they seem to be focusing on getting everything ready for the new router launch scheduled for Computex. I will most likely make a Beta 2 release later this week since there are quite a few changes I want to push live, and the firmware is working fine for RT-AC66U and RT-N16 users (and a lot of RT-N66U users not using the 5 GHz band).

Most notable changes are a lot of RT-N16 issues fixed since I now have a (donated) RT-N16 to test things on it. Various tweaks and fixes to the Site Survey page as well based on user feedback. 3 TB HDD support is also improved - even my Vantec USB enclosure now works fine with it - provided the disk is formated in ext3. And version updates for miniupnpd and dropbear (nothing major in either cases).

Had a thought about this...have you considered using the wireless driver from your 26b firmware in your next beta firmware for rt-n66u users; i.e. if the firmware is installing on an rt-n66u then use wireless driver "26.b", otherwise use wireless driver "27"? You'll get more testing of new features and fixes that way. I've been using 26b for quite some time now after the one in 27 didn't work well for me.

Or just move the wireless driver back to 26b for everyone, that would be easier, but I don't know if either of these choices is worthwhile for you in moving forward.

Just a thought, wondering if it might help. I'd be happy to test new beta firmware that uses the 26b wireless driver.