Some sites block IP addresses coming from known VPN providers, due to past abuses.has anyone any ideas how to cure this?
dcd crashes are long-standing issue that Trend Micro seems to not care enough to fully address (there are many different causes for these dcd crashes). The issues have been there for years, and by now they are fully aware of their existence.AX86U
388.1_beta2
Your router is running out of memory. If you use any third party addon that can use a lot of memory (like Diversion with large lists), remove them.hi every 5 secs i am getting this error on AX88U beta2:
There are so many scenarios that will enable/disable flow cache, since Asus hasn't implemented a robust way to do so, some of these events can incorrectly re-enable it without checking first if it should be kept disabled. Without knowing the exact scenario triggering this, it will be difficult to track down. You would need to trace back your steps to figure out whichShouldn't Flow Cache be disabled?
I think here is what you want.When you search the log, is there any call that reenables HW Acceleration after above entry?
Does your router correctly reboot after you enable cake?I rebooted after enabling Cake and Flow Cache is disabled now. HW Accel is still enabled.
I think here is what you want.
May 4 23:05:02 kernel: ===> Activate Deep Green Mode
May 4 23:05:02 kernel: dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered
May 4 23:05:02 kernel: Broadcom Command List Driver v1.0
May 4 23:05:02 kernel: Initialized Runner Host Layer
May 4 23:05:02 kernel: Initialized Runner Unicast Layer
May 4 23:05:02 kernel: Initialized Runner L2 Unicast Layer
May 4 23:05:02 kernel: Initialized Runner Multicast Layer
May 4 23:05:02 kernel: Retrieve num_fhw_path=64
May 4 23:05:02 kernel: ^[[0;36;44mBroadcom Packet Flow Cache HW acceleration enabled.^[[0m
May 4 23:05:02 kernel: Enabled Runner binding to Flow Cache
May 4 23:05:02 kernel: Initialized Runner Protocol Layer (800)
May 4 23:05:02 kernel: Broadcom Runner Blog Driver Char Driver v0.1 Registered <3009>
And this as well.
May 4 23:05:02 kernel: DHD_FKB_POOL size is:1280 and entry size:2816
May 4 23:05:02 kernel: DHD_PKTTAG POOL size is:2592 and entry size:128
May 4 23:05:02 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device AAA4(good PCI location)
May 4 23:05:02 kernel: pcieh 0000:01:00.0: enabling device (0000 -> 0002)
May 4 23:05:02 kernel: dor0: runner supported ring format types TxP 0x5, RxP 0x3 TxC 0x3 RxC 0x3^M
May 4 23:05:02 kernel: dhd_runner_attach: Tx Offload - Enabled, Ring Size = 1024
May 4 23:05:02 kernel: dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
May 4 23:05:02 kernel: TX wakeup info: reg = <0x82299004>, val = <0x10000000>
May 4 23:05:02 kernel: RX wakeup info: reg = <0x8229a004>, val = <0x28000000>
May 4 23:05:02 kernel: CFG80211-ERROR) wl_setup_wiphy : Registering Vendor80211
May 4 23:05:02 kernel: dhd_attach(): thread:dhd_watchdog_thread:275 started
May 4 23:05:02 kernel: Creating CPU ring for queue number 0 with 1024 packets descriptor=0xffffffbffc54a8c0
May 4 23:05:02 kernel: Creating CPU ring for queue number 1 with 1024 packets descriptor=0xffffffbffc54a900
May 4 23:05:02 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 4 23:05:02 kernel: Instantiating WFD 0 thread
May 4 23:05:02 kernel: dor0: MSG Ring format set to 1
May 4 23:05:02 kernel: dhd_runner_flowmgr_init: dhd0_rnr bootmem addr<ffffffc00a600000> size<14680064>
May 4 23:05:02 kernel: dhd_runner_profile_init: N+M profile = 3 01:1024/0512 -1:2048/1024 -1:1024/0512 -1:0512/0512 00:0512/0512
May 4 23:05:02 kernel: dhd_runner_policy_init: N+M Policy = 0 1 (HW)
Funny you should say that. When I enabled it after my reset to defaults, yes it needed a reboot right away. However when disabling and re-enabling with a elective reboot in between, the router does not require a reboot upon enabling.Does your router correctly reboot after you enable cake?
At the non-technical level, Wireguard and Broadcom's AX chipsets just don't play nicely together. Furthermore, disabling Flow Control will limit the speed for all devices, not just those on the VPN tunnels. As noted in previous threads if you want to use Wireguard with a fast ISP, don't run it on the router. Whether you can get better results by moving Wireguard to another host (your NAS, a Pi, something else) is for others to advise.Found out that without flow cache enabled I cant achieve 1 gig speeds on any device. But having flow cache enabled Wireguard wont work anymore. Why is that? Should I just disable wireguard VPN on my router and not use it on VPN Director to my NAS and instead install Windows software for Wireguard on my NAS to achieve better speeds for all devices in my network. I really wish that I could use my router for this.
At the non-technical level, Wireguard and Broadcom's AX chipsets just don't play nicely together. Furthermore, disabling Flow Control will limit the speed for all devices, not just those on the VPN tunnels. As noted in previous threads if you want to use Wireguard with a fast ISP, don't run it on the router. Whether you can get better results by moving Wireguard to another host (your NAS, a Pi, something else) is for others to advise.
Do you use DNS-over-TLS with your setup?Whatever you may think of IPv6, certainly works smooth & snappy here. No latency issues.
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0000
May 5 07:05:11 kernel: brcmboard registered
May 5 07:05:11 kernel: genirq: Flags mismatch irq 34. 00000000 (brcm_34) vs. 00000000 (brcm_34)
May 5 07:05:11 kernel: gluebi (pid 1): gluebi_resized: got update notification for unknown UBI device 0 volume 0
May 5 07:05:11 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link DOWN
May 5 07:05:11 kernel: bcm_enet_init:L2453 ENET system contructed and configured enet-kthrd thread
May 5 07:05:11 kernel: enet_kthread_handler:L296 Instantiating ENET thread
May 5 07:05:11 kernel: Lservices Loaded - NComm, Inc.
May 5 07:05:11 kernel: exLinuxETH Loaded - NComm, Inc.
May 5 07:05:11 kernel: broadcomThermalDrv brcm-therm: init (CPU count 4 4 4 4)
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1200
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5200
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9200
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8800
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9000
May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9800
May 5 07:05:11 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link UP
May 5 07:05:11 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 1000 mbps full duplex
May 5 07:05:11 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
What DNS servers are you using for your ipv6? Try cloudflares' or google DnS if not already.
Installed beta2 on my AX86U and got the following during boot (never saw this with previous 386 firmwares). Do I have to worry about? Everything seems normal so far.
Code:May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0000 May 5 07:05:11 kernel: brcmboard registered May 5 07:05:11 kernel: genirq: Flags mismatch irq 34. 00000000 (brcm_34) vs. 00000000 (brcm_34) May 5 07:05:11 kernel: gluebi (pid 1): gluebi_resized: got update notification for unknown UBI device 0 volume 0 May 5 07:05:11 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link DOWN May 5 07:05:11 kernel: bcm_enet_init:L2453 ENET system contructed and configured enet-kthrd thread May 5 07:05:11 kernel: enet_kthread_handler:L296 Instantiating ENET thread May 5 07:05:11 kernel: Lservices Loaded - NComm, Inc. May 5 07:05:11 kernel: exLinuxETH Loaded - NComm, Inc. May 5 07:05:11 kernel: broadcomThermalDrv brcm-therm: init (CPU count 4 4 4 4) May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1200 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5200 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9200 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa0800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa1800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa2800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa3800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa4800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa5800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa6800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa7800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa8800 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9000 May 5 07:05:11 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xa9800 May 5 07:05:11 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link UP May 5 07:05:11 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 1000 mbps full duplex May 5 07:05:11 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
Yes.Do you use DNS-over-TLS with your setup?
No issues here. Auto channel enabled, (but no DFS channels).Well, not sure how much is it considered as a bug, but worth mention it.
Beta2, Ax88U
The WiFi 5Ghz is having hard time to start broadcast.
It takes 2-3 min, used to happen when Ch control was set to auto.
Now it fixed to a certain channel and still takes 2-3 min.
On Beta1 everything was just fine.
Any known changes to AX88U between 2 Beta?
Not sure why.
You are using a mix of filtered, Quad9, and unfiltered, Cloudflare DNS resolvers which is not giving you the best protection from malware and other bad actors.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!