Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. J

    Router crashes repeatedly when Guest Network 1 (5Ghz) is used and IPv6 is configured on the router

    Good day @ASUSWRT_2020 . Just sharing that the closed source Guest Network function has some significant bugs in it. I have tested this with build FW_RT_AX56U_300438645898 but I believe the faults can be replicated with any 386 based build. If you use Guest Network 1 (I used 5Ghz band) and...
  2. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    This is "solved". Here is a summary. Asus provides 3 guest networks, which I believe is a closed source function from Asus. Guest Network 1: uses 192.168.101.x and 192.168.102.x IP range, optimized for AIMesh and does not support IPv6 (although that is not documented by Asus as such) Guest...
  3. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    Thanks @dave14305 for your help & knowledge. The Asus guest networks on the 386 builds are really messed up as compared with the old 384 code base. So: Guest Network 1: uses 192.168.101.x and 192.168.102.x IP range, optimized for AIMesh and does not support IPv6 (using Guest Network 1 is...
  4. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    The parameters are the same such as mtu 1500 qlen 1000 ra-param=br0,10,600 enable-ra quiet-ra dhcp-range=lan,::,constructor:br0,ra-stateless,64,600 Yes I am using guest networks 1 and 2 because Asus designed the function to give these 2 network unique IP address ranges not shared with the...
  5. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    Thanks @dave14305. Appreciate your troubleshooting expertise. I ran your commands on both builds and here are my findings: - From your shell commands, the parameters for both the 384.18 and the 386.3-2 builds are identical on my router. - The commands confirm what the GUI shows. The 384.18...
  6. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    Much appreciated. This is very useful. Will circle back once I have the comparison done.
  7. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    Well the mystery deepens! Glad it is working for you.
  8. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    Will do
  9. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    I went back to the 384.18 build to get the users up and running but can test this later on late today or tomorrow.
  10. J

    Solved IPv6 Native with Prefix Delegation does not provide LAN side IP addresses in any 386 Build on RT-AX56U

    As part of testing why the 386 based builds are unstable in my configuration on my RT-AX56U, I noticed that on the 384.18 build that IPv6 works great and 1) I have 9 devices with LAN side IPv6 addresses and 2) the SYSTEM LOG -> WIRELESS matches the SYSTEM LOG -> IPv6, meaning that the LAN side...
  11. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    TEST 1 I just got to 5 days without any crashes on my RT-AX56U running firmware version 384.18. In my configuration I have: - Two main networks (2.4 and 5.0 Ghz using WPA2 and fixed channels) - Two guest networks (using 1 and 2 with WPA2 on both) - Stubby DNS over TLS with 4 IPv4 and 4 IPv6...
  12. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    That sounds like a good plan. For me, once I get through the weekend confirming stability on 384.18 or not, I will reduce my configuration on the 386 base by taking away Stubby and IPv6. If it is still not stable, I will remove the guest networks.
  13. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    The other odd thing that I notice is that on the 384.18 build, I have 7 devices that pick up IPv6 addresses on the LAN side (in the IPv6 log). On any of the 386 builds (386.3-2, 386.2-2 and 386.4 alpha 1), the LAN side (IPv6 log) will have 0 devices or sometimes 1 device. And on the 386...
  14. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    Personally, I login once a day and look at the uptime on the General Log page. If you look after 7 days when the logfile is pretty large, it can be a science project to figure out what the uptime is and how many crashes have been experienced. I am only myself checking once a day to develop an...
  15. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    I clean flashed 386.4 alpha1 when I first got the RT-AX56U router 2 weeks ago, and it was immediately crashing after running for 1/2 a day on a brand new router that had never been configured. All of the 386 builds behave the same way on the RT-AX58U (I have had 2 of them) and the RT-AX56U (a...
  16. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    My opinion is that it is the 386 code base that is causing these crashes. I have gone back to 384.18 on my RT-AX56U with a clean flash to see if I can run for 5-7 days without a crash which I cannot do on the 386 code base (386.3-2, 3862-2 both experience 1 - 2 crashes a day and I also get...
  17. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    A basic design principle is that a client should not be able to cause a restart of a superior node in the network; a basic principle of defensive SW design. It should not be possible for my clients to crash my router. Most of the WIFI chips in our devices are made by just 4 companies: Intel...
  18. J

    RT-AX3000 crashing every few days in bcmsw_rx (Tried hw/sw reset/rebuilds and even new replacement router)

    I have had the same problems on 2 different RT-AX58U units that I no longer have, and now a brand new 2 week old RT-AX56U running 386.3_2. My latest crash I also posted today. Current crash log points to bcm_mcast_netlink_process_snoop_cfg May 5 01:05:00 crashlog: <4>^[[0;33;41m[ERROR mcast]...
  19. J

    RT-AX56U on 386.3_2 crashed out

    I have an RT-AX56U that is about 2 weeks old. It most recently crashed yesterday on 386.3_2. I am running IPv6, 2 Guest networks, 2 Main networks and DNS over TLS (both IPv4 & IPv6), no USB connected devices. Appreciated your ideas of what is going on as I need to send this router back in the...
  20. J

    [ 386.4 alpha Build(s) ] Testing available build(s)

    What kind of CPU and wireless temperatures are you seeing a) during low load and b) during high load? What kind of CPU loads do you see?
Top