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. technet

    AiMesh: clients keep connecting to the wrong AP

    Ended up moving the Mesh AP to a better position until a better solution comes (is on its way): an external access point. Yes, there was obstacles between the AP and clients (a led TV, etc.), so connection was being lost, clients moving to the main distant router, etc.
  2. technet

    AiMesh: clients keep connecting to the wrong AP

    Devices loses connection (inacessible) and shows as connected to the router (office) and not the AiMesh node, Living Room, which is expected. Shouldn't Bind work as expected, avoiding client roaming between nodes?
  3. technet

    AiMesh: clients keep connecting to the wrong AP

    We also noticed that the AiMesh node has enabled leds after a reboot, even if they were set as off.
  4. technet

    AiMesh: clients keep connecting to the wrong AP

    On a 2 RT-AX88U AiMesh setup, 2.4 Ghz clients are binded to the closest AP and after some time they still connect to the main, distant AP. Network is a Guest Network set to be on all AiMesh Nodes. At the AiMesh Topology, we see clients with an attention mark reporting "This device is currently...
  5. technet

    DNSOMATIC new API Settings

    Solved using the same password created for the new https://login.opendns.com account. Details about the change: https://support.opendns.com/hc/en-us/articles/360037648951
  6. technet

    DNSOMATIC new API Settings

    I'm always using the username, worked for years. Still getting "authentication failed" here - credentials are correct and they don't have special characters/symbols.
  7. technet

    RT-AX88U issues with DNS-O-Matic and System Log

    Is the system log issue related to that? protocol 86dd is buggy, dev eth7
  8. technet

    DNSOMATIC new API Settings

    Ours not working yet. And email/username field only accepts 32 characters - our email is larger than that.
  9. technet

    RT-AX88U issues with DNS-O-Matic and System Log

    On a RT-AX88U running AsusWRT Merlin 386.3_2, we are getting the following output at system log: Dec 13 18:12:00 inadyn[19644]: Fatal error in DDNS server response: Dec 13 18:12:00 inadyn[19644]: [401 Unauthorized] badauth Dec 13 18:12:00 inadyn[19644]: Error response from DDNS server, exiting...
  10. technet

    IPv6 DNS

    Correct, so it is. Thank you, @dave14305.
  11. technet

    IPv6 DNS

    Hello! Router is RT-AX88U with 386.3_2 firmware. Clients are getting ISP IPv6 DNS instead of Google IPv6 DNS (DoT), manually set. System Log > IPv6 shows the expected Google DNS, 2001:4860:4860::8888 2001:4860:4860::8844. Is this the expected behaviour or we are doing something wrong?
  12. technet

    Channels above 11 on Asus RT-AC87U: possible?

    Wifi Analyzer always shows me that 2.4 Ghz channels above 11 would be the recommended ones. On the interface of the latest Asuswrt-Merlin for RT-AC-87U, 380.67, I can't select channels higher than 11. There are any possible way to use channels higher than this? Thanks!
  13. technet

    Transparent Netflix only region unblock with Asuswrt Merlin

    One file, you meant? dnsmasq.conf.add
  14. technet

    Transparent Netflix only region unblock with Asuswrt Merlin

    The procedures on https://gist.github.com/epeli/9789586 aren't working anymore. What's the recommended method to undo the changes from Asuswrt-Merlin? I've done it with WinSCP. Does anyone have an updated method to overcome the region blocking of Netflix?
  15. technet

    Asuswrt-Merlin 378.51 Beta 1 is out

    RT-AC87U. Reset before and after upgrade. DNS-O-MATIC DDNS does not update automatically, only when forced on DDNS page. WAN type is PPPoE.
  16. technet

    Asuswrt-Merlin 378.50 is out

    AC87U upgraded after a factory reset. Using PPPoE WAN we lost NAT Loopback after a couple of hours. Only way to get it working again is the same: completely disabling CTF.
  17. technet

    Dual WAN: fail over does not work correctly

    AC87U with latest Merlin build. Main WAN is a PPPoE, secondary WAN is by DHCP. When the main fails, the second takes a long time to assume and then link keeps going down, back to the first one, then to the second... Tried any possible combination of setttings for fail over, without...
Top