Welcome Guest ( Log In | Register )

826 Pages « < 500 501 502 503 504 > » Bottom

Outline · [ Standard ] · Linear+

Home Networking ASUS Malaysia Networking User & Technical Support, Managed by ASUS Malaysia Representative

views
     
nitehawk
post Mar 29 2019, 06:14 PM

On my way
****
Senior Member
699 posts

Joined: May 2006


QUOTE(SilentVampire @ Mar 28 2019, 07:50 PM)
Mesh WiFi.
*
What shall I buy and how shall I confire if I use Mesh Wi-Fi?



SilentVampire
post Mar 29 2019, 07:26 PM

Networking Enthusiast
*******
Senior Member
5,714 posts

Joined: Mar 2007



QUOTE(nitehawk @ Mar 29 2019, 06:14 PM)
What shall I buy and how shall I confire if I use Mesh Wi-Fi?
*
This is the ASUS thread, so I would respect that and PM you instead.
kktong83
post Mar 30 2019, 09:07 AM

Getting Started
**
Junior Member
96 posts

Joined: Sep 2005


My Asus 86u just died, there is no light and no response. But this unit I bought in China 3months ago , does Asus malaysia able to provide warranty?
SzeMeng76
post Mar 30 2019, 09:23 AM

Look at all my stars!!
*******
Senior Member
2,318 posts

Joined: Dec 2012
QUOTE(kktong83 @ Mar 30 2019, 09:07 AM)
My Asus 86u just died, there is no light and no response. But this unit I bought in China 3months ago , does Asus malaysia able to provide warranty?
*
No. You need to send back to China. Have 3 years China warranty.

Asus Malaysia only covered Malaysia unit.
blacktubi
post Mar 30 2019, 01:56 PM

-
Group Icon
Elite
8,402 posts

Joined: Jul 2008

QUOTE(jonathanwhm @ Mar 29 2019, 03:11 PM)
In that case, what I need to do is do get a cheap 5-ports switch with vlan feature and configure 3 vlans as follow? hmm.gif  hmm.gif

1) vlan 1 (default vlan across 5 ports) and the ONU unit connected to port#1
2) vlan 500 & 621 for Unifi & Maxis Internet - ASUS Dual-WAN router connected to port#2 (Wondering whether can configure 2 PVID on same port?)
3) vlan 600 (Unifi IPTV) - connected to port#3
*
What is your current ONU situation now?
For most TM single ONU implementation, LAN 1 is configured for Unifi and LAN 3 is for Maxis.

Switch A
Switch Port 1 -> ONU LAN 1
Switch Port 2 VLAN 500 -> BRT-AC828 WAN 1
Switch Port 3 VLAN 600 -> HyppTV

Switch B
Switch Port 1 -> ONU LAN 3
Switch Port 2 VLAN 621 -> BRT-AC828 WAN 2

It is possible to do it with just a single switch but I separated it for simplicity sake.
Anyways, HyppTV is a bit of a hit or miss, some users face connectivity issues when using the TP-Link switch. I suspect it got something to do with TP-Link Multicast implementation.

https://www.blacktubi.com/guide/make-any-ro...-work-on-unifi/
jusbella
post Mar 30 2019, 08:58 PM

Look at all my stars!!
*******
Senior Member
3,032 posts

Joined: Dec 2011


QUOTE(blacktubi @ Mar 30 2019, 01:56 PM)
What is your current ONU situation now?
For most TM single ONU implementation, LAN 1 is configured for Unifi and LAN 3 is for Maxis.

Switch A
Switch Port 1 -> ONU LAN 1
Switch Port 2 VLAN 500 -> BRT-AC828 WAN 1
Switch Port 3 VLAN 600 -> HyppTV

Switch B
Switch Port 1 -> ONU LAN 3
Switch Port 2 VLAN 621 -> BRT-AC828 WAN 2

It is possible to do it with just a single switch but I separated it for simplicity sake.
Anyways, HyppTV is a bit of a hit or miss, some users face connectivity issues when using the TP-Link switch. I suspect it got something to do with TP-Link Multicast implementation.

https://www.blacktubi.com/guide/make-any-ro...-work-on-unifi/
*
Any guide on dell powerconnect 6248p?
jonathanwhm
post Mar 30 2019, 10:07 PM

Getting Started
**
Junior Member
87 posts

Joined: Jun 2011
QUOTE(blacktubi @ Mar 30 2019, 02:56 PM)
What is your current ONU situation now?
For most TM single ONU implementation, LAN 1 is configured for Unifi and LAN 3 is for Maxis.

Switch A
Switch Port 1 -> ONU LAN 1
Switch Port 2 VLAN 500 -> BRT-AC828 WAN 1
Switch Port 3 VLAN 600 -> HyppTV

Switch B
Switch Port 1 -> ONU LAN 3
Switch Port 2 VLAN 621 -> BRT-AC828 WAN 2

It is possible to do it with just a single switch but I separated it for simplicity sake.
Anyways, HyppTV is a bit of a hit or miss, some users face connectivity issues when using the TP-Link switch. I suspect it got something to do with TP-Link Multicast implementation.

https://www.blacktubi.com/guide/make-any-ro...-work-on-unifi/
*
Thanks for the detailed info and the URL.
Just checked on the ONU that LAN 1 is configured for Unifi and Maxis on LAN 3. From time being, I think I will configure the switch as follow since I have only one switch.

Switch
Switch Port 1 -> ONU LAN 1
Switch Port 2 VLAN 500 -> BRT-AC828 WAN 1
Switch Port 3 VLAN 600 -> HyppTV
Switch Port 4 -> ONU LAN 3
Switch Port 5 VLAN 621 -> BRT-AC828 WAN 2
tom_k3nt
post Mar 31 2019, 08:06 AM

R - E -S - P - 3 -C - T
******
Senior Member
1,068 posts

Joined: Jan 2003
From: Pahang - Kuantan | Selangor - Damansara



Hi,

Am using Asus Ac86u router. Sometimes the router will disconnect from internet for 1 to 2 mins and I notice the log msg date change from today to May and when it back to normal, the log change back to March. Can any 1 pls help?

31 07:44:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:45:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:46:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:47:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:48:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:49:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:50:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:51:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:52:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:52:41 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:54:21 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 07:55:04 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
May 5 13:05:05 kernel: klogd started: BusyBox v1.24.1 (2018-12-04 10:54:31 CST)
May 5 13:05:05 kernel: Linux version 4.1.27 (jenkins@asuswrt-build-server) (gcc version 5.3.0 (Buildroot 2016.02) ) #2 SMP PREEMPT Tue Dec 4 11:29:14 CST 2018
May 5 13:05:05 kernel: CPU: AArch64 Processor [420f1000] revision 0
May 5 13:05:05 kernel: Kernel command line: coherent_pool=1M cpuidle_sysfs_switch
May 5 13:05:05 kernel: Virtual kernel memory layout:
May 5 13:05:05 kernel: vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
May 5 13:05:05 kernel: vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)
May 5 13:05:05 kernel: 0xffffffbe00000000 - 0xffffffbe00700000 ( 7 MB actual)
May 5 13:05:05 kernel: fixed : 0xffffffbffabfd000 - 0xffffffbffac00000 ( 12 KB)
May 5 13:05:05 kernel: PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000 ( 16 MB)
May 5 13:05:05 kernel: modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
May 5 13:05:05 kernel: memory : 0xffffffc000000000 - 0xffffffc020000000 ( 512 MB)
May 5 13:05:05 kernel: .init : 0xffffffc00068a000 - 0xffffffc0006c3000 ( 228 KB)
May 5 13:05:05 kernel: .text : 0xffffffc000080000 - 0xffffffc000689264 ( 6181 KB)
May 5 13:05:05 kernel: .data : 0xffffffc0006c4000 - 0xffffffc00070b9c0 ( 287 KB)
May 5 13:05:05 kernel: Broadcom Logger v0.1
May 5 13:05:05 kernel: creating mapping for reserved memory phys 0x0c400000 virt 0xffffffc00c400000 size 0x00e00000 for dhd1
May 5 13:05:05 kernel: Do not need to create mapping for reserved memory phys 0x0e000000 size 0x02000000 for buffer
May 5 13:05:05 kernel: creating mapping for reserved memory phys 0x0d200000 virt 0xffffffc00d200000 size 0x00e00000 for flow
May 5 13:05:05 kernel: pmc_init:PMC using DQM mode
May 5 13:05:05 kernel: CPU1: Booted secondary processor
May 5 13:05:05 kernel: skbFreeTask created successfully
May 5 13:05:05 kernel: gbpm_do_work scheduled
May 5 13:05:05 kernel: ^[[0;34mBLOG v3.0 Initialized^[[0m
May 5 13:05:05 kernel: BLOG Rule v1.0 Initialized
May 5 13:05:05 kernel: Broadcom IQoS v0.1 initialized
May 5 13:05:05 kernel: Broadcom GBPM v0.1 initialized
May 5 13:05:05 kernel: nand: Could not find valid ONFI parameter page; aborting
May 5 13:05:05 kernel: >>>>> For primary mtd partition rootfs, cferam/vmlinux.lz mounted as JFFS2, vmlinux fs mounted as UBIFS <<<<<
May 5 13:05:05 kernel: Secondary mtd partition rootfs_update detected as JFFS2 for cferam/vmlinux source and UBIFS for vmlinux filesystem
May 5 13:05:05 kernel: Creating 10 MTD partitions on "brcmnand.0":
May 5 13:05:05 kernel: 0x000000540000-0x000006000000 : "rootfs"
May 5 13:05:05 kernel: 0x000006440000-0x00000bf00000 : "rootfs_update"
May 5 13:05:05 kernel: 0x00000f700000-0x00000ff00000 : "data"
May 5 13:05:05 kernel: 0x000000000000-0x000000100000 : "nvram"
May 5 13:05:05 kernel: 0x000000100000-0x000006000000 : "image"
May 5 13:05:05 kernel: 0x000006000000-0x00000bf00000 : "image_update"
May 5 13:05:05 kernel: 0x000000100000-0x000000540000 : "bootfs"
May 5 13:05:05 kernel: 0x000006000000-0x000006440000 : "bootfs_update"
May 5 13:05:05 kernel: 0x00000c700000-0x00000f700000 : "misc2"
May 5 13:05:05 kernel: 0x00000bf00000-0x00000c700000 : "misc1"
May 5 13:05:05 kernel: brcmboard registered
May 5 13:05:05 kernel: brcmboard: brcm_board_init entry
May 5 13:05:05 kernel: print_rst_status: Last RESET due to SW reset
May 5 13:05:05 kernel: print_rst_status: RESET reason: 0x00000000
May 5 13:05:05 kernel: DYING GASP IRQ Initialized and Enabled
May 5 13:05:05 kernel: map_hw_timer_interrupt,132: interrupt_id 22
May 5 13:05:05 kernel: map_hw_timer_interrupt,132: interrupt_id 23
May 5 13:05:05 kernel: map_hw_timer_interrupt,132: interrupt_id 24
May 5 13:05:05 kernel: map_hw_timer_interrupt,132: interrupt_id 25
May 5 13:05:05 kernel: Registering button 0 (ffffffc0007463e0) (bpGpio: 00008017, bpExtIrq:00000000 (0))
May 5 13:05:05 kernel: extIrqIdx:0, gpioNum:23 ACTIVE LOW
May 5 13:05:05 kernel: Registering button 1 (ffffffc0007464a0) (bpGpio: 00008016, bpExtIrq:00000001 (1))
May 5 13:05:05 kernel: extIrqIdx:1, gpioNum:22 ACTIVE LOW
May 5 13:05:05 kernel: Registering button 2 (ffffffc000746560) (bpGpio: 0000800f, bpExtIrq:00000001 (1))
May 5 13:05:05 kernel: extIrqIdx:1, gpioNum:15 ACTIVE LOW
May 5 13:05:05 kernel: genirq: Flags mismatch irq 36. 00000000 (brcm_36) vs. 00000000 (brcm_36)
May 5 13:05:05 kernel: request_irq failed for irq=36 (brcm_36) retval=-16
May 5 13:05:05 kernel: registerBtns: Button index 3 out of range (max 3)
May 5 13:05:05 kernel: BPM: tot_mem_size=536870912B (512MB), buf_mem_size <15%> =80530635B (76MB), num of buffers=35951, buf size=2240
May 5 13:05:05 kernel: Broadcom BPM Module Char Driver v0.1 Registered<3004>^[[0m
May 5 13:05:05 kernel: PCIe HCD (impl1)^M
May 5 13:05:05 kernel: bcm963xx-pcie: found core [0] Rev [ 3. 4]^M
May 5 13:05:05 kernel: pci 0000:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 13:05:05 kernel: pci 0000:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 13:05:05 kernel: bcm963xx-pcie: found core [1] Rev [ 3. 4]^M
May 5 13:05:05 kernel: pci 0001:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 13:05:05 kernel: pci 0001:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 13:05:05 kernel: bcm963xx-pcie: found core [2] Rev [ 3. 4]^M
May 5 13:05:05 kernel: bcm963xx-pcie: failed to bring up core [2] link^M
May 5 13:05:05 kernel: ubi0: attaching mtd0
May 5 13:05:05 kernel: ubi0: scanning is finished
May 5 13:05:05 kernel: ubi0: attached mtd0 (name "rootfs", size 90 MiB)
May 5 13:05:05 kernel: ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 13:05:05 kernel: ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 13:05:05 kernel: ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 13:05:05 kernel: ubi0: good PEBs: 726, bad PEBs: 0, corrupted PEBs: 0
May 5 13:05:05 kernel: ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 13:05:05 kernel: ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 0
May 5 13:05:05 kernel: ubi0: available PEBs: 0, total reserved PEBs: 726, PEBs reserved for bad PEB handling: 15
May 5 13:05:05 kernel: ubi0: background thread "ubi_bgt0d" started, PID 59
May 5 13:05:05 kernel: UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs_ubifs", R/O mode
May 5 13:05:05 kernel: UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 13:05:05 kernel: UBIFS (ubi0:0): FS size: 88375296 bytes (84 MiB, 696 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
May 5 13:05:05 kernel: UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
May 5 13:05:05 kernel: UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID C63E3C9E-0228-41C6-9AE3-4479E5149275, small LPT model
May 5 13:05:05 kernel: wlcsm: module license 'Proprietary' taints kernel.
May 5 13:05:05 kernel: Disabling lock debugging due to kernel taint
May 5 13:05:05 kernel: bm_base_addr 0xffffffc00e000000, size 33554432, bm_base_addr_phys 0x000000000e000000
May 5 13:05:05 kernel: fm_base_addr 0xffffffc00d200000, size 14680064, fm_base_addr_phys 0x000000000d200000
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: RDP Physical address=0x82200000 Virtual address = 0xffffff8000780000
May 5 13:05:05 kernel: configure_runner: NATC keysize 0x100070 key element size 16 contextsize 0x102000 context element size 64
May 5 13:05:05 kernel: ++++Runner gso_desc_pool created successfully
May 5 13:05:05 kernel: rdd_init_params.runner_nat_cache_key_ptr=0xffffffc00d900000
May 5 13:05:05 kernel: FPM_BPM phy_addr 0x82c30000,virt_addr 0xffffff80003fe000
May 5 13:05:05 kernel: RDP PKT memory = 32MB : Max Possible Bufs <16384> of size <2048>; Allocating <15360> bufs; RDP enum <5>
May 5 13:05:05 kernel: brcmchipinfo: brcm_chipinfo_init entry
May 5 13:05:05 kernel: NBUFF v1.0 Initialized
May 5 13:05:05 kernel: ^[[0;36;44mInitialized fcache state^[[0m
May 5 13:05:05 kernel: ^[[0;36;44mBroadcom Packet Flow Cache Char Driver v4.0 Registered<3002>^[[0m
May 5 13:05:05 kernel: Created Proc FS /procfs/fcache
May 5 13:05:05 kernel: ^[[0;36;44mBroadcom Packet Flow Cache registered with netdev chain^[[0m
May 5 13:05:05 kernel: ^[[0;36;44mBroadcom Packet Flow Cache learning via BLOG enabled.^[[0m
May 5 13:05:05 kernel: ^[[0;35m[FHW] pktDbgLvl[0xffffffbffc356588]=0^[[0m
May 5 13:05:05 kernel: ^[[0;34m[FHW] fhw_construct: ^[[0m
May 5 13:05:05 kernel: ^[[0;36;44mInitialized Fcache HW accelerator layer state^[[0m
May 5 13:05:05 kernel: flwStatsThread created
May 5 13:05:05 kernel: ^[[0;36;44mConstructed Broadcom Packet Flow Cache v4.0^[[0m
May 5 13:05:05 kernel: Runner Port#3 (Internal MUX Port#1) connects to Crossbar Port#1
May 5 13:05:05 kernel: Unused MUX Internal Port#0 connects to Crossbar External Port#0
May 5 13:05:05 kernel: Cross Bar MUX Config : Internal Port 00 maps to External Port 00 <reg_val : 0x00000000>
May 5 13:05:05 kernel: Cross Bar MUX Config : Internal Port 01 maps to External Port 01 <reg_val : 0x00000004>
May 5 13:05:05 kernel: Broadcom BCM4906_A0 Ethernet Network Device v0.1
May 5 13:05:05 kernel: dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: ++++ disabling GSO on logical_port=3 dev=eth0
May 5 13:05:05 kernel: eth0: <Int sw port: 3> <Logical : 03> MAC : 40:B0:76:C2:D7:28
May 5 13:05:05 kernel: Chip Physical Port 10, Cross Bar Port 1, PHY_ID <0x0007f00c:0x0c:Internal PHY >
May 5 13:05:05 kernel: eth1: <Ext sw port: 0> <Logical : 08> PHY_ID <0x0007f008:0x08:Internal PHY> MAC:40:B0:76:C2:D7:28
May 5 13:05:05 kernel: eth2: <Ext sw port: 1> <Logical : 09> PHY_ID <0x0007f009:0x09:Internal PHY> MAC:40:B0:76:C2:D7:28
May 5 13:05:05 kernel: eth3: <Ext sw port: 2> <Logical : 10> PHY_ID <0x0007f00a:0x0a:Internal PHY> MAC:40:B0:76:C2:D7:28
May 5 13:05:05 kernel: eth4: <Ext sw port: 3> <Logical : 11> PHY_ID <0x0007f00b:0x0b:Internal PHY> MAC:40:B0:76:C2:D7:28
May 5 13:05:05 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3 --> 8 ]
May 5 13:05:05 kernel: Ethernet Auto Power Down and Sleep: Enabled
May 5 13:05:05 kernel: Cross bar port 1 of Int switch port 3; Adv capability change : MII=0x01e1, GMII=0x0f00
May 5 13:05:05 kernel: Ext switch port 0; Adv capability change : MII=0x01e1, GMII=0x0f00
May 5 13:05:05 kernel: Ext switch port 1; Adv capability change : MII=0x01e1, GMII=0x0f00
May 5 13:05:05 kernel: Ext switch port 2; Adv capability change : MII=0x01e1, GMII=0x0f00
May 5 13:05:05 kernel: Ext switch port 3; Adv capability change : MII=0x01e1, GMII=0x0f00
May 5 13:05:05 kernel: All Port Bit Map: 0x0f08: eth0,eth1,eth2,eth3,eth4
May 5 13:05:05 kernel: Chip WAN Only Ports 0008, Defined WAN Only Ports 0000, WAN Only Port Result: 0x0008:eth0
May 5 13:05:05 kernel: Chip WAN Preffered Ports 0000, Defined WAN Preffered Ports 0000, WAN Preffered Port Result: 0x0000:
May 5 13:05:05 kernel: Chip LAN Only Ports 0f00, Defined LAN Only Ports 0000, LAN Only Port Result: 0x0f00:eth1,eth2,eth3,eth4
May 5 13:05:05 kernel: WAN/LAN Both Capable Ports 0x0000:
May 5 13:05:05 kernel: Creating Enet CPU ring for queue number 1 with 512 packets,Descriptor base=ffffff800025d000, physical=0x1ea0c000
May 5 13:05:05 kernel: Creating Enet CPU ring for queue number 0 with 512 packets,Descriptor base=ffffff8000261000, physical=0x1ea10000
May 5 13:05:05 kernel: ===> Activate Deep Green Mode
May 5 13:05:05 kernel: Initialized Runner Unicast Layer
May 5 13:05:05 kernel: Initialized Runner Multicast Layer
May 5 13:05:05 kernel: ^[[0;36;44mBroadcom Packet Flow Cache HW acceleration enabled.^[[0m
May 5 13:05:05 kernel: Enabled Runner binding to Flow Cache
May 5 13:05:05 kernel: Initialized Runner Protocol Layer (800)
May 5 13:05:05 kernel: Broadcom Runner Blog Driver Char Driver v0.1 Registered <3009>
May 5 13:05:05 kernel: ^[[1m^[[34mWifi Forwarding Driver is initialized!^[[0m
May 5 13:05:05 kernel: broadcomThermalDrv brcm-therm: init (CPU count 2 2 2 2)
May 5 13:05:05 kernel: RDPA DS WAN UDP Filter Command Driver
May 5 13:05:05 kernel: Ethernet Auto Power Down and Sleep: Enabled
May 5 13:05:05 kernel: Energy Efficient Ethernet: Enabled
May 5 13:05:05 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 100 mbps full duplex
May 5 13:05:05 kernel: <=== Deactivate Deep Green Mode
May 5 13:05:05 kernel: ubi1: attaching mtd9
May 5 13:05:05 kernel: ubi1: scanning is finished
May 5 13:05:05 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
May 5 13:05:05 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 13:05:05 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 13:05:05 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 13:05:05 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 13:05:05 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 13:05:05 kernel: ubi1: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 113886647
May 5 13:05:05 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 13:05:05 kernel: ubi1: background thread "ubi_bgt1d" started, PID 349
May 5 13:05:05 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
May 5 13:05:05 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 13:05:05 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 13:05:05 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 13:05:05 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID DA02FFC9-330C-43B0-884B-CD262F788227, small LPT model
May 5 13:05:05 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 13:05:05 kernel: ubi1: detaching mtd9
May 5 13:05:05 kernel: ubi1: mtd9 is detached
May 5 13:05:05 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
May 5 13:05:05 kernel: ubi1: attaching mtd9
May 5 13:05:05 kernel: ubi1: scanning is finished
May 5 13:05:05 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
May 5 13:05:05 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 13:05:05 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 13:05:05 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 13:05:05 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 13:05:05 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 13:05:05 kernel: ubi1: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 113886647
May 5 13:05:05 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 13:05:05 kernel: ubi1: background thread "ubi_bgt1d" started, PID 407
May 5 13:05:05 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
May 5 13:05:05 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 13:05:05 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 13:05:05 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 13:05:05 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID DA02FFC9-330C-43B0-884B-CD262F788227, small LPT model
May 5 13:05:05 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 13:05:05 kernel: ubi1: detaching mtd9
May 5 13:05:05 kernel: ubi1: mtd9 is detached
May 5 13:05:05 kernel: Loading HND Module
May 5 13:05:05 kernel: dpsta_init: msglevel set to 0x1
May 5 13:05:05 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
May 5 13:05:05 kernel: Creating CPU ring for queue number 7 with 128 packets descriptor=0xffffffbffc27d148
May 5 13:05:05 kernel: Done initializing Ring 7 Base=0xffffff8000258000 End=0xffffff8000258800 calculated entries= 128 RDD Base=0x1ea07000K descriptor=0xffffffbffc27d148
May 5 13:05:05 kernel: RDPA returned tx wakeup reg = <0x82299004>, val = <0x10000000>^M
May 5 13:05:05 kernel: RDPA returned rx wakeup reg = <0x8229a004>, val = <0x28000000>^M
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
May 5 13:05:05 kernel: dhd_attach(): thread:dhd_watchdog_thread:247 started
May 5 13:05:05 kernel: Creating CPU ring for queue number 0 with 1024 packets descriptor=0xffffffbffc549cc0
May 5 13:05:05 kernel: Creating CPU ring for queue number 1 with 1024 packets descriptor=0xffffffbffc549cf0
May 5 13:05:05 kernel: ^[[1m^[[34m wfd_bind: Dev eth%d wfd_idx 0 wl_radio_idx 0 Type fkb configured WFD thread wfd0-thrd minQId/maxQId (8/9), status (0) qmask 0x3^[[0m
May 5 13:05:05 kernel: Instantiating WFD 0 thread
May 5 13:05:05 kernel: random: nonblocking pool is initialized
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: dhd_runner_profile_init: N+M profile = 3 01:1024 -1:2048 -1:1024 -1:0512 00:0512^M
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: dhd_runner_policy_init: N+M Policy = 0 1 (HW)
May 5 13:05:05 kernel: ^[[0;33;40mRunner DHD PCIE: vendor<0x14e4> device<0x4365> bus<1> slot<0>^[[0m
May 5 13:05:05 kernel: Initial configuration
May 5 13:05:05 kernel: =================================
May 5 13:05:05 kernel: rx_post_flow_ring_base_addr : ffffffc0170c0000
May 5 13:05:05 kernel: tx_post_flow_ring_base_addr : (null)
May 5 13:05:05 kernel: rx_complete_flow_ring_base_addr : ffffffc017210000
May 5 13:05:05 kernel: tx_complete_flow_ring_base_addr : (null)
May 5 13:05:05 kernel: r2d_wr_arr_base_addr : ffffff8001326000
May 5 13:05:05 kernel: d2r_rd_arr_base_addr : ffffff8001326402
May 5 13:05:05 kernel: r2d_rd_arr_base_addr : ffffff8001326c00
May 5 13:05:05 kernel: d2r_wr_arr_base_addr : ffffff8001326802
May 5 13:05:05 kernel: tx_post_mgmt_arr_base_addr : ffffff8001327000
May 5 13:05:05 kernel: tx_post_mgmt_arr_base_phys_addr : 0x17209000
May 5 13:05:05 kernel: r2d_wr_arr_base_phys_addr : 0x17208000
May 5 13:05:05 kernel: d2r_rd_arr_base_phys_addr : 0x17208402
May 5 13:05:05 kernel: r2d_rd_arr_base_phys_addr : 0x17208c00
May 5 13:05:05 kernel: d2r_wr_arr_base_phys_addr : 0x17208802
May 5 13:05:05 kernel: Doorbell ISR : ffffffbffc645278
May 5 13:05:05 kernel: Doorbell CTX : ffffffc016844000
May 5 13:05:05 kernel: ^[[0;33;40mRunner DHD Offload initialization complete^[[0m
May 5 13:05:05 kernel: Dongle Host Driver, version 1.363.45.84015 (r676423)
May 5 13:05:05 kernel: Compiled in drivers/net/wireless/bcmdhd on Dec 4 2018 at 10:55:50
May 5 13:05:05 kernel: wfd_registerdevice Successfully registered dev eth5 ifidx 0 wfd_idx 0
May 5 13:05:05 kernel: Register interface [eth5] MAC: 40:b0:76:c2:d7:28
May 5 13:05:05 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
May 5 13:05:05 kernel: Creating CPU ring for queue number 1 with 128 packets descriptor=0xffffffbffc27ce48
May 5 13:05:05 kernel: Done initializing Ring 1 Base=0xffffff800025c000 End=0xffffff800025c800 calculated entries= 128 RDD Base=0x1ea0b000K descriptor=0xffffffbffc27ce48
May 5 13:05:05 kernel: RDPA returned tx wakeup reg = <0x82299004>, val = <0x11000000>^M
May 5 13:05:05 kernel: RDPA returned rx wakeup reg = <0x8229a004>, val = <0x29000000>^M
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
May 5 13:05:05 kernel: dhd_attach(): thread:dhd_watchdog_thread:24d started
May 5 13:05:05 kernel: Creating CPU ring for queue number 2 with 1024 packets descriptor=0xffffffbffc549d20
May 5 13:05:05 kernel: Creating CPU ring for queue number 3 with 1024 packets descriptor=0xffffffbffc549d50
May 5 13:05:05 kernel: ^[[1m^[[34m wfd_bind: Dev eth%d wfd_idx 1 wl_radio_idx 1 Type fkb configured WFD thread wfd1-thrd minQId/maxQId (10/11), status (0) qmask 0xc^[[0m
May 5 13:05:05 kernel: Instantiating WFD 1 thread
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: dhd_runner_profile_init: N+M profile = 3 01:1024 -1:2048 -1:1024 -1:0512 00:0512^M
May 5 13:05:05 kernel: Scratch pad is not initialized.
May 5 13:05:05 kernel: dhd_runner_policy_init: N+M Policy = 0 1 (HW)
May 5 13:05:05 kernel: ^[[0;33;40mRunner DHD PCIE: vendor<0x14e4> device<0x4365> bus<1> slot<0>^[[0m
May 5 13:05:05 kernel: Initial configuration
May 5 13:05:05 kernel: =================================
May 5 13:05:05 kernel: rx_post_flow_ring_base_addr : ffffffc015650000
May 5 13:05:05 kernel: tx_post_flow_ring_base_addr : ffffffc00c3c4000
May 5 13:05:05 kernel: rx_complete_flow_ring_base_addr : ffffffc015658000
May 5 13:05:05 kernel: tx_complete_flow_ring_base_addr : ffffffc019228000
May 5 13:05:05 kernel: r2d_wr_arr_base_addr : ffffff8001339000
May 5 13:05:05 kernel: d2r_rd_arr_base_addr : ffffff8001339402
May 5 13:05:05 kernel: r2d_rd_arr_base_addr : ffffff8001339c00
May 5 13:05:05 kernel: d2r_wr_arr_base_addr : ffffff8001339802
May 5 13:05:05 kernel: tx_post_mgmt_arr_base_addr : ffffff800133a000
May 5 13:05:05 kernel: tx_post_mgmt_arr_base_phys_addr : 0x17015000
May 5 13:05:05 kernel: r2d_wr_arr_base_phys_addr : 0x17014000
May 5 13:05:05 kernel: d2r_rd_arr_base_phys_addr : 0x17014402
May 5 13:05:05 kernel: r2d_rd_arr_base_phys_addr : 0x17014c00
May 5 13:05:05 kernel: d2r_wr_arr_base_phys_addr : 0x17014802
May 5 13:05:05 kernel: Doorbell ISR : ffffffbffc645278
May 5 13:05:05 kernel: Doorbell CTX : ffffffc0171ff800
May 5 13:05:05 kernel: ^[[0;33;40mRunner DHD Offload initialization complete^[[0m
May 5 13:05:05 kernel: Dongle Host Driver, version 1.363.45.84015 (r676423)
May 5 13:05:05 kernel: Compiled in drivers/net/wireless/bcmdhd on Dec 4 2018 at 10:55:50
May 5 13:05:05 kernel: wfd_registerdevice Successfully registered dev eth6 ifidx 0 wfd_idx 1
May 5 13:05:05 kernel: Register interface [eth6] MAC: 40:b0:76:c2:d7:2c
May 5 13:05:05 kernel: jffs2: notice: (608) check_node_data: wrong data CRC in data node at 0x012497ac: read 0x783a86d9, calculated 0x7fa54927.
May 5 13:05:05 kernel: ++++ Powering up USB blocks
May 5 13:05:05 kernel: usb3 reseting..........
May 5 13:05:05 kernel: release usb3 reseting..........
May 5 13:05:05 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May 5 13:05:05 kernel: _ Reboot message ... _______________________________________________________
May 5 13:05:05 kernel: Unable to handle kernel paging request at virtual address e8ffffffc0176c3dpgd = ffffffc015369000[e8ffffffc0176c3d] *pgd=0000000000000000, *pud=0000000000000000Internal error: Oops: 96000004 [#1] PREEMPT SMPModules linked in: nf_nat_sip init_addr( (null) - (null)), core_addr(ffffffbffca9e000 - ffffffbffca9f980) nf_conntrack_sip init_addr( (null) - (null)), core_addr(ffffffbffca93000 - ffffffbffca95e80) nf_nat_h323 init_addr( (null) -
May 5 13:05:05 kernel: ____________________________________________________________________________
May 5 13:05:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,202: Could not rdpa_ucast_ipv6_host_address_table_find^[[0m
May 5 13:05:06 nat: apply redirect rules
May 5 13:05:08 dnsmasq[787]: warning: no upstream servers configured
May 5 13:05:08 RT-AC86U: start httpd:80
May 5 13:05:08 httpd: Generating SSL certificate...
May 5 13:05:08 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 100 mbps full duplex
May 5 13:05:08 avahi-daemon[805]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 5 13:05:08 NAT Tunnel: AAE Service is stopped
May 5 13:05:08 AAE: AAE Service is started
May 5 13:05:08 disk monitor: be idle
May 5 13:05:08 hour monitor: daemon is starting
May 5 13:05:08 hour monitor: daemon terminates
May 5 13:05:08 jffs2: valid logs(1)
May 5 13:05:08 miniupnpd[844]: version 1.9 started
May 5 13:05:08 miniupnpd[844]: HTTP listening on port 43509
May 5 13:05:08 miniupnpd[844]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 13:05:08 ERP: The model isn't under support list!
May 5 13:05:09 lldpd[857]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
May 5 13:05:09 avahi-daemon[805]: Alias name "RT-AC86U" successfully established.
May 5 13:05:11 WAN Connection: Fail to connect with some issues.
May 5 13:05:11 kernel: netdev path : eth0.v0 -> eth0
May 5 13:05:11 kernel: netdev path : eth1.v0 -> eth1
May 5 13:05:11 Mastiff: init
May 5 13:05:11 pppd[1115]: pppd 2.4.7 started by admin, uid 0
May 5 13:05:13 WLCEVENTD: eth5: ReAssoc 10:C3:7B:C7:F9:C0
May 5 13:05:13 kernel: ubi1: attaching mtd9
May 5 13:05:13 kernel: ubi1: scanning is finished
May 5 13:05:13 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
May 5 13:05:13 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 13:05:13 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 13:05:13 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 13:05:13 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 13:05:13 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 13:05:13 kernel: ubi1: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 113886647
May 5 13:05:13 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 13:05:13 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1179
May 5 13:05:14 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
May 5 13:05:14 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 13:05:14 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 13:05:14 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 13:05:14 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID DA02FFC9-330C-43B0-884B-CD262F788227, small LPT model
May 5 13:05:15 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 13:05:15 kernel: ubi1: detaching mtd9
May 5 13:05:15 kernel: ubi1: mtd9 is detached
May 5 13:05:16 kernel: ubi1: attaching mtd9
May 5 13:05:16 kernel: ubi1: scanning is finished
May 5 13:05:16 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
May 5 13:05:16 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 13:05:16 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 13:05:16 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 13:05:16 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 13:05:16 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 13:05:16 kernel: ubi1: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 113886647
May 5 13:05:16 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 13:05:16 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1237
May 5 13:05:17 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
May 5 13:05:17 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 13:05:17 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 13:05:17 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 13:05:17 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID DA02FFC9-330C-43B0-884B-CD262F788227, small LPT model
May 5 13:05:17 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 13:05:17 kernel: ubi1: detaching mtd9
May 5 13:05:17 kernel: ubi1: mtd9 is detached
May 5 13:05:19 modprobe: module ledtrig-usbdev not found in modules.dep
May 5 13:05:19 modprobe: module leds-usb not found in modules.dep
May 5 13:05:19 modprobe: module scsi_wait_scan not found in modules.dep
May 5 13:05:19 kernel: SCSI subsystem initialized
May 5 13:05:19 modprobe: module mbcache not found in modules.dep
May 5 13:05:19 modprobe: module jbd not found in modules.dep
May 5 13:05:19 modprobe: module ext3 not found in modules.dep
May 5 13:05:19 modprobe: module ext4 not found in modules.dep
May 5 13:05:19 modprobe: module ext2 not found in modules.dep
May 5 13:05:19 modprobe: module btusbdrv not found in modules.dep
May 5 13:05:19 WLCEVENTD: eth6: Assoc 48:D6:D5:DD:BF:9A
May 5 13:05:32 rc_service: zcip 1336:notify_rc start_firewall
May 5 13:05:32 miniupnpd[844]: shutting down MiniUPnPd
May 5 13:05:32 nat: apply nat rules (/tmp/nat_rules__br1)
May 5 13:05:32 miniupnpd[1384]: version 1.9 started
May 5 13:05:32 miniupnpd[1384]: HTTP listening on port 45092
May 5 13:05:32 miniupnpd[1384]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 13:05:33 zcip client: configured 169.254.12.63
May 5 13:05:37 nat: apply redirect rules
May 5 13:05:38 kernel: ubi1: attaching mtd9
May 5 13:05:38 kernel: ubi1: scanning is finished
May 5 13:05:38 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
May 5 13:05:38 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 13:05:38 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 13:05:38 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 13:05:38 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 13:05:38 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 13:05:38 kernel: ubi1: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 113886647
May 5 13:05:38 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 13:05:38 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1413
May 5 13:05:39 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
May 5 13:05:39 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 13:05:39 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 13:05:39 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 13:05:39 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID DA02FFC9-330C-43B0-884B-CD262F788227, small LPT model
May 5 13:05:39 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 13:05:39 kernel: ubi1: detaching mtd9
May 5 13:05:39 kernel: ubi1: mtd9 is detached
May 5 13:05:46 pppd[1115]: Timeout waiting for PADO packets
May 5 13:05:48 kernel: net_ratelimit: 12 callbacks suppressed
May 5 13:06:48 kernel: net_ratelimit: 34 callbacks suppressed
May 5 13:07:02 pppd[1115]: Timeout waiting for PADO packets
May 5 13:07:48 kernel: net_ratelimit: 34 callbacks suppressed
May 5 13:08:03 WLCEVENTD: eth6: Assoc 04:D6:AA:2A:0A:1B
May 5 13:08:17 pppd[1115]: Timeout waiting for PADO packets
May 5 13:08:17 pppd[1115]: Connected to f0:1c:2d:22:0f:cc via interface br1
May 5 13:08:17 pppd[1115]: Connect: ppp0 <--> br1
May 5 13:08:17 pppd[1115]: PAP authentication succeeded
May 5 13:08:17 pppd[1115]: peer from calling number F0:1C:2D:22:0F:CC authorized
May 5 13:08:17 pppd[1115]: local IP address 175.137.51.66
May 5 13:08:17 pppd[1115]: remote IP address 10.233.33.32
May 5 13:08:17 pppd[1115]: primary DNS address 202.188.18.188
May 5 13:08:17 pppd[1115]: secondary DNS address 1.9.1.9
May 5 13:08:17 rc_service: ip-up 1536:notify_rc start_firewall
May 5 13:08:17 miniupnpd[1384]: shutting down MiniUPnPd
May 5 13:08:17 kernel: net_ratelimit: 34 callbacks suppressed
May 5 13:08:17 nat: apply nat rules (/tmp/nat_rules_ppp0_br1)
May 5 13:08:17 wan: finish adding multi routes
May 5 13:08:17 rc_service: ip-up 1536:notify_rc stop_upnp
May 5 13:08:17 rc_service: ip-up 1536:notify_rc start_upnp
May 5 13:08:17 rc_service: waitting "stop_upnp" via ip-up ...
May 5 13:08:17 miniupnpd[1611]: version 1.9 started
May 5 13:08:17 miniupnpd[1611]: HTTP listening on port 46622
May 5 13:08:17 miniupnpd[1611]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 13:08:17 miniupnpd[1611]: shutting down MiniUPnPd
May 5 13:08:17 WAN Connection: WAN was restored.
May 5 13:08:18 miniupnpd[1626]: version 1.9 started
May 5 13:08:18 miniupnpd[1626]: HTTP listening on port 44429
May 5 13:08:18 miniupnpd[1626]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 13:08:20 ntp: start NTP update
Mar 31 07:58:58 rc_service: ntp 1610:notify_rc restart_diskmon
Mar 31 07:58:58 disk_monitor: Finish
Mar 31 07:58:58 disk monitor: be idle
Mar 31 07:59:37 crond[795]: time disparity of 474891 minutes detected
Mar 31 07:59:56 kernel: net_ratelimit: 130 callbacks suppressed
Mar 31 08:00:56 kernel: net_ratelimit: 34 callbacks suppressed
Mar 31 08:00:58 disk_monitor: Got SIGALRM...


ulala2
post Mar 31 2019, 02:09 PM

Getting Started
**
Junior Member
245 posts

Joined: Jul 2007
Did asus resolve Ac86 unable to detect unifi IPTV after re-switch on the router?

Keep unable to detect unifi IPTV, any quick solution?

This post has been edited by ulala2: Mar 31 2019, 02:19 PM
blacktubi
post Mar 31 2019, 04:06 PM

-
Group Icon
Elite
8,402 posts

Joined: Jul 2008

tom_k3nt
Spoiler the logs please, it is really long.

As usual, update firmware to the latest one and factory reset.

QUOTE(ulala2 @ Mar 31 2019, 02:09 PM)
Did asus resolve Ac86 unable to detect unifi IPTV after re-switch on the router?

Keep unable to detect unifi IPTV, any quick solution?
*
Supposedly fixed on latest firmware.
tom_k3nt
post Mar 31 2019, 07:21 PM

R - E -S - P - 3 -C - T
******
Senior Member
1,068 posts

Joined: Jan 2003
From: Pahang - Kuantan | Selangor - Damansara



QUOTE(blacktubi @ Mar 31 2019, 04:06 PM)
tom_k3nt
Spoiler the logs please, it is really long.

As usual, update firmware to the latest one and factory reset.
Supposedly fixed on latest firmware.
*
Done that already but still will occurs sometimes.... Dunno why... seek your kind advise...
TSASUSmy
post Apr 1 2019, 10:44 AM

Look at all my stars!!
*******
Senior Member
2,319 posts

Joined: Mar 2010
QUOTE(ulala2 @ Mar 31 2019, 02:09 PM)
Did asus resolve Ac86 unable to detect unifi IPTV after re-switch on the router?

Keep unable to detect unifi IPTV, any quick solution?
*
Hi ulala2,

You can refer to my signature before for the firmware. Remember to do a factory reset after the update.

Thank you
TSASUSmy
post Apr 1 2019, 02:40 PM

Look at all my stars!!
*******
Senior Member
2,319 posts

Joined: Mar 2010
QUOTE(tom_k3nt @ Mar 31 2019, 07:21 PM)
Done that already but still will occurs sometimes.... Dunno why... seek your kind advise...
*
Hi tom_k3nt,

I have PM you regarding the problem you faced, do let me know if you need help on the process.

Thank you
ulala2
post Apr 1 2019, 05:07 PM

Getting Started
**
Junior Member
245 posts

Joined: Jul 2007
QUOTE(ASUSmy @ Apr 1 2019, 10:44 AM)
Hi ulala2,

You can refer to my signature before for the firmware. Remember to do a factory reset after the update.

Thank you
*
Dear ASUSMy,

Download the firmware provided, updated it and factory reset after update but still not working.

When i switch back to my RT-AC55, it work well.

TSASUSmy
post Apr 1 2019, 06:25 PM

Look at all my stars!!
*******
Senior Member
2,319 posts

Joined: Mar 2010
QUOTE(ulala2 @ Apr 1 2019, 05:07 PM)
Dear ASUSMy,

Download the firmware provided, updated it and factory reset after update but still not working.

When i switch back to my RT-AC55, it work well.
*
Hi ulala2,

Can you show me the image of the error that you get from the HyppTV?

And what is the HyppTV box model that you are using?

Thank you
junclj
post Apr 2 2019, 04:20 PM

Look at all my stars!!
*******
Senior Member
2,347 posts

Joined: Apr 2008


QUOTE(kktong83 @ Mar 30 2019, 09:07 AM)
My Asus 86u just died, there is no light and no response. But this unit I bought in China 3months ago , does Asus malaysia able to provide warranty?
*
So fast?? Lol, can you describe your house environment? Do you put the router in the dusty area? My house is fully sealed by windows and my RT-AC86U is put inside a cupboard. I never open the my house windows because I only open aircond. So just keep your house away from dust, always keep your house clean. House windows never left opened. Only let oxygen to flow in from toilet exhaust fan and your house main door or kitchen door.
My RT-AC86 was bought at September 2018 from Tmall and received at October 2018. Now already been using for half year, never experience your issue. Did you attach two fans at behind the router? Better just do it if you don't. Since my router is putting inside a cupboard, no open air environment but less dusty. The temperature inside the cupboard is higher until 35'c~40'c, that's why I need to attach two fans on the router to prevent it from overheating.
Lord Suave
post Apr 2 2019, 04:25 PM

Getting Started
**
Junior Member
168 posts

Joined: Nov 2017


Hi AsusMY,

I am current user of DLink DIR890L and recently got VPN (ExpressVPN). I am thinking of doing full system replacement by getting a router which could be installed with the VPN app, based on EVPN website, the applicable models are Asus RT-AC56(U/R/S), Asus RT-AC68U & Asus RT-AC87U. The reason i am going for Asus (most probably 87u) is also to leverage on the AiMesh by buying two Asus routers so that the coverage is sufficient for my double storey house without having to manually switch whenever I go upstairs and vice versa.

My question:
1- If the router was bought in Malaysia (Unifi-compatible) and i perform the app install of ExpressVPN, will i lose the ability to connect to Unifi (probably due to VLAN missing etc)
EVPN Asus Guide

2- Is there any other router from the latest series by Asus that can similarly be installed with the App but ExpressVPN has not updated their website?

My apology if the questions seems too amateurish as I am just learning up on VPN and not an advanced networker. I am just worried that if i were to spend the money and buy I would not be able to totally leverage on the capabilities of my router and would have to go back to manually activating VPN on each devices as I am struggling with right now.
TSASUSmy
post Apr 2 2019, 06:32 PM

Look at all my stars!!
*******
Senior Member
2,319 posts

Joined: Mar 2010
QUOTE(Lord Suave @ Apr 2 2019, 04:25 PM)
Hi AsusMY,

I am current user of DLink DIR890L and recently got VPN (ExpressVPN). I am thinking of doing full system replacement by getting a router which could be installed with the VPN app, based on EVPN website, the applicable models are Asus RT-AC56(U/R/S), Asus RT-AC68U & Asus RT-AC87U. The reason i am going for Asus (most probably 87u) is also to leverage on the AiMesh by buying two Asus routers so that the coverage is sufficient for my double storey house without having to manually switch whenever I go upstairs and vice versa.

My question:
1- If the router was bought in Malaysia (Unifi-compatible) and i perform the app install of ExpressVPN, will i lose the ability to connect to Unifi (probably due to VLAN missing etc)
EVPN Asus Guide

2- Is there any other router from the latest series by Asus that can similarly be installed with the App but ExpressVPN has not updated their website?

My apology if the questions seems too amateurish as I am just learning up on VPN and not an advanced networker. I am just worried that if i were to spend the money and buy I would not be able to totally leverage on the capabilities of my router and would have to go back to manually activating VPN on each devices as I am struggling with right now.
*
Hi Lord Suave,

The ExpressVPN APP provided by ExpressVPN are customize firmware to connect to ExpressVPN easily. The AiMesh feature will be gone if you use their firmware. I would suggest you to have a look at the video below, this setup doesn't need to install the APP, ASUS original firmware will do the trick.

https://youtu.be/0BihQPiqjgw

Thank you
Lord Suave
post Apr 2 2019, 09:39 PM

Getting Started
**
Junior Member
168 posts

Joined: Nov 2017


QUOTE(ASUSmy @ Apr 2 2019, 06:32 PM)
Hi Lord Suave,

The ExpressVPN APP provided by ExpressVPN are customize firmware to connect to ExpressVPN easily. The AiMesh feature will be gone if you use their firmware.  I would suggest you to have a look at the video below, this setup doesn't need to install the APP, ASUS original firmware will do the trick.

https://youtu.be/0BihQPiqjgw

Thank you
*
wow, thanks so much for understanding my predicament!
decided now that will be getting AC-86U as my main router and AC-68U as my node under AiMesh or AC-88U as main and 86U as node.

Can i confirm that both 68U or 88U when act as main router, both 5Ghz and 2.4Ghz can be setup under one SSID and traffic would be automatically assigned to minimize the clog of bandwidth? also can i confirm that the node will not require manual activation of node when i roam into area of coverage?

oh btw, the main router will be upstairs and i have ran network cable to downstairs area where i could plug in the node to allow aimesh via ethernet

This post has been edited by Lord Suave: Apr 2 2019, 09:42 PM
Nando's
post Apr 3 2019, 09:07 AM

Casual
***
Junior Member
431 posts

Joined: Dec 2012
From: Kitchen
Hi, can i setup AiMesh through switch?

E.g. Asus RT86U -> Switch -> Asus RT86U

826 Pages « < 500 501 502 503 504 > » Top
 

Change to:
| Lo-Fi Version
0.0332sec    0.42    6 queries    GZIP Disabled
Time is now: 4th December 2025 - 10:40 AM