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

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    Maybe @ASUSWRT_2020 could change the Guest Network setting to allow 3 choices instead of just Access Intranet = Enabled or Disabled. The settings called be called Enabled, Disabled and AP Isolation. Option 1) Access intranet enabled (same as current setting ENABLED) Option 2) Access intranet...
  2. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    I did a dirty flash from 386.1 Beta 2. The aim is to check the behavior of these variables. After dirty flash, I checked that wl0.1_ap_isolate = 1 and all 5 others = 0. That is my baseline. I then made changes to the Guest Networks, and I found that any Guest Network that I saved with...
  3. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    Hi @john9527 , I do not see a change in behavior with the patch. Even with the patch applied, if I set Guest Network Access Intranet = Disable and apply the Guest Network settings, the Guest Network function will set wlx.y_ap_isolate = 1 which is what also kills ChromeCast. With or without...
  4. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    Thanks @john9527 ! A quick question. Not sure if it is what Asus intended or not but in the 386.1 builds, the wlx.y_ap_isolate setting seems to survive restart in my testing. What is the change in the patch so I test it correctly?
  5. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    RT-AX58U. Thanks @john9527
  6. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    In the past 384 builds, nothing. In the 386 builds, the first guest network is on a completely different subnet. The first guest network uses subnet 192.168.101.0/24 for 2.4Ghz and 192.168.102.0/24 for 5Ghz. See the first post...
  7. J

    Beta Asuswrt-Merlin 386.1 Beta is now available

    Upgraded from Beta 1 to Beta 2 on my RT-AX58U. Seems solid. Aunt Budge very happy. New function reporting HW acceleration from HW instead of a parameter is a great idea.
  8. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    Nope have not tried the YazFi scripts on 386.
  9. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    In my testing, the AP isolate variable appears to work the same way for all Guest Networks.
  10. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    Setting AP isolate = 0 for the Guest Network variables (keep in mind there are separate AP isolate variables for the main radios) survives restart of the router. If you make any change to the Guest Network via the GUI while Access Intranet is set to Disabled in the GUI, it will write the...
  11. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    @JimbobJay and @ColinTaylor, you can be my IT psychologists as you understand me. :)
  12. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    @ColinTaylor you nailed it. The Access Intranet = Disabled setting for Guest Networks in addition to packet filtering rules is setting ap_isolate = 1 on the 386 builds. This was never done on the 384 builds. This is what is breaking Chromecast as the clients on the same SSID cannot...
  13. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    Asus probably needs to separate "AP Isolation" which is a parameter from "Access Intranet" which is a user settable function in the Guest Network GUI. As a suggestion, Asus could have these as 2 user settable selections in the Guest Network GUI.
  14. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    In software, the biggest frustration for customers is finding something that worked in the old release broken in the new release. Simplest way I can put it. Using the 1st 5Ghz Guest Network as an example, with Guest Network on and Intranet Access set to disabled, wl1.1_ap_isolate=0 in the 384...
  15. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    I've been using Chromecast on the 384 based Merlin since the early part of this year. I have all IoT devices including phones and tablets on the same guest network. And I agree with you, the guest network should be isolated from the inside network. :) It has worked like this on the 384...
  16. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    C states Intranet, meaning any other subnet on the router
  17. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    For clarity, this issue did not exist on the 384 builds and "wl0.x_ap_isolate" and "wl1.x_ap_isolate" are set to 0 as the default on the 384 builds. I tested using both guest network 1 and 2 on the 386.1 Beta 1 build with Access Intranet set to Disable in the GUI and manually set...
  18. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    Not using Diversion. Plain vanilla Asus Merlin.
  19. J

    Guest Network on 386 builds doesn't play nice with Chromecast, and a potential workaround

    I noticed that Chromecast is not working on build 386.1 Beta 1 on my RT-AX58U. I am using a Guest Network for IoT devices including all my Chromecast devices. Chromecast of course functions by allowing devices on the same WIFI network to connect to each other via casting. On the 386.1 Beta 1...
  20. J

    Beta Asuswrt-Merlin 386.1 Beta is now available

    Seeing these messages on RT-AX58U with latest 386.1 Beta 1 release. Not a critical issue or anything, just curious what these kernel messages are and if our fellow RT-AX58U users on latest 386.1 Beta 1 are seeing same messages. Noticed that @Trent Hubbert got these messages a couple months...
Top