Recent content by v.y.k

  1. v.y.k

    iptables pkts & bytes numbers are too low on Merlin 3004.388

    @RMerlin Thanks for the information
  2. v.y.k

    iptables pkts & bytes numbers are too low on Merlin 3004.388

    If this is true, there is no concern
  3. v.y.k

    iptables pkts & bytes numbers are too low on Merlin 3004.388

    Is it possible to find out which part of the firewall chains/rules, packets are not allowed to skip (ie INPUT)?
  4. v.y.k

    iptables pkts & bytes numbers are too low on Merlin 3004.388

    @ColinTaylor Is this just a traffic counters counting issue or actually some traffic packets are not using firewall?
  5. v.y.k

    iptables pkts & bytes numbers are too low on Merlin 3004.388

    Did not find anything on restart of firewall in the logs for the past 3 days. I will restart Router and monitor for the next few days
  6. v.y.k

    iptables pkts & bytes numbers are too low on Merlin 3004.388

    Uptime 6 days 8 hour(s) 4 minute(s) 26 seconds
  7. v.y.k

    iptables pkts & bytes numbers are too low on Merlin 3004.388

    Hi iptables pkts & bytes numbers on Merlin 3004.388 # iptables -L INPUT -v Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 1707 134K INPUT_PING icmp -- any any anywhere anywhere...
  8. v.y.k

    Traffic Monitoring - Save frequency - issue

    Should "Every 1 week" choice be removed from drop down, since it does not work?
  9. v.y.k

    Traffic Monitoring - Save frequency - issue

    So maximum value is 99 hours ~ 4.125 days, using direct nvram setting. Should "Every 1 week" choice be removed from drop down?
  10. v.y.k

    Traffic Monitoring - Save frequency - issue

    Asuswrt-Merlin Version 3004.388.6 - Asus RT-AX86U Pro Traffic Monitoring. Save frequency choice "Every 1 week" does not get persistent. After using "Apply" button, save frequency reverts back to the previous saved choice. Similar issue was found in Asuswrt-Merlin Version 386.12_4 - Asus RT-AC68U
Back
Top