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

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

    Interesting, I wasn't aware as a new user. Would be nice to have both perhaps, such as: 2.4GHz Guest 1 (LAB) ... if that wouldn't complicate/break the script functionality.
  2. orion44

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

    Tested YazFi with 384.7_2 and it works PERFECTLY! All guest wifi subnet traffic is routed through VPN client and an intensive nmap scan yields no leaks to the 192.168.1.0/24 LAN subnet. A feature request I have is a minor change. My guest network SSID is named "LAB" and it would be beneficial...
  3. orion44

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

    Interesting, thanks for sharing. I've never used collectd previously and it looks way more accurate than SNMP under the current firmware.
  4. orion44

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

    Thanks for the quick reply. After further debate, I've decided to sacrifice accurate traffic (SNMP) monitoring to stay on the current firmware branch (see: https://www.snbforums.com/threads/snmp-monitoring-issue-after-upgrading-to-384-4_2-on-rt-ac5300.46512/). I'll be using your add-in with...
  5. orion44

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

    Interesting read, saw that post while searching if the SNMP issues might have been resolved. Will try a dirty upgrade and see.
  6. orion44

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

    It's PRTG.
  7. orion44

    How does the Guest Network "Access Intranet" feature actually work?

    YES! admin@RT-AC5300-F8D0:/tmp/home/root# ebtables -L Bridge table: filter Bridge chain: INPUT, entries: 0, policy: ACCEPT Bridge chain: FORWARD, entries: 2, policy: ACCEPT -i wl0.1 -j DROP -o wl0.1 -j DROP Bridge chain: OUTPUT, entries: 0, policy: ACCEPT...
  8. orion44

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

    Does this work with Merlin legacy firmware 380.70?
  9. orion44

    How does the Guest Network "Access Intranet" feature actually work?

    I've never used the Guest Network feature previously so I'd assumed the "Access Intranet" (block LAN traffic) feature worked via iptables similar to the Parental Controls. However, after turning on a guest network and enabling "Access Intranet" I observed no changes being made to the iptables. I...
  10. orion44

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

    I already tried monitoring every port, vlan or otherwise. None of the them provided WAN traffic data. Guess I'll stay on 380 until the next botnet targeting ASUS devices bricks it. By then the hardware should need replacing anyway.
  11. orion44

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

    Any idea if the SNMP issue can be corrected in a future 384 release? I'd rather not stay on 380 long term.
  12. orion44

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

    Stock ASUS firmware doesn't offer SNMP.
  13. orion44

    [Release 384/NG] Asuswrt-Merlin 384.5 is now available

    I did a quick test of 384.5 to see if SNMP issue was still present on my AC5300 -- unfortunately it still was. I'll stick with 380.70 in the short-term and hold out hope someday it can be corrected under a future 384 release.
  14. orion44

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

    Success! Steps to correct the SNMP issue: Flash 380.x firmware Perform factory reset Power cycle router (optional) Manually configure settings Confirm SNMP working as expected Restore prior config (optional) I also noticed the average CPU usage dropped as well after reverting to 380.x...
  15. orion44

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

    I'm not able to reproduce the issue with my RT-N66U since I can't run the new firmware. Is anyone else using the SNMP feature for monitoring and noticing a change in eth0 after updating to 384.x? The only thing I haven't tried is going back to 380.x and then doing a factory reset. When I...
  16. orion44

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

    Tools - System Information leads me to believe WAN traffic is now under vlan2 -- however the link state is down and no traffic is logged. Is this the root cause of the issue?
  17. orion44

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

    To note, I've tried downgrading back to 380 and the monitoring of eth0 is still LAN traffic (combined). I re-upgraded to 384, did a factory default restore, new manual config, and still no dice. Is this something that transcends firmware? It seems odd it can't be remedied with the old FW version...
  18. orion44

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

    I've always used SNMP to monitor my WAN traffic (among others) and after upgrading to 384.4_2 the data returned no longer includes WAN traffic and instead is the LAN traffic. Prior setup under 380.xx Monitoring interface 005 (eth0) via SNMP Shows only WAN traffic Current setup under 384...
  19. orion44

    Debating whether to update to 384

    I'm an RT-AC5300 owner on the fence as well. While I can deal with the royal PITA of a one-time factory reset for the 384 codebase, I have no time budget for a stability issues. 380 has been beyond rock solid for me, but I understand if I want to cling to it, I'll be SOL for future security patches.
  20. orion44

    ASUS Krackattack patch?

Top