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

    Release Asuswrt-Merlin 386.12 is now available for AC models

    I'm also experiencing wireless stability issues on my RT-AC5300 after upgrading to 386.12_4. Currently debating rolling back vs. fiddling with settings mentioned earlier in this thread. Either way, not a good experience. The writing is on the wall for these EOL routers.
  2. orion44

    Asus EOL = Merlin EOL?

    Yes, that's exactly what happened to my RT-N66U – no more routing duties or WAN access.
  3. orion44

    Asus EOL = Merlin EOL?

    As an example, the ASUS End-of-life product list page (https://www.asus.com/event/network/EOL-product/) lists the RT-AC5300 as an EOL model. Is it safe to assume it will soon be moved to the "No longer supported" list on Merlin's page https://www.asuswrt-merlin.net ?
  4. orion44

    386.4 on AC88U breaks Chromecast device detection

    I'm also experiencing the issue with Chromecast devices disappearing since 386.4 on a RT-AC5300. If I reboot the router the Chromecast devices are discoverable again. Did not happen prior 386.4, so I'll look into some the workarounds mentioned while I wait for the next firmware release.
  5. orion44

    Cannot access web interface after upgrade to 386.1_2 on AC5300

    Well, despite the crippled search functionality of this forum and RMerlin's general hatred of the end-user, it could be beneficial for anyone experiencing web gui slowness/unresponsiveness after upgrading to 386.1_2 to monitor when the issue (database maintenance) is resolved: ssh into your...
  6. orion44

    386.1 on AC68U locks up web interface

    Thanks, I was looking for which process is doing the db maintenance after the 386.1_2 upgrade. Unable to find it because the search functionality of this forum sucks now – error: "The search could not be completed because the search keywords were too short, too long, or too common."
  7. orion44

    DDNS error - "PID file /var/run/inadyn.pid already exists, inadyn already running?"

    Earlier this morning, my ISP had some major issues that led my home IP address to change. This was done without a modem reboot (upstream of my RT-AC5300) – but I see in the router logs the WAN state correctly changed from down to up. However, my DDNS settings did not correctly pull the new IP...
  8. orion44

    SNMP monitoring issue after upgrading to 384.4_2 on RT-AC5300

    Yes, SNMP is dead. Long live SNMP!
  9. orion44

    YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

    Solution: The following YazFi fields are now required wl01_FORCEDNS wl01_CLIENTISOLATION Adding these to my config with the appropriate values resolved my issue.
  10. orion44

    YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

    After upgrading my RT-AC5300 firmware to 384.16 and YazFi to v4.0.2 my wireless clients can no longer connect through the VPN tunnel. I'm also seeing a constant flood of multicast DNS traffic hitting my LAN originating from the guest WiFi (172.16.1.1:5353 going to 224.0.0.251:5353). Clients...
  11. orion44

    [Release] Asuswrt-Merlin 384.15 (and 384.13_4) are now available

    Thanks for the quick reply. I don't use AiMesh or have any related features enabled, so I'll just ignore the error for now.
  12. orion44

    [Release] Asuswrt-Merlin 384.15 (and 384.13_4) are now available

    No issues upgrading RT-AC5300 to 384.15 but I'm seeing syslog flooded with these errors now: Feb 10 10:47:28 dnsmasq-script[1256]: connect error: No such file or directory Feb 10 10:47:28 dnsmasq-script[1256]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory. Do I need...
  13. orion44

    [Release] Asuswrt-Merlin 384.12 is now available

    I set the syslog to maximum verbosity and no clues were provided. The solution was to reconfigure the OpenVPN client from scratch. It'll remain forever unknown as to why the firmware update borked the config.
  14. orion44

    [Release] Asuswrt-Merlin 384.12 is now available

    ProtonVPN client no longer works on 384.12 and hangs indefinitely while attempting to connect. "Error check configuration" Changing new Inbound Firewall settings to Allow/Block have no effect. Currently using @Jack Yaz's YazFi 3.2.2 to redirect VPN Client (ProtonVPN) traffic to guest wireless...
  15. orion44

    YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

    Testing the new menu and it's not showing the hostname or IP address of my device (Raspberry PI) connected to the guest network. I've confirmed the device is connected and the DHCP process completed successfully. Feb 12 10:17:55 192.168.1.1 Feb 12 10:17:48 dnsmasq-dhcp[343]: DHCPACK(wl0.1)...
  16. orion44

    YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

    Yes and YES! I didn't see that post - it's exactly my issue.
  17. orion44

    YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

    Yes, but I'm not entirely sure these timestamps are from rebooting the entire system.
  18. orion44

    YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

  19. orion44

    YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

    I'm not sure if this is expected or not, but I recently restarted by router via the GUI and YazFi did not start automatically. When I attempted to connect to the guest WIFI configured for YazFi, no IP was assigned via DHCP. The device assigned itself an APIPA address and that was about it. I...
  20. orion44

    So...Do I have to wait for the next firmware again?

    I wrote the post regarding the MikroTik routers and we've seen 600,000+ compromised MikroTik routers worldwide since July. The problem was exacerbated due to two reasons: The Winbox management port (8291/tcp) was exposed to internet. The RouterOS (firmware) was not updated after a...
Top