Menu
What's new
By:
Filters Better Search

Recent content by rickard

  • 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. R

    Device stuck on wrong IP

    Well, the guest network seems to be isolated, the primary DNS set in router for "normal" network is not reached if I try to ping it, but it's still given as the guest network's primary DNS, which it obviously shouldn't. I guess Asus didn't take into account that a DNS could be located in the...
  2. R

    Device stuck on wrong IP

    You're probably right about that theory! I guess that my setup is actually working as intended, even though at first it did not seem so. :) Thank you for all your help, Colin! I have seen in the other threads that you are a big help around here. Rickard
  3. R

    Device stuck on wrong IP

    Ok, that's good, I guess! :) I can buy that the IoT network also get a "1.*" address, now that I see that this is how it works, but should not the DNS be set to the router, rather than the local core DNS, just like the other guest network is behaving (DNS is set to 101.1)?
  4. R

    Device stuck on wrong IP

    Hmm... strange things going on here, but you may be onto something. If I connect my workstation to the guestnet, it gets a 102 address and DNS set to .1, just as expected. If I connect the workstation to the IoT network, I get a 1.* address, just like you said, and DNS set to 1.200 (which is my...
  5. R

    Device stuck on wrong IP

    This is an illustration of my guest networks: ** Tried to make it clear with both tabs and spaces, but those were removed, sorry... ** 2,4 GHz Network Name (SSID) ** GuestNet ** IoT ** Not enabled Authentication Method ** WPA2/WPA3-Personal...
  6. R

    Device stuck on wrong IP

    Well, yes and no. I have enabled the first column (both 2.4 and 5 GHz), which should be the first guest network, but that guest network get the 102-range. The next column is my IoT network (only 2.4 GHz), and that is given the 101-range by the router. Maybe I activated the second column before...
  7. R

    Device stuck on wrong IP

    Hello! I have just bought and configured mu Asus RT-AX86U, and I am generally happy with it! :) But, there's this one thing... I want one of my devices on a guestnet for IoT devices, which should be isolated from my core network (intranet). My core network uses the "192.168.1.*" addresses...
See more
Top